nerdexam
Network_Appliance

NS0-528 · Question #70

After setting up a new cluster peering relationship between a production site and a new DR site, the customer mentions that the communication for this peer needs to be secured to help deter "man in…

The correct answer is C. Modify the relationship using -encryption-protocol-proposed. To secure an existing cluster peering relationship, you can modify it to enable encryption by using the -encryption-protocol-proposed option. This ensures that intercluster SnapMirror traffic is encrypted, helping protect against man-in-the-middle attacks.

Data Protection Solutions Implementation

Question

After setting up a new cluster peering relationship between a production site and a new DR site, the customer mentions that the communication for this peer needs to be secured to help deter "man in the middle" attacks. What can you do on the NetApp end to secure the existing cluster peering?

Options

  • AModify the firewall policy settings on the Intercluster LIFs.
  • BEnable aggregate level encryption.
  • CModify the relationship using -encryption-protocol-proposed.
  • DEnable IPsec between the sites.

How the community answered

(25 responses)
  • A
    4% (1)
  • B
    12% (3)
  • C
    80% (20)
  • D
    4% (1)

Explanation

To secure an existing cluster peering relationship, you can modify it to enable encryption by using the -encryption-protocol-proposed option. This ensures that intercluster SnapMirror traffic is encrypted, helping protect against man-in-the-middle attacks.

Topics

#cluster peering encryption#man-in-the-middle protection#intercluster security#encryption-protocol-proposed

Community Discussion

No community discussion yet for this question.

Full NS0-528 Practice