An administrator would like to use vRealize Operations Cloud to monitor an on-premises deployment. Which initial step must the administrator take?

Question

Options

• ADeploy a Cloud Proxy on-premises, and pair it with vRealize Operations Cloud.
• BInitiate a Cloud Proxy deployment on the cloud console, and pair it with vRealize Operations
• COpen firewall ports to vRealize Operations Cloud from the on-premises vCenter, and then add the
• DDeploy a vRealize Operations node on-premises, and pair it with vRealize Operations Cloud.

• A
  4% (1)
• B
  74% (17)
• C
  13% (3)
• D
  9% (2)

Explanation

Option B is correct because vRealize Operations Cloud (a SaaS product) requires the deployment process to be initiated from the cloud console first - this generates the necessary pairing token/OTP that the Cloud Proxy needs to authenticate and register itself with the cloud instance. Only after initiating from the cloud side can you deploy and activate the proxy on-premises.

Why the distractors are wrong:

• A reverses the order - you cannot deploy a Cloud Proxy on-premises and then try to pair it; the cloud console must initiate the process to generate the credentials needed for pairing.
• C is insufficient - opening firewall ports alone does not establish communication; a Cloud Proxy is still required as the secure intermediary between on-premises infrastructure and the cloud service.
• D confuses architectures - deploying a full vRealize Operations node on-premises describes a traditional on-premises deployment, not the Cloud (SaaS) model; Cloud Proxy is a lightweight component, not a full node.

Memory tip: Think "Cloud First, Proxy Second" - with any SaaS monitoring tool, you always start in the cloud console to generate the handshake credentials, then deploy the on-premises component (the Cloud Proxy) using those credentials to complete the pairing.

No community discussion yet for this question.