VMware Cloud Foundation Administrator (2V0-17.25) (2V0-17.25) - Broadcom

In VCF 9.x, air-gapped bring-up requires staging the required binaries in the VCF Installer. The documented list explicitly includes NSX and VCF Operations among the components to upload. The product guide states: “VMware Cloud Foundation required binaries include… NSX … VMware Cloud Foundation Operations … vCenter … SDDC Manager…” (exact list excerpt). This list does not call for ESX images or the legacy “Lifecycle Manager.” Therefore, from the given options the two binaries that must be uploaded are NSX and VCF Operations. ESX is pre-imaged on hosts per preparation guidance and is not a required VCF Installer binary; “Lifecycle Manager” is not used in VCF 9.0 bring-up.<br />
===========

VCF 9.0 introduces Log Data Transfer initiated from VCF Operations. The docs say: “You can transfer log data for up to 90 days from Aria Operations for Logs 8.x… The migrated logs are stored in VCF Operations for logs.” and “To transfer logs… navigate to the Logs Data Transfer card in Administration > Control Panel… click the INITIATE TRANSFER button… You can select the duration of logs to transfer…” (emphasis added). They further clarify that simple forwarding does not transfer already ingested logs: “Forward logs… does not transfer already ingested logs. Transfer historical logs up to 90 days… using the Log Data Transfer feature in VCF Operations.” Hence, the correct action is to initiate the transfer in VCF Operations (Administration > Control Panel > Logs Data Transfer).<br />
===========

VCF 9.0 replaces legacy bring-up tooling with the VCF Installer, which provides a deployment wizard that validates configuration before bring-up. The guide describes: “The deployment wizard validates your inputs… and displays errors and warnings if any.” and that administrators “Download and complete the planning and preparation workbook and have the information ready for validating inputs in the deployment wizard.”<br />
While the workbook is used to collect information, the validation of those inputs is performed by the<br />
VCF Installer wizard prior to deployment. SDDC Manager is used after bring-up for lifecycle operations, and Cloud Builder is not used in VCF 9.0 deployments. Therefore, VCF Installer is the correct tool for collecting (via wizard prompts) and validating initial deployment inputs.<br />
===========

A VM Class predefines hardware for Supervisor-managed VMs: “The VM class… defines such parameters as the number of virtual CPUs, memory capacity, and reservation settings.” Administration steps show these are configurable: “You can configure hardware resources such as CPU, memory, and different devices” when editing a VM class. Additionally, the DCLI/API specification underscores CPU and Memory fields: “<br />
<br />
--cpu-count …<br />
Required.” and “<br />
<br />
--memory-mb … Required.” for a VM class.<br />
While network adapters, PCI devices, and instance storage can also be added via advanced config,<br />
the question asks for two; CPU and Memory are canonical, always-present VM Class resources per the core definition above.<br />
===========

VCF 9.0 documents two Operations for Logs/Operations models—Simple (Standard) and High Availability (Cluster)—and highlight that Simple is the minimal footprint option intended for test/dev: “Architecture flexibility: Can be deployed in a Simple or Highly Available Cluster deployment. Recommended deployment is a HA Cluster… Simple deployment is for test/dev environments, it is not for production use cases.” By contrast, HA/clustered models increase resources to provide redundancy at scale. Since the requirement is the smallest resource footprint, the Simple model is the correct selection. (Stretched/Continuous Availability options are not listed VCF Operations models in this context.)