nerdexam
Network_Appliance

NS0-157 · Question #344

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

The correct answer is A. Provides zero copy, non-disruptive relocation of (non-root) online SFO aggregates to a partner C. Is utilized during planned events such as fast negotiated takeovers, controller hardware. 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.

Data Protection and High Availability

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

How the community answered

(30 responses)
  • A
    83% (25)
  • B
    13% (4)
  • D
    3% (1)

Why each option

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.

AProvides zero copy, non-disruptive relocation of (non-root) online SFO aggregates to a partnerCorrect

ARL relocates non-root SFO aggregates to the partner node in a zero-copy fashion, meaning only ownership metadata changes while the data remains in place on the same disks, keeping volumes continuously online throughout the operation.

BProvides zero copy, non-disruptive relocation of (root) online CFO aggregates to a partner node

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.

CIs utilized during planned events such as fast negotiated takeovers, controller hardwareCorrect

ARL is specifically designed for planned, controlled events such as fast negotiated takeovers, controller hardware upgrades, and replacement procedures where maintaining data availability is required and the operation can be orchestrated in advance.

DIs utilized during unplanned events such as controller failure

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

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

Topics

#aggregate relocation#ARL#SFO aggregates#non-disruptive operations

Community Discussion

No community discussion yet for this question.

Full NS0-157 Practice