This website uses cookies to ensure you get the best experience.
Learn more.
A pipeline needs recent event replay for consumers and seven years of queryable historical retention at an appropriate cost. Which design principles should it apply? Select 2 answers.
Published
- Assume any stream automatically retains all data forever without a retention setting.
- Persist history to an appropriate durable store such as S3, with cataloging, query layout, and lifecycle policies for the long-term requirements.
- Use the stream retention window for operational replay and recovery of recent consumer progress.
- Delete stream records before any durable sink commits them and rely on downstream consumers to reconstruct the missing events.
- Keep only consumer checkpoints and discard the event payloads needed for future historical queries.
Comments — 0
Sign in to comment