You must update a production streaming pipeline that ingests from Pub/Sub and have the updated pipeline reprocess the previous two days of delivered messages. Which actions accomplish this? (Choose two.)

The retain-acked-messages flag, when enabled on a Pub/Sub subscription, allows messages that have already been acknowledged to be retained for a specified duration. This enables reprocessing of past messages, which is crucial for updating a streaming pipeline and re-evaluating historical data. Pub/Sub Seek with a timestamp is the other correct option. Seek allows you to reset a subscription's position to a specific timestamp or snapshot, effectively replaying messages from that point forward. This directly addresses the need to reprocess messages from the previous two days. Using a Pub/Sub Snapshot captured two days before deployment would only allow you to replay messages from the point the snapshot was created, not necessarily the last two days of delivered messages if the snapshot was older. Creating a new Pub/Sub subscription two days before deployment would not help reprocess existing messages on the old subscription; it would only start receiving new messages from its creation time. The clear-retry-policy flag is for managing message redelivery attempts, not for reprocessing acknowledged messages.