1Z0-083 · Question #70
Which three are true about RMAN persistent configuration settings, administration, and their effects? (Choose three.)
The correct answer is A. A target database's persistent RMAN configuration settings are always stored in the target's C. Backups written to the fast recovery area (FRA) that are oboslete based on the redundancy F. The V$RMAN_CONFIGURATION view displays only settings with values that have been. A is correct because RMAN persistent configuration settings are stored in the target database's control file - this is why they persist across sessions without a recovery catalog. C is correct because the Fast Recovery Area (FRA) has built-in automatic space management: when…
Question
Which three are true about RMAN persistent configuration settings, administration, and their effects? (Choose three.)
Options
- AA target database's persistent RMAN configuration settings are always stored in the target's
- BBackup older than the recovery window retention policy are always deleted automatically if the
- CBackups written to the fast recovery area (FRA) that are oboslete based on the redundancy
- DThe RMAN SHOW ALL command displays only settings with nondefault values.
- EA target database's persistent RMAN configuration settings are always synchronized
- FThe V$RMAN_CONFIGURATION view displays only settings with values that have been
- GA DBA must specify either a redundancy retention policy or a recovery window retention policy.
How the community answered
(28 responses)- A71% (20)
- B4% (1)
- D14% (4)
- E7% (2)
- G4% (1)
Explanation
A is correct because RMAN persistent configuration settings are stored in the target database's control file - this is why they persist across sessions without a recovery catalog.
C is correct because the Fast Recovery Area (FRA) has built-in automatic space management: when space is needed, Oracle automatically deletes obsolete backups (those exceeding the redundancy threshold), which is a key advantage of using the FRA over a regular disk location.
F is correct because V$RMAN_CONFIGURATION only contains rows for settings that have been explicitly changed from their defaults - making it a compact, non-default-only view, unlike SHOW ALL which displays every setting regardless.
Why the distractors fail: B is wrong because RMAN never auto-deletes obsolete backups outside the FRA - you must run DELETE OBSOLETE manually. D is the reverse of reality: SHOW ALL shows all settings including defaults (F describes the view that filters to non-defaults only). E is wrong because settings live in the control file and are not automatically synchronized with a recovery catalog - sync requires explicit action. G is wrong because RMAN has a built-in default retention policy (REDUNDANCY 1), so no explicit specification is required.
Memory tip: Think "ACF = Always Control File, Auto-FRA, Configured-only V$" - A stores in the control file, C means FRA handles its own cleanup, and F reminds you the V$ view only shows what you've explicitly configured.
Topics
Community Discussion
No community discussion yet for this question.