Explanation:
To reprocess Pub/Sub messages from the last two days, enabling the retain-acked-messages flag is essential as it allows the subscription to retain acknowledged messages for a certain period, enabling replay with the seek operation. Using Pub/Sub Seek with a timestamp is the method to actually reset the subscription's cursor to a given timestamp or snapshot, allowing reprocessing from that point in time. These two actions together ensure the pipeline can access and reprocess the necessary messages.
Ultimate access to all questions.
No comments yet.
You are enhancing the business logic of a streaming pipeline that ingests data from Pub/Sub in production. To ensure the updated pipeline can reprocess Pub/Sub messages from the last two days, which two actions should you take?
A
Utilize the Pub/Sub subscription clear-retry-policy flag
B
Capture a Pub/Sub Snapshot two days prior to deployment
C
Establish a new Pub/Sub subscription two days before deployment
D
Enable the Pub/Sub subscription retain-acked-messages flag
E
Apply Pub/Sub Seek with a specific timestamp