NetApp NS0-528 Exam Dumps

Although the SnapMirror policy includes rules for retaining Snapshot copies, the ability to make them tamper-proof (i.e., locked) depends on enabling snapshot locking on the destination volume. You must explicitly run:

volume modify -volume <vol_name> -snapshot-locking-enabled true

Without this setting, SnapMirror-created Snapshot copies can still be deleted manually. Enabling snapshot-locking ensures that retention rules (like the 5-day daily rule in your policy) are enforced and Snapshots are immutable.

For a SnapMirror relationship to function properly, each node in a cluster must have at least one intercluster LIF. These LIFs are used exclusively for replication traffic and ensure that all nodes can participate in SnapMirror operations.

Active IQ Unified Manager can monitor SnapMirror relationships and generate email alerts based on lag threshold policies. You can configure it to trigger an alert when the replication lag exceeds 1.5 hours, helping prevent unnoticed replication issues.

To ensure Intercluster LIFs are bound to dedicated ports and used only for replication traffic, you must first create a service policy that defines the LIF's role (e.g., intercluster). The network interface service-policy create command allows you to specify that the LIF is intended strictly for intercluster services, ensuring it's isolated from data traffic.

To protect SnapLock Compliance WORM data with long-term retention (14 years) against hardware and site-level failures, you must use NetApp solutions that preserve both the data and its compliance metadata:

SnapMirror Asynchronous supports replication of SnapLock volumes, preserving WORM and compliance metadata.

SnapMirror SVM replicates the entire SVM, including configuration and compliance settings.

MetroCluster provides synchronous replication and automatic site failover with full preservation of SnapLock compliance attributes.