An administrator is preparing to deploy VMware vSphere Foundation using the VMware Cloud Foundation (VCF) Installer wizard. During host onboarding, it is discovered that the VMware ESX hosts each…

Question

Options

• AProceed with the wizard and override host credentials during staging.
• BUse the deployment wizard and enter credentials per host manually.
• CSet the password to expire on all ESX hosts.
• DUse a JSON specification file to define per-host credentials.

• A
  10% (4)
• B
  5% (2)
• C
  3% (1)
• D
  82% (32)

Explanation

When VMware ESX hosts have differing root passwords during a VCF deployment, the standard Installer wizard cannot proceed because it expects uniform credentials across all hosts - the JSON specification file is the only supported mechanism that allows per-host credential definitions, giving administrators granular control over each host's authentication parameters within a single deployment specification.

Why the distractors are wrong:

• A is incorrect because there is no "override host credentials during staging" option within the wizard itself - that functionality simply doesn't exist in the UI flow.
• B is incorrect because the wizard UI does not provide a field to enter different credentials per host manually; it treats host credentials as a uniform value.
• C is incorrect because setting passwords to expire is a security/lifecycle operation and does nothing to resolve the immediate problem of mismatched credentials during deployment.

Memory tip: Think of the JSON file as the "escape hatch" for anything non-uniform in VCF deployments. Whenever a VCF question involves hosts that differ in any per-host parameter (passwords, networking, etc.), the JSON specification file is almost always the correct answer - the wizard is designed for homogeneous environments, while JSON handles the exceptions.

No community discussion yet for this question.