1Z0-062 Question #118: Real Exam Question with Answer & Explanation

Question

Options

• ATransactions and queries accessing database objects contained in any tablespace stored in
• BMirroring of allocation units will be done to ASM disks in the CONTROLLER2 failure group until
• CThe data in the CONTROLLER1 failure group is copied to the controller2 failure group and
• DASM does not mirror any data until the controller failure group is brought back online, and newly
• ETransactions accessing database objects contained in any tablespace stored in DGROUP1 will

Explanation

When an ASM failure group becomes temporarily unavailable, ASM does not automatically copy or rebalance the affected allocation units to the remaining failure group - it waits for the failure group to return and then resyncs.

Common mistakes.

• A. With a NORMAL or HIGH redundancy disk group, ASM has mirror copies in the surviving failure group and continues to serve transactions - it does not simply fail all transactions when one failure group goes offline.
• B. ASM does not copy allocation units from the failed failure group into the remaining failure group during the outage; rebalancing to compensate for a missing mirror requires a permanent disk drop, not a response to temporary unavailability.
• C. ASM does not copy data from CONTROLLER1 to CONTROLLER2 while CONTROLLER1 is offline; such a copy would require CONTROLLER1 to be accessible as the source, which it is not during the failure.
• E. Because mirror copies exist in CONTROLLER2, transactions can continue to access data stored in DGROUP1 - ASM reads from and writes to the surviving failure group rather than failing all access.

Concept tested. ASM failure group behavior during temporary unavailability

Reference. https://docs.oracle.com/en/database/oracle/oracle-database/19/ostmg/asm-disk-groups.html

No community discussion yet for this question.