To leverage version-flexible SnapMirror replication, you must use a relationship of type XDP (Cross-cluster Data Protection). The relationship type is defined only when the SnapMirror relationship is created and cannot be modified later. Therefore, to switch an existing DP (Data Protection) relationship to XDP, the administrator must first delete the original DP relationship and then create a new one, explicitly specifying the -type as XDP. This process enables replication between clusters running different supported versions of ONTAP software.

A. ONTAP does not automatically convert SnapMirror relationship types during a software upgrade. This change requires explicit administrative action to avoid unintended replication behavior.

B. The snapmirror resync command is used to re-synchronize data for an existing broken relationship, but it does not have an option to change the relationship's fundamental type.

C. This action is the opposite of the goal. A DP-type relationship is version-dependent, whereas an XDP-type relationship is required for version-flexible replication.

1. NetApp ONTAP 9.12.1 Documentation, "Data protection with SnapMirror," Section: "Transition from SnapMirror DP to SnapMirror XDP."

This section explicitly states the procedure: "You can transition from a SnapMirror DP relationship to a SnapMirror XDP relationship by deleting the SnapMirror DP relationship and then creating a SnapMirror XDP relationship between the source and destination volumes."

2. NetApp ONTAP 9.12.1 Documentation, "ONTAP commands," snapmirror create manual page.

The command syntax shows that the -type {DP|XDP|LS} parameter is set at the time of creation. It is not listed as a modifiable parameter in the snapmirror modify command, confirming that the type cannot be changed on an existing relationship.

3. NetApp Technical Report TR-4015, "SnapMirror Configuration and Best Practices Guide for ONTAP 9," Section: "SnapMirror Version-Independent Relationships."

This report details that "Version-independent SnapMirror relationships are also known as XDP relationships... If you want to convert a DP relationship to an XDP relationship, you must delete the DP relationship and create a new XDP relationship." This confirms the required procedure.

To secure an existing cluster peering relationship against man-in-the-middle attacks, encryption must be enabled for the intercluster traffic. NetApp ONTAP uses Transport Layer Security (TLS) to provide authentication and encryption for this communication. The cluster peer modify command is used to alter the properties of an existing peer relationship. Specifically, the -encryption-protocol-proposed parameter is used to propose and enable a TLS encryption policy on the connection, thereby securing all subsequent SnapMirror and management traffic between the clusters.

A. Modify the firewall policy settings on the Intercluster LIFs.

Firewall policies on LIFs control which services (e.g., management, NFS, iSCSI) are permitted to access the LIF; they do not encrypt the data traffic itself.

B. Enable aggregate level encryption.

NetApp Aggregate Encryption (NAE) is a data-at-rest encryption technology. It encrypts data on the physical disks within an aggregate, not data in transit over the network.

D. Enable IPsec between the sites.

While IPsec is an encryption protocol, ONTAP's native and integrated method for securing cluster peering and SnapMirror traffic is TLS, which is managed directly through the cluster peer command set.

1. NetApp ONTAP Documentation, cluster peer modify command reference:

"Use the cluster peer modify command to modify the attributes of a cluster peer relationship. ... -encryption-protocol-proposed {none|tls-psk} - Encryption Protocol Proposed. This parameter specifies the proposed encryption protocol to be used for authenticating the peer cluster and encrypting intercluster data."

Source: NetApp ONTAP 9.12.1 Documentation Center, Command Reference, cluster peer modify.

2. NetApp ONTAP Documentation, Security and data encryption:

"You can use Transport Layer Security (TLS) to encrypt all traffic between peered clusters, including SnapMirror replication traffic and management traffic. TLS encryption protects against eavesdropping and man-in-the-middle attacks. You can enable TLS encryption when you create a cluster peer relationship, or you can enable it later by modifying the relationship."

Source: NetApp ONTAP 9.12.1 Documentation Center, "Security and data encryption," section "Encrypting intercluster traffic with TLS."

3. NetApp Technical Report TR-4569, "ONTAP 9 Security Hardening Guide":

"ONTAP supports TLS encryption for intercluster communication. This includes cluster peering, SnapMirror, and SnapVault traffic. Enabling TLS encryption for intercluster communication is a recommended security best practice to protect data in transit from eavesdropping and man-in-the-middle attacks."

Source: NetApp TR-4569, "ONTAP 9 Security Hardening Guide," Page 23, Section "Intercluster Communication."

For establishing a resilient and functional cluster peer relationship for data protection, NetApp best practices require creating at least one Intercluster LIF on each node in both the source and destination clusters. This configuration ensures that if a volume is moved to a different node within its cluster (e.g., during a high-availability takeover event), replication can continue without interruption. Therefore, the six-node primary cluster requires a minimum of six Intercluster LIFs (one per node), and the two-node secondary cluster requires a minimum of two Intercluster LIFs (one per node).

A. This configuration is insufficient for a multi-node cluster, creating a single point of failure and preventing replication from any node that does not host the single LIF.

C. This is insufficient for the six-node primary cluster. Volumes on the four nodes without an Intercluster LIF would be unable to participate in replication.

D. This configuration exceeds the minimum requirement. While creating multiple Intercluster LIFs per node is a valid strategy for increasing throughput, it is not the minimum number needed.

1. NetApp ONTAP 9 Documentation, Network management, "Create intercluster LIFs" section: "For cluster peering, you must create at least one intercluster LIF on each node in the cluster. This practice enables each node to connect with every node in the peer cluster."

2. NetApp Technical Report 4182, "SnapMirror Configuration and Best Practices Guide for ONTAP 9," Section 3.1 Intercluster Networking: "NetApp recommends creating one intercluster LIF on each node in the cluster. This configuration provides the optimal balance of availability and simplicity."

3. NetApp ONTAP 9 Documentation, Data protection, "Prerequisites for cluster peering" section: "You must create at least one intercluster LIF on each node that will communicate with the remote cluster. It is a best practice to create intercluster LIFs on all nodes in the local and remote clusters."

The customer has two distinct requirements that can be met by creating a single Snapshot policy with two different schedules.

1. Four-Month Retention: The first requirement is for a local retention time of at least four months. This is best achieved by creating a weekly schedule within the Snapshot policy and setting its retention period to 122 days (approximately four months). This provides long-term recovery points without consuming excessive space.

2. One-Week Immutability: The second requirement is to protect one week of retention from deletion by ransomware or administrators. This is accomplished by using NetApp's SnapLock feature. A daily schedule can be configured to set a SnapLock (WORM) retention period of 7 days on the daily Snapshot copies, making them immutable for that duration.

Combining these two settings in one policy effectively meets both customer objectives.

A. Enable Autonomous Ransomware Protection (ARP) on the volume.

ARP is a reactive feature that creates locked Snapshot copies after it detects a potential ransomware attack. It does not guarantee a proactive, one-week protected retention as part of a standard policy.

C. Create a Snapshot policy with the maximum daily snapshots set to 122.

While this provides four months of retention, keeping 122 daily snapshots is generally less space-efficient for long-term retention than a tiered policy using weekly or monthly copies as described in option B.

1. NetApp Technical Report 4572: Ransomware Protection Using NetApp ONTAP Technologies, Page 10, Section: "ONTAP SnapLock".

Quote: "SnapLock for SnapVault copies provides the ability to make Snapshot copies immutable for a specified retention period... This feature prevents the Snapshot copies from being deleted either accidentally or maliciously before the retention period expires." This document confirms that SnapLock is the correct technology to protect Snapshot copies from deletion (supporting option D).

2. NetApp ONTAP 9 Documentation Center, Command Reference, snapshot policy create.

Details: The documentation for this command shows the parameters for creating schedules within a policy. It includes -schedule (e.g., daily, weekly), -count (number of copies to keep), and -retention-period (duration to keep copies). It also details the -snaplock-period parameter, which can be applied to a specific schedule. This confirms that a single policy can have a weekly schedule with a long retention period (Option B) and a daily schedule with a SnapLock period (Option D).

3. NetApp ONTAP 9 Documentation Center, Data protection, "Create a Snapshot policy".

Details: This guide explains that a Snapshot policy defines when to create Snapshot copies and how many copies to retain. It states, "A Snapshot policy can have up to five schedules with different retention periods and labels." This supports the creation of a policy with both a daily schedule for SnapLock and a weekly schedule for long-term retention.

Multi-admin approval (MAA), also known as multi-admin verification, is a security feature in ONTAP designed to prevent a single administrator from performing critical destructive operations, such as deleting a volume. Once this feature is enabled on a cluster, it cannot be disabled by a cluster administrator through either the command-line interface (CLI) or ONTAP System Manager. The only sanctioned method to disable this security control is to contact NetApp Support, who will guide you through a verified process. This restriction ensures the integrity of the dual-control security principle that MAA enforces.

A. Multi-admin approval can be disabled, but it requires intervention from NetApp Support; it is not a permanently enabled feature.

C. The -force parameter in the volume delete command is used to bypass operational warnings (e.g., deleting a volume that is online), not security workflows like multi-admin approval.

D. A simple toggle in System Manager would defeat the purpose of a multi-person security control, as a single administrator could easily bypass it. Therefore, this option is not available.

1. NetApp ONTAP Documentation, "ONTAP concepts > Security and data encryption > Multi-admin verification": This document states, "When multi-admin verification is enabled, you cannot disable it. You must contact NetApp Support to disable it." This directly confirms that a support case is the required procedure.

2. NetApp ONTAP 9 Commands, security multi-admin-verify Manual Page: Examination of the command set for managing MAA (security multi-admin-verify) shows commands to create, approve, reject, and veto requests, but there is no disable or modify command available to the administrator to turn the feature off once enabled. This reinforces that the control is outside the administrator's direct management.