What is the key difference between configuring Hybrid Linked Mode from the Cloud Gateway Appliance and the VMware vSphere Client?

Question

Options

• AThe on-premises VMware vSphere version must be vSphere 6.5 or later.
• BVMware Cloud on AWS software-defined data center (SDDC) does NOT reveal the on-
• CMinimal overhead is required in the on-premises data center.
• DCentralized administration is available through the VMware vSphere Client.

• A
  3% (1)
• B
  74% (23)
• C
  6% (2)
• D
  16% (5)

Explanation

Option B identifies the critical behavioral distinction between the two configuration methods: when Hybrid Linked Mode is set up through the VMware vSphere Client (rather than the Cloud Gateway Appliance), the VMware Cloud on AWS SDDC does not expose or reveal the on-premises vCenter Server to cloud-side administrators - creating a one-directional visibility boundary that is unique to that method.

Option A is a general prerequisite for HLM (vSphere 6.5+ is required regardless of which method you use), so it doesn't distinguish between the two approaches. Option C describes a benefit of the vSphere Client method (no need to deploy an on-premises appliance), but it's a deployment convenience, not the defining functional difference. Option D describes a capability of HLM in general - unified management via the vSphere Client is the whole point of HLM, not something specific to one configuration path over the other.

Memory tip: Think "Client = Conceals." When you configure HLM from the vSphere Client, the cloud SDDC conceals (does not reveal) the on-premises vCenter. The Cloud Gateway Appliance acts as a visible bridge in both directions, but the Client method keeps the on-premises side private from the cloud perspective.

No community discussion yet for this question.