Capacity planners ask how long undeleted OCI Queue messages can remain compared with Streaming retention. Which statement matches official Queue retention?
Select an answer to reveal the explanation.
Short Explanation
Queue keeps messages from 10 seconds up to 7 days (default one day). Past retention, undeleted messages expire. That is a wider, queue-level setting—not Streaming’s 24–168 hour create-time window, and not a fictional 30-day Queue tier.
Full Explanation
Official OCI Queue retention is configurable from 10 seconds to 7 days, with a default of one day. Undeleted messages can expire when retention elapses even if no consumer deleted them—capacity planners must not invent a 30-day Queue option or assume infinite keep. That retention model differs from Streaming’s create-time retention window (documented in hours within Streaming’s own bounds) and from Object Storage lifecycle policies. Claiming Queue always keeps messages forever until ack matching an infinite retention guarantee is false and dangerous for municipal backlog planning. Saying retention is fixed at 24 hours and immutable after create, identical to Streaming’s only option, misstates both products’ flexibility and ranges. Asserting Queue retention is only 30 to 90 days to match Object Storage lifecycle defaults invents a range Queue does not offer. Exam caveat: retention expiry can look like “lost jobs” if workers are down longer than the queue retains messages—pair retention settings with alerting on queue depth and consumer lag. Operational check: create a non-production queue with a short retention, publish a message, leave it untouched past retention, and confirm it disappears without a delete—then set production retention to cover expected outage windows within the 7-day maximum.