An administrator attempted to enable Data-in-Transit Encryption on a Scale-Out Prism Central cluster to encrypt service-level traffic between nodes. However, the feature did not work correctly due…

The correct answer is A. 2009. Nutanix Data-in-Transit Encryption secures inter-node service-level traffic within a Scale-Out Prism Central cluster using TLS. The CVM-specific port used for this encrypted communication between nodes is TCP port 2009. Firewall rules must explicitly allow port 2009 between all…

Secure and Protect Data

Question

An administrator attempted to enable Data-in-Transit Encryption on a Scale-Out Prism Central cluster to encrypt service-level traffic between nodes. However, the feature did not work correctly due to a firewall restriction. Which CVM-specific port should be allowed through the firewall for Data-in-Transit Encryption?

Options

A2009
B2010
C2020
D9440

How the community answered

(46 responses)

A
87% (40)
B
2% (1)
C
7% (3)
D
4% (2)

Explanation

Nutanix Data-in-Transit Encryption secures inter-node service-level traffic within a Scale-Out Prism Central cluster using TLS. The CVM-specific port used for this encrypted communication between nodes is TCP port 2009. Firewall rules must explicitly allow port 2009 between all Prism Central nodes for the feature to function. Port 2010 is used for other Nutanix internal services, port 2020 is used for the Stargate (storage I/O) service, and port 9440 is the standard HTTPS port for Prism UI and API access - none of these are the correct answer for Data-in-Transit Encryption.

Topics

#Data-in-Transit Encryption#Prism Central Networking#Firewall Configuration#Nutanix Security

Community Discussion

No community discussion yet for this question.

Full NCP-MCI-6.10 Practice