2V0-17.25 Practice Questions

The VCF 9.0 Convergence and Migration Guide outlines prerequisites and unsupported configurations when moving from a standalone vSphere deployment into VCF-managed workload domains.

Enhanced Linked Mode (ELM) must be removed : VCF does not support multiple vCenters joined in Enhanced Linked Mode. Each workload domain has its own dedicated vCenter instance, managed by SDDC Manager. The documentation states: “Before convergence, Enhanced Linked Mode must be deactivated. VCF requires independent vCenters for each workload domain.”

Lifecycle Manager must use Images only : VCF lifecycle operations are exclusively image-based. Baselines are not supported. “All clusters managed by VCF must be converted to vSphere Lifecycle Manager image-based lifecycle management prior to convergence.”

Other options are not required:

25 Gbps uplinks (A) are recommended for high throughput but not mandatory; 10 Gbps uplinks are supported.

An additional vMotion VMkernel (C) is not required by default, as standard vMotion networking is included in convergence designs.

vSphere Standard Switches (D) are not supported; VCF requires Distributed Switches, and existing vDS configurations can be adapted.

Therefore, the two configurations that must change are: Deactivate Enhanced Linked Mode (B) and switch Lifecycle Manager to Images only (E) .

Comprehensive and Detailed Explanation:

The VCF Automation Networking Guide (9.0) documents that when an Organization for All Applications is created, networking constructs are provisioned automatically to provide immediate connectivity. Specifically, “During region creation, the system automatically deploys a Default VPC, a Provider Tier-0 Gateway, a VPC connectivity profile, and default SNAT rules to enable outbound access.” .

DNAT rules are not provisioned by default (they must be configured for inbound services). Likewise, NSX Transit Gateway is a multi-region design element, not automatically deployed for a single org setup. A VDS is a vSphere construct and not part of the NSX automation performed at this stage. Therefore, the automatically created items are: Default VPC (A), Provider Tier-0 Gateway (B), SNAT rule (E), and VPC Connectivity Profile (G).

The VCF 9.0 Operations Access Control Guide describes how dashboard sharing and user access is managed:

Identity Broker Authentication (D): All external users must authenticate via the VCF Identity Broker , which integrates with Active Directory, LDAP, or other identity providers. Documentation states: “Identity Broker provides single sign-on and federation, ensuring users are authenticated consistently across VCF Operations and Automation services.”

Grant Access to Dashboard (E): After authentication, the administrator must explicitly grant access to the dashboard for the specified group. This ensures that only the intended users can view or interact with the dashboard.

Set Time-Bound Access (C): VCF Operations supports time-bound access policies. The documentation specifies: “Access can be granted with an expiration period, ensuring access is automatically revoked after the configured interval (for example, 90 days).” This aligns with the 3-month requirement.

Other options are not suitable:

Reports (A) only send static data, not interactive dashboard access.

Embedded code (B, F) bypasses access control and does not provide authentication or time-limited sharing, which violates the security requirement.

Thus, the correct three steps are: Use Identity Broker (D), Grant access to dashboard (E), and Configure 3-month access expiration (C).

The VCF 9.0 Deployment Guide notes: “ All ESXi hosts must be installed with a supported ESXi version using a VMware ISO before they are commissioned into SDDC Manager. Commissioning is always performed via the management domain vCenter. ” The new workload domain vCenter does not exist until the domain is deployed, ruling out option

A.