Free Google Professional Data Engineer Actual Exam Questions - Question 7 Discussion
streaming pipeline with improved business logic. You need to ensure that the updated pipeline
reprocesses the previous two days of delivered Pub/Sub messages. What should you do?
Choose 2 answers
A. Seek with a timestamp is the only straightforward way to rewind and reprocess messages from exactly two days ago. E also works since Snapshots let you restore a consistent state from that time.
Option A makes sense since Seek rewinds messages by timestamp; E captures state to replay.
A and E. Seek with a timestamp is the only way to rewind the subscription to a precise point in time, which is perfect for reprocessing past messages. Snapshots are also useful because they let you capture the exact subscription state from two days ago, ensuring consistent replay without missing anything. The other options either don’t exist (B and D) or wouldn’t work since creating a new subscription now won’t give you backdated messages (C).
A/E for sure. Seek is built for replaying messages from a specific time, and snapshots let you capture the subscription state exactly two days ago so you can restart cleanly. Both cover the reprocessing need well.
A/E? Seek with a timestamp definitely works for replaying messages from a certain point in time, which fits the need to reprocess two days of data. Snapshots also seem handy because they capture the subscription state exactly, so when you update the pipeline, you can resume from that snapshot and not miss anything. Other options like creating a new subscription (C) won't help with past messages, and the retry-policy or retain-asked-messages flags don’t seem designed for reprocessing old data.
A imo since Seek works well for replaying from a timestamp. E also makes sense because snapshots can capture the exact state to resume from, which helps with consistent reprocessing after the update.
It’s A and E for me. Seek with a timestamp lets you replay messages from the past, and using a snapshot from two days ago ensures you have a precise point to replay from without missing anything.
Option A seems useful since Seek lets you replay messages from a specific time, but how exactly do you coordinate that with your pipeline update? Also, is there a limit to how far back Seek can go based on message retention?