Which network configuration is required for NetApp BlueXP to discover an on-premises NetApp cluster?

NetApp BlueXP utilizes a Connector, a software instance deployed within the customer's on-premises or cloud network, to manage resources. For BlueXP to discover and manage an on-premises ONTAP cluster, the Connector must establish a secure, outbound connection to the BlueXP SaaS platform. This communication occurs over HTTPS (port 443). The Connector initiates this connection to receive instructions, such as a discovery command, and to send back information about the on-premises cluster. All communication between the BlueXP service and the on-premises environment is brokered through this outbound-initiated connection, eliminating the need for insecure inbound firewall rules.

B. inbound 443 access to the cluster-management LIF: This is incorrect. Requiring inbound access from the internet to the cluster's management interface would be a significant security vulnerability. All communication is initiated from the internal Connector.

C. inbound 443 access from the BlueXP service: This is incorrect. The BlueXP architecture is designed so that the Connector initiates all connections outbound. The BlueXP service never initiates an inbound connection into the customer's network.

D. outbound 443 access to the Connector IP address: This describes an illogical traffic flow. The Connector is the component that needs outbound access to the BlueXP service, not the other way around.

1. NetApp BlueXP Documentation, "Networking requirements for the Connector": This document explicitly states the primary network requirement. In the "Outbound internet access" section, it specifies, "The Connector needs outbound internet access on port 443 to contact specific BlueXP endpoints." This directly supports the correct answer.

2. NetApp BlueXP Documentation, "Security in BlueXP": This document outlines the security architecture. Under the "Connector security" section, it states, "The Connector initiates a secure outbound connection to the BlueXP SaaS layer. No inbound connectivity from the internet to the Connector is required." This statement directly refutes options B and C, which propose inbound access.

3. NetApp BlueXP Documentation, "Learn about the Connector": This page describes the role of the Connector, stating, "It provides secure communication between the BlueXP management platform and the resources in your network." This reinforces that the Connector is the local agent responsible for all communication, which is initiated outbound.