As part of a VMware Cloud Foundation (VCF) design, an architect is responsible for planning for the migration of existing workloads using HCX to a new VCF environment. Which two prerequisites would…

Question

Options

• AExtended IP spaces for all moving workloads.
• BDRS enabled within the VCF instance.
• CService accounts for the applicable appliances.
• DNSX Federation implemented between the VCF instances.
• EActive Directory configured as an authentication source.

• A
  4% (2)
• B
  15% (7)
• C
  74% (34)
• D
  7% (3)

Explanation

VMware HCX (Hybrid Cloud Extension) is a key workload migration tool in VMware Cloud Foundation (VCF) 5.2, enabling seamless movement of VMs between on-premises environments and VCF instances (or between VCF instances). To plan an HCX-based migration, the architect must ensure prerequisites are met for deployment, connectivity, and operation. Let's evaluate Option A: Extended IP spaces for all moving workloads This is incorrect. HCX supports migrations with or without extending IP spaces. Features like HCX vMotion and Bulk Migration allow VMs to retain their IP addresses (Layer 2 extension via Network Extension), while HCX Mobility Optimized Networking (MON) can adapt IPs if needed. Extended IP space is a design choice, not a prerequisite, making this option unnecessary for completing the objective. Option B: DRS enabled within the VCF instance This is incorrect. VMware Distributed Resource Scheduler (DRS) optimizes VM placement and load balancing within a cluster but is not required for HCX migrations. HCX operates independently of DRS, handling VM mobility across environments (e.g., from a source vSphere to a VCF destination). While DRS might enhance resource management post-migration, it's not a prerequisite for HCX functionality. Option C: Service accounts for the applicable appliances This is correct. HCX requires service accounts with appropriate permissions to interact with source and destination environments (e.g., vCenter Server, NSX). In VCF 5.2, HCX appliances (e.g., HCX Manager, Interconnect, WAN Optimizer) need credentials to authenticate and perform operations like VM discovery, migration, and network extension. The architect must ensure these accounts are configured with sufficient privileges (e.g., read/write access in vCenter), making this a critical prerequisite. Option D: NSX Federation implemented between the VCF instances This is incorrect. NSX Federation is a multi-site networking construct for unified policy management across NSX deployments, but it's not required for HCX migrations. HCX leverages its own Network Extension service to stretch Layer 2 networks between sites, independent of NSX Federation. While NSX is part of VCF, Federation is an advanced feature unrelated to HCX's core migration capabilities. Option E: Active Directory configured as an authentication source This is correct. In VCF 5.2, HCX integrates with the VCF identity management framework, which typically uses Active Directory (AD) via vSphere SSO for authentication. Configuring AD as an authentication source ensures that HCX administrators can log in using centralized credentials, aligning with VCF's security model. This is a prerequisite for managing HCX appliances and executing migrations securely.

No community discussion yet for this question.