NS0-157 Question #344: Real Exam Question with Answer & Explanation

The correct answer is A: Provides zero copy, non-disruptive relocation of (non-root) online SFO aggregates to a partner. Aggregate Relocation (ARL) is a planned, non-disruptive operation that transfers ownership of non-root SFO aggregates between HA pair nodes without copying data, used during controller upgrades and similar maintenance.

Question

What is aggregate relocation (ARL)? Choose all that apply.

Options

AProvides zero copy, non-disruptive relocation of (non-root) online SFO aggregates to a partner
BProvides zero copy, non-disruptive relocation of (root) online CFO aggregates to a partner node
CIs utilized during planned events such as fast negotiated takeovers, controller hardware
DIs utilized during unplanned events such as controller failure

Explanation

Aggregate Relocation (ARL) is a planned, non-disruptive operation that transfers ownership of non-root SFO aggregates between HA pair nodes without copying data, used during controller upgrades and similar maintenance.

Common mistakes.

B. ARL applies only to non-root SFO aggregates; root aggregates are handled by CFO (Controller Failover) operations and follow a different code path during takeover and giveback.
D. ARL is exclusively a planned-event mechanism; unplanned controller failures trigger automatic SFO takeover, which is a distinct process from ARL and is not initiated by the administrator.

Concept tested. Aggregate Relocation (ARL) scope and use cases

Reference. https://docs.netapp.com/us-en/ontap-systems-upgrade/upgrade-arl/index.html

Community Discussion

No community discussion yet for this question.

Full NS0-157 Practice