Which statement is true regarding the retention policy for the incidents accumulated in the Automatic Diagnostic Repository (ADR)?

The correct answer is D. The default setting is for one year after which the incident metadata is purged from the ADR and. See the full explanation below for the reasoning.

Question

Options

AThe incident metadata is purged when the problem is resolved and the DBA closes the SR.
BThe incident files and dumps are not retained in the ADR for the manually created incidents.
CThe incident files are retained but the incident metadata is purged when the problem is resolved
DThe default setting is for one year after which the incident metadata is purged from the ADR and

How the community answered

(33 responses)

A
6% (2)
B
15% (5)
C
3% (1)
D
76% (25)

Community Discussion

Ingrid P.Mar 9, 2026

D is the correct answer. Oracle's ADR uses a time-based retention policy, not an event-based one, so incident metadata stays in the repository for one year by default regardless of whether the associated SR is open or closed. This is a classic trap on this exam because candidates assume some manual action like closing a service request triggers the purge, but the ADR operates on its own clock via the ADRCI utility. The dump files themselves actually have a shorter default retention than the metadata, which is a separate detail worth a second card. Make two cards here: one for the default metadata retention period (one year) and one to contrast it with the dump file retention period, because the exam loves to test whether you know those two values are not the same.

Wesley A.Jun 24, 2026

D is the one. The ADR keeps incident metadata for one year by default before purging it, which is the retention window Oracle sets out of the box, and you do not need to resolve a ticket or close an SR to trigger that cleanup, it just happens automatically on the age-based schedule.

Dragan P.Jun 27, 2026

D is correct, and anyone who has actually sat with ADRCI and run SET CONTROL knows this by reflex. The default retention period for incident metadata in the ADR is one year, 365 days, after which the purging policy kicks in automatically during housekeeping, no DBA action required. C is the tempting trap here because it sounds reasonable that a resolved problem would trigger cleanup, but ADR retention is purely time-driven, not state-driven, and nothing about closing an SR or marking a problem resolved touches the ADR clock. MOS note 1082335.1 spells out the two-tier retention scheme, where dump files get a shorter window than metadata, which is exactly why D trails off the way it does in the option text, the full sentence includes that the dump files are purged on a shorter default schedule than the metadata. Know your ADRCI commands, know your retention tiers, and this question is free points.

Grace U.Jun 29, 2026

Worth adding that some questions rephrase the retention windows in hours rather than days, so locking in that SHORTP_POLICY defaults to 720 hours and LONGP_POLICY to 8760 keeps you from second-guessing a reworded version of this exact item.

Marisol N.Mar 23, 2026

D, one year then metadata purges, saw this word-for-word on my 034 sitting, circled it immediately because I had drilled the ADRCI "purge" command defaults the week before and that timestamp burned right in.

Dervla O.Apr 23, 2026

D is the one that holds up under scrutiny because the ADR does not tie purge behavior to SR closure or problem resolution status, it runs on a time-based default. Quick question for anyone working through this: do you know whether that one-year default applies equally to the incident metadata and the dump files, or does Oracle set a different default interval for each?

Anjali D.Jun 27, 2026

Our group went back and forth on this one because A is genuinely tempting if you have a support background and think in terms of SR lifecycle, but Oracle does not tie ADR purging to any manual action like closing a service request. The ADR retention is purely time-based and managed through ADRCI, with the default being one year for incident metadata and 30 days for the actual dump files, which is a detail worth keeping straight because those two thresholds are different. C tries to flip the relationship in a way that sounds plausible but gets it backwards, since the dumps age out before the metadata does, not the other way around. So D is where we landed, even though the option text got cut off in some versions of the question, the key phrase is the one-year default after which the metadata is purged from the ADR. Anyone in the group who has used ADRCI and run SET CONTROL want to add anything here, especially around whether the default thresholds differ between Oracle 11g and later versions?

Toby R.Apr 7, 2026

This one showed up almost word for word on my exam and I almost talked myself into C because I kept thinking "purge the files, keep the metadata" sounds more reasonable, but then I remembered the ADR default retention is a full year for the metadata and that snapped me back to D.

Ingrid P.Apr 10, 2026

The memory anchor is solid but worth tightening before it goes on a card, because the ADR deleted-object lifetime default is 180 days, not a full year, so if that number ever shows up in a distractor you want the right figure locked in.

Imani T.Jun 27, 2026

D is right, though "one year" feels generous, that default holds for metadata purge.

Anjali D.Jun 29, 2026

The "one year" number usually assumes you are on a standard retention plan, so if your org negotiated a shorter SLA with the vendor that default could be cut to 90 days or even 30, which is worth verifying before you lock in that answer.

Grace U.Jun 17, 2026

D is the one to go with here, and once you know that Oracle sets the ADR purging window to 365 days by default, it sticks. That threshold applies to both the incident metadata and the associated dump files, which is why the other options describing manual closure or selective purging do not hold up under the actual ADR architecture.

Full 1Z0-034 Practice