Which three tasks can be performed using a duplicate database? (Choose three.)

Bao N.Dec 21, 2025

A, B, and C are your three correct picks here. A duplicate database is essentially a copy of your production target that you spin up separately, so it is the perfect sandbox for testing backup and recovery procedures without touching live data, validating what an upgrade path actually does to your environment before you commit, and benchmarking how an application change hits performance under realistic conditions. Option D is the trap, because continuously shipping archive logs to support failover is what a standby database does in a Data Guard setup, not a duplicate. Keep that distinction straight because the exam loves to blur duplicate versus standby, and if your score is dipping on RMAN questions this is usually one of the spots bleeding points.

Brenda K.Jan 1, 2026

Saw this exact question on my 1Z0-034 sitting and knocked it out in under 40 seconds because D is a Data Guard standby job, not a duplicate database job, so I crossed it off immediately and banked the time. A, B, and C are your three keepers, this is a quick win so grab it and move on.

Carlos M.Jan 7, 2026

A, B, C. D trips people up because it sounds plausible but that describes a physical standby database in a Data Guard setup, not a duplicate. RMAN duplicate gives you a point-in-time copy of the target for testing, it has no built-in mechanism to keep pulling archive logs from production on an ongoing basis for failover purposes. A duplicate is a sandbox, basically, so anything you would want to test without touching production fits right in, backup and recovery scripts, upgrade paths, and application load testing for performance impacts. I saw this exact question on my exam last month and the key word that knocked out D for me was "continuously," because nothing about RMAN duplicate implies a live, sustained connection to the target for log shipping.

Anjali D.Dec 28, 2025

Saw this exact question, eliminated D fast since that is standby database territory, locked in A, B, C.

Lena V.Jan 10, 2026

I went back and forth on this one but I keep landing on A, B, and D as my three. The continuously updating archive logs piece is exactly what a duplicate database does when you set it up as a warm standby scenario, and Oracle's own RMAN duplicate documentation covers that use case directly. You use the duplicate to receive and apply those archived logs from the target so you have a near-real-time copy ready for failover, which is a core operational reason someone would build a duplicate in the first place. C feels like a distractor to me because performance testing against application changes is more of a snapshot clone or a refreshed test environment scenario, not the purpose Oracle specifically calls out for RMAN duplicate. The failover continuity angle in D is what separates a duplicate from just a plain backup restore, so I think that distinction is exactly what the exam is testing here.