Which two prerequisites are required for integrating vRealize Operations Cloud and vRealize Log Insight Cloud to manage on-premises vSphere environments? (Choose two.)

Question

Options

• ADeploy the vRealize Operations Cloud Content pack, and configure the adapter to connect to the
• BvRealize Operations Cloud and vRealize Log Insight Cloud must be enabled in the same
• CDeploy a cloud proxy, and then configure vCenter and ESXi hosts syslog to forward logs to the
• DvRealize Operations Cloud and vRealize Log Insight Cloud must be enabled in separate
• EDeploy an on-premises vRealize Log Insight instance, and configure the integration directly with

• A
  2% (1)
• B
  7% (3)
• C
  80% (33)
• D
  10% (4)

Explanation

Integrating cloud-based vRealize Operations and Log Insight with on-premises vSphere requires two physical bridging components: a cloud proxy (C) to relay telemetry from vCenter/ESXi to the cloud service, and an on-premises vRealize Log Insight collector instance (E) to actually ingest and forward syslog data from the on-premises hosts into vRealize Log Insight Cloud. Without both, there is no secure, routable path from the on-premises environment to either cloud service.

Why the distractors are wrong:

• A - Content packs add dashboards and analysis templates; they are post-integration enhancements, not prerequisites.
• B - Being enabled in the "same" [organization/tenant] is a configuration detail, not a named technical prerequisite for the integration to function.
• D - Requiring separate organizations contradicts how VMware's cross-product cloud integrations actually work; co-tenancy (same org) is expected, not separation.

Memory tip: Think "Proxy + Collector = Bridge" - you need one bridge piece for metrics (cloud proxy → vRealize Operations Cloud) and one for logs (on-prem Log Insight instance → vRealize Log Insight Cloud). If either bridge piece is missing, the on-premises environment stays invisible to the cloud services.

No community discussion yet for this question.