2V0-17.25 VMware Cloud Foundation 9.0 Administrator Questions and Answers

The VCF Operations for Networks (formerly vRNI) enables Application Discovery and Network Visibility. According to VCF 9.0: “Operations for Networks provides flow-based application discovery, dependency mapping, and security planning. This allows administrators to visualize application topology and relationships across the VCF fleet.” By contrast, VCF Operations for Logs provides log aggregation, while the Collector provides integration for metrics, not discovery. The vSphere Supervisor enables Kubernetes workloads, not application discovery. Therefore, to achieve Service and Application Discovery, administrators must deploy VCF Operations for Networks.

The vSAN ESA documentation in VCF 9.0 explains that auto-policy management dynamically selects the most efficient data placement policy based on cluster size. For RAID-6 (erasure coding with double parity), the minimum required host count is 6. The docs state:

“RAID-6 (Erasure Coding with FTT=2) requires a minimum of six hosts in a vSAN ESA cluster. This ensures that data and parity components can be distributed across unique failure domains.”

With fewer than six hosts, RAID-6 cannot be enforced and auto-policy management will fall back to RAID-1 mirroring. RAID-6 in vSAN ESA provides higher storage efficiency but comes with stricter host count requirements. Options 2 and 4 are far below requirements, while 8 provides more redundancy but is not the minimum. Therefore, the correct minimum number of hosts for RAID-6 with ESA is 6.

A VCF Automation region is built from one or more vSphere Supervisors, and the participating vCenter instances must be integrated with an NSX Manager. VMware Cloud Foundation 9.0 states that before creating a region, administrators must verify that the vCenter instance has a Supervisor enabled.

The documentation also states that VCF Automation creates a region by grouping Supervisors from one or more vCenter instances, provided those vCenter instances are configured with the same NSX instance. A single NSX Manager must therefore integrate with all vCenters participating in a particular region.

Options A and E apply when multiple Supervisors/vCenters are combined into one region because VM classes and storage classes must then be identical across those participating instances. In this scenario, the design is for three separate service-class regions backed by three workload domains, so identical classes across all vCenters are not inherently required. Region quotas are created after regions exist and are assigned to Organizations; they are not prerequisites for creating the regions themselves.

In VMware Cloud Foundation 9.0, certificate replacement procedures for components such as:

vCenter Server

NSX Manager

SDDC Manager

Aria Suite components

require certificates to be provided in PEM format.

From the VCF 9.0 documentation under Certificate Management:

“When replacing certificates with CA-signed certificates, provide the certificate and private key in PEM format.”

Additionally:

“The certificate file must include the full chain (server certificate and intermediate certificates) in PEM encoding.”

Why PEM?

PEM format:

Base64 encoded

Human-readable

Common format for VMware components

Required for SDDC Manager certificate import workflows

Why the Other Options Are Incorrect

A. PFX (PKCS#12)Contains private key and certificate bundled together; not the required format for VCF certificate replacement workflows.

B. DERBinary format; VMware Cloud Foundation certificate workflows require Base64 PEM format.

D. P7B (PKCS#7)Does not contain private key; unsuitable for certificate replacement.

Document References (VCF 9.0)

VMware Cloud Foundation 9.0 → Security and Certificate Management

VMware Cloud Foundation 9.0 → Replace Certificates with CA-Signed Certificates

VMware Cloud Foundation 9.0 → Certificate Requirements and Formats

Resetting identity management in VCF requires removal of existing identity configurations, including external identity providers and the Identity Broker configuration. The VCF documentation states that to reset identity services, administrators must remove the SSO configuration, including broker settings, and then reconfigure SSO.

Option B ensures complete cleanup of identity integrations.

Option C re-establishes identity management with the correct configuration.

Disabling (D) or reverting (E) is not a supported reset method. Leaving provisioned users/groups (A) would not fully reset identity management.

To integrate VCF Automation with an external CMDB (such as ServiceNow) for compliance and tracking of Kubernetes or VM resources, the system utilizes a specific extensibility framework. According to the VCF 9.0 documentation on " Integrating VCF Automation for ITSM with ServiceNow " :

Event Subscriptions (D): These act as the trigger mechanism within the VCF Automation Event Broker Service. When a resource (such as a Kubernetes cluster or deployment) is provisioned, an event is published. An administrator creates a subscription to listen for these specific lifecycle events (e.g., Compute.PostProvision or Kubernetes-specific topics) to initiate the registration process.

VCF Operations orchestrator (B): This is the orchestration engine (formerly known as VMware Aria Automation Orchestrator or vRO). Documentation specifies that for CMDB and ITSM compliance, VCF Automation is integrated with VCF Operations orchestrator workflows. These workflows contain the complex technical logic required to:

Separate objects and feed inputs into technical integration tasks.

Handle API tokens and authentication for the external CMDB.

Execute the REST API calls to the CMDB (e.g., to the cmdb_ci_vmware_instance table).

Update custom properties (like serviceNowSysId) back into the deployment for future decommissioning lifecycle events.

Extract from VCF 9.0 Documentation:

" Enterprise users commonly integrate their Cloud Management Platform with an IT Service Management (ITSM) and Configuration Management Database (CMDB) platform for compliance. Following this example, you can integrate VCF Automation with ServiceNow for CMDB and ITSM using VCF Operations Orchestrator Client... This integration uses Event Subscriptions to trigger VCF Operations Orchestrator workflows. "

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).

According to VMware Cloud Foundation 9.0 documentation for VCF Automation (Aria Automation integration):

To deploy workloads to specific NSX segments with VLAN-based selection and IPAM integration, the administrator must:

1️⃣ Configure Network IPAM Settings (Option C)

VCF Automation requires network segments to be associated with IPAM configuration:

“To enable automatic IP allocation for workloads, configure network profiles with gateway, subnet, and IP range details for the associated networks.”

This ensures automatic IP address allocation from the internal IPAM.

2️⃣ Create a Network Profile and Associate Segments (Option D)

VCF Automation uses Network Profiles to group NSX segments and associate them with projects:

“A network profile defines the networks available to a project and includes capability tags that are matched during workload deployment.”

Including all appdev segments in a dedicated network profile ensures logical isolation from other projects.

3️⃣ Use Capability Tags for VLAN Selection (Option F)

VCF Automation uses capability tags to match user input to infrastructure:

“Capability tags applied to networks can be matched in cloud templates to dynamically select networks based on user-defined inputs.”

By applying vlan: < number > tags to each segment, a self-service user can specify a VLAN number that determines which segment is selected during deployment.

Why Other Options Are Incorrect

A – Custom groups are not required for network selection.

B – Tagging segments alone is insufficient without associating them through a network profile.

E – Adding networks to the existing development project violates logical isolation requirements.

Document reference (VCF 9.0):

VMware Cloud Foundation 9.0 → VCF Automation → Projects and Network Profiles

VMware Cloud Foundation 9.0 → Network Profiles and IPAM Configuration

VMware Cloud Foundation 9.0 → Capability Tags and Network Selection

The requirement is to ensure DNS records are created only when a domain name is provided.

Since the blueprint includes a custom property for domainName, the correct conditional logic in the event subscription must validate that this property is not null.

Adding the condition:

event.data.customProperties[ ' domainName ' ] != null

ensures the workflow executes only when the domain name is provided.

Option B validates hostname instead of domain name.

Option A controls workflow blocking, not conditional execution.

Option C relates to cleanup, not creation condition validation.

A documented use case of VCF Operations for networks is Crown Jewel Analysis. VMware Cloud Foundation 9.0 states that administrators can use Crown Jewel Analysis to identify possible lateral movement opportunities for an adversary based on existing network flow paths. Administrators can mark critical VMs or physical IP addresses as crown jewels and then analyze their connectivity, incoming flows, relationships, and potential exposure.

The documentation specifically provides the workflow Plan & Assess > Crown Jewel Analysis, where administrators can analyze reachability scores and determine how many lateral movements might be required to reach critical assets. It can also suggest firewall rules to improve security.

While VCF Operations for networks can generate various reports, option A is too generic. Network automation jobs are a VCF Operations automation capability, not a primary VCF Operations for networks use case. NSX log collection is handled by VCF Operations for Logs rather than Operations for networks.

In VMware Cloud Foundation (VCF) 9.0, the VCF Service Broker is the component responsible for providing a self-service catalog of available services, blueprints, and content to end users in the VM Apps tenant. The documentation explains:

“Service Broker acts as the catalog service for VM-based and cloud-native applications, allowing organizations to expose curated content to end users while applying policies, constraints, and governance.”

VCF Operations Orchestrator (A) provides workflow automation but does not expose services directly in a self-service catalog.

VCF Assembler (B) is used for designing blueprints and application templates but not for publishing them to end users.

VCF Config (D) is responsible for infrastructure configuration management and desired state compliance, not catalog services.

Thus, the correct component for the catalog is the VCF Service Broker.

VCF Operations Continuous Availability (CA) requires a multi-node deployment including a witness node. The standard deployment path involves:

Deploying VCF with High Availability (HA) mode initially (E).

Deploying required nodes including the Witness node (D).

Completing deployment of a Continuous Availability cluster (A).

Connecting to an existing instance (B) does not meet the requirement.

Conversion (C) alone is insufficient without proper CA cluster deployment.

Deploying without VCF Operations (F) violates design requirements.

In VMware Cloud Foundation 9.0, pricing policies are configured within VCF Operations (Costing and Chargeback).

From the VCF 9.0 documentation under Cost and Chargeback Configuration:

“Base Settings define the default cost drivers for CPU, memory, and storage that apply across clusters unless overridden by a custom policy.”

To meet the requirement:

CPU, memory, and storage pricing must be identical across all clusters.

A new policy named Resources must be created and applied globally.

Thus:

1️⃣ Create a new policy under Base Settings for resource cost (Option A)

This satisfies:

Same CPU, memory, and storage cost across clusters.

From the documentation regarding policy hierarchy:

“When a custom cost policy is set as default, it applies to all objects that do not have a more specific policy assigned.”

2️⃣ Set “Resources” as the default policy (Option E)

This ensures:

All clusters inherit this pricing model.

Other unspecified settings fall back to default behavior.

From documentation regarding overrides:

“Specific object types such as clusters can have additional cost components defined through child policies that override parent policy settings.”

3️⃣ Create a child policy under “Resources” for SAP HANA cluster VM setup charges (Option F)

This satisfies:

VM setup charges applied only to SAP HANA cluster.

Other clusters remain unaffected.

All other settings remain default.

Why Other Options Are Incorrect

B – Setting Default Policy as default contradicts requirement to create a new named policy “Resources.”

C – VM setup charges should not be in Base Settings (would apply globally).

D – Incorrect hierarchy; policies are structured under custom policy trees, not under “Default Policy” in this context.

Document References (VCF 9.0):

VMware Cloud Foundation 9.0 → VCF Operations → Costing and Chargeback

VMware Cloud Foundation 9.0 → Policy Inheritance and Overrides

VMware Cloud Foundation 9.0 → Base Settings and Custom Cost Policies

The VCF 9.0 Design Guide highlights that for resiliency across sites with RPO = 0, the recommended approach is a vSAN Stretched Cluster. Documentation states: “Stretched clusters provide site-level resilience by mirroring data across two fault domains (sites). In the event of a full site outage, workloads remain available with no data loss (RPO = 0).” Relocating six hosts to another site creates the two fault domains required for vSAN Stretched Cluster. Options B and C provide backup or redundancy but not synchronous replication with zero RPO. Option D (fault domains) protects against host/rack failures, not entire data center loss. Therefore, the correct solution is to relocate hosts and configure a stretched cluster.

The vSphere 9.0 Resource Management documentation, included within VMware Cloud Foundation 9.0, specifies that Resource Pools are the mechanism to delegate compute resources within a cluster. A resource pool acts as a container of compute resources (CPU and memory) that can be subdivided and assigned to VMs or groups of VMs.

The documentation states:

“Resource pools provide resource isolation, control, and delegation. You can configure reservations, limits, and shares to ensure that mission-critical workloads (such as production VMs) receive guaranteed resources, while development or test workloads consume only available resources.”

This aligns directly with the requirements:

Power on only if resources are available → Achieved via reservations and limits.

Production VMs require guaranteed levels of resources → Enforced using reservations.

Three-tier apps with varying demand → Controlled using shares and limits across multiple resource pools.

Other options are incorrect:

vSphere Availability (A) provides failover, not resource governance.

VCF Operations (B) monitors resource usage but does not allocate or enforce it.

Dynamic Resource Scheduling (D) balances workloads but does not provide delegated, guaranteed allocations per department or application tier.

Thus, the correct feature is vSphere Resource Pools.

Memory tiering in modern vSphere environments allows hosts to utilize different memory technologies (e.g., DRAM and persistent memory tiers) to optimize cost and performance.

The vSphere documentation explains:

“Memory tiering enables efficient placement of memory pages across different memory types, optimizing performance and capacity for memory-intensive workloads.”

The primary use case is for:

Large in-memory databases

Analytics workloads

Memory-intensive applications

Incorrect options:

It does not primarily reduce swap for small VMs (A).

It does not directly boost CPU throughput (B).

It does not address host availability during hardware failure (C).

Thus, memory tiering is best suited for optimizing memory usage for large, memory-intensive workloads.

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.

===========

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).

In VMware Cloud Foundation 9.0, network security and segment integrity are maintained through Segment Security Profiles. These profiles are applied to NSX segments to define what type of traffic is permitted to originate from or be received by the virtual machines attached to that segment.

According to the VCF 9.0 (NSX) Networking and Security Guide:

The Default Segment Security Profile is designed with a " Zero Trust " approach for foundational services. One of its key default settings is DHCP Server Block, which is set to Yes. This is a security measure to prevent " rogue " DHCP servers from being accidentally or maliciously connected to a segment and disrupting the network by handing out unauthorized IP addresses.

When an administrator intentionally places a legitimate DHCP server on a segment:

Segment Security Profile: The " DHCP Server Block " feature resides specifically within the Segment Security Profile, not the IP Discovery profile (which handles how NSX learns IP addresses via ARP/DHCP snooping).

Cloning vs. Editing: In VCF 9.0, the " Default " profiles are system-defined. While some default settings can be edited in certain versions, the architectural best practice and documented procedure for production environments is to Clone the default profile. This creates a custom profile where the DHCP Server Block can be set to No, allowing the DHCP server ' s " Offer " and " ACK " packets to pass through the segment.

Application: Once the cloned profile is modified, it must be manually applied to the specific segment where the virtual desktops and the DHCP server reside.

The VMware Cloud Foundation 9.0 networking design documentation specifies that container workloads running on VMware Kubernetes Service (VKS) with NSX networking require external connectivity via a Centralized Connectivity model. This is implemented using an NSX Tier-0 (T0) Gateway which provides north-south routing to the corporate physical network.

The guide states: “In VKS deployments backed by NSX networking, workloads achieve external reachability through a centralized Tier-0 Gateway, ensuring integration with corporate networking and enterprise services.” This model ensures traffic consolidation, policy enforcement, and simplified routing for Kubernetes workloads.

Round-robin Connectivity is not a supported NSX gateway connectivity model.

Distributed Connectivity refers to east-west NSX overlay communication, not north-south connectivity.

Physical Connectivity is not precise, as workloads do not connect directly to the physical network; instead, they use logical routing.

Centralized Connectivity is the correct model, where the T0 Gateway centralizes external routing for container workloads.

In VMware Cloud Foundation 9.0, the Account and Password Management table explicitly lists the NSX Local Manager local appliance accounts whose passwords are managed (updated/remediated) through VCF Operations UI or API. Under NSX Local Manager, the accounts shown as managed are:

audit — “Update or remediate by using the VCF Operations UI or API.”

admin — “Update or remediate by using the VCF Operations UI or API.”

root — “Update or remediate by using the VCF Operations UI or API.”

These three correspond exactly to options A (admin), C (audit), and E (root).

Document reference (VCF 9.0):

VMware Cloud Foundation 9.0 → Account Management Design → Table 674: Account and Password Management in VMware Cloud Foundation (section showing NSX Local Manager accounts: audit, admin, root).

According to the VCF 9.0 Operations and Monitoring Guide:

Fleet Management: “VCF Operations Fleet Management enables cross-instance monitoring, unifying health and metrics across multiple VCF instances.”

Operations for Networks: “Provides application and network visibility, dependency mapping, and traffic analytics. Required to complete full-stack monitoring.”

Core VCF Operations is already deployed as part of the management stack and does not need to be added separately. Operations for Logs is optional for log aggregation, not mandatory for full-stack observability. The Management Pack Builder (C) is an add-on tool for custom packs, not a required component. Therefore, the correct two to add for full-stack monitoring are VCF Operations Fleet Management (A) and VCF Operations for Networks (E).

For hosts that will be commissioned for a workload domain using VMFS on Fibre Channel as principal storage, the Fibre Channel storage must already be accessible to every ESX host before commissioning begins. VMware Cloud Foundation 9.0 explicitly states: “The VMFS datastore must be mounted on all the hosts before commissioning.”

VCF also requires supported Fibre Channel HBAs and drivers, and the hosts must be able to access the FC array. Fibre Channel does not require a dedicated Ethernet storage network because FC traffic uses Fibre Channel HBAs and the SAN fabric rather than VMkernel-based IP storage networking.

A network pool must exist before host commissioning, but for VMFS-FC it is used for VCF host networking such as management and vMotion; it is not a dedicated Fibre Channel storage network. Therefore, option D is not the specific storage prerequisite asked here. Pass-through mode is also unrelated to FC principal storage.

Comprehensive and Detailed Explanation:

The VCF Operations 9.0 Monitoring Guide specifies: “For any alert definition to be active in the environment, it must be associated with and enabled in an Active Policy.” . Creating symptom and alert definitions only defines conditions; they do not generate alerts until policies include them. REST notification plugins or payload templates are used for outbound integrations, not for enabling alerts. A super metric is only needed for custom composite KPIs, not for native read latency which is a standard metric already available. Therefore, the required step is to enable the alert in an Active Policy so that when the symptom triggers (latency > 1 ms), the alert activates.

In VMware Cloud Foundation 9.0, configuration drift detection is handled through VCF Operations Configuration Management integrated with vSphere Configuration Profiles.

According to the VCF 9.0 documentation:

vCenter Version Requirement (D):Configuration drift monitoring requires vCenter 8.0 Update 3 or later, as this introduces the enhanced configuration profile capabilities necessary for drift comparison.

Create a Configuration Template (E):VCF Operations requires a defined baseline configuration template to compare cluster states against.

Assign the Template to a Policy (F):Policies enforce and monitor configuration compliance. Assigning the template to a policy allows drift detection against the desired state.

Incorrect options:

vCenter 9.0 (A) is not required; 8.0 U3 is sufficient.

A collector (B) is not specifically required for drift detection.

Scheduling drift detection (C) is part of policy evaluation, not a standalone mandatory step.

Configuring vSphere Configuration Profiles (G) is beneficial but not mandatory for drift monitoring via VCF Operations.

Thus, the three required steps are: vCenter 8.0 U3 or later, create a configuration template, and assign it to a policy.

The VCF 9.0 Deployment Guide states:

“Each new VCF instance requires its own management domain consisting of vCenter Server, NSX Manager cluster, and SDDC Manager.”

vCenter (A) is required to manage ESXi hosts and clusters.

NSX Manager (D) provides software-defined networking for the instance.

SDDC Manager (E) is the lifecycle and management component central to each VCF instance.

Supervisor (B) is optional and only enabled if Kubernetes workloads are required. VCF Automation (C) is a separate solution, not part of the core instance bring-up. VCF Installer (F) is the deployment tool, not a persistent component. Thus, the correct components to deploy are vCenter, NSX Manager, and SDDC Manager.

Upgrading from VCF 5.2 to VCF 9.0 involves a significant architectural transition. The VCF 9.0 Upgrade Guide outlines the sequence for environments previously using Aria components.

Deploy VCF Installer (E):VCF 9.0 introduces the VCF Installer appliance to orchestrate deployment and lifecycle operations. This must be deployed first.

Deploy NSX Manager 9.0 (A):NSX must align with the new VCF 9.0 architecture before further component integration.

Manually upgrade Aria Operations to VCF Operations 9.0 (D):Aria Operations transitions to the integrated VCF Operations platform. This is not automatic in major version transitions and requires administrator-driven upgrade.

Options B and F are incorrect because automatic upgrade paths are not supported for this major version shift. Option C is not part of the initial mandatory sequence before platform alignment.

Therefore, the correct three are:

Deploy NSX Manager 9.0, Manually upgrade Aria Operations to VCF Operations 9.0, and Deploy VCF Installer appliance.

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.)

The VCF 9.0 Resource Policy Guide describes IaaS Resource Policies as mechanisms to enforce deployment rules for Supervisor-based Kubernetes clusters.

For the production project, only Kubernetes resources are allowed, so administrators must disallow VM deployments (A).

To tolerate a single control plane node failure, production clusters should use multi-control-plane node templates, ensuring availability (B).

In the development project, resources should be minimized, so a single-control-plane node policy is enforced (D), which reduces overhead.

Incorrect options:

Organization-wide policies (C and F) would apply to both projects, which is not desired since dev and prod have different requirements.

Enforcing single-control-plane nodes in production (E) contradicts the requirement for failure tolerance.

Thus, the correct approach is: Disallow VMs in production, enforce multi-control-plane clusters in production, and enforce single-control-plane clusters in development.

The VCF Automation documentation defines its primary use cases as:

Self-Service Catalog – “VCF Automation Service Broker provides a catalog for developers and operators to request services and blueprints.”

Application Dependency Mapping – achieved through integration with VCF Operations for Networks. The guide highlights: “Developers can discover application relationships and map dependencies through automated workflows in VCF Automation.”Alerting (A) is handled by VCF Operations, not Automation. VPC implementation (B) and Private AI (D) are supported solutions but not direct Automation use cases. Therefore, the correct answers are C (Self-Service Catalog) and E (Application Dependency Mapping).

VCF 9.0 licensing is managed through VCF Operations and the VCF Business Services console. The product requires periodic license updates even in connected mode. The documentation states explicitly: “You must update your licenses at least once every 6 months (180 days). If license usage data is not submitted… your licenses are treated as expired, your hosts are disconnected from the vCenter instance, and you cannot start any workload operations.” This language is repeated in the Licensing Overview and Upgrade/Registration sections, confirming the 180-day requirement applies to both connected and disconnected modes (in connected mode usage submission is automated, but you still must perform an update action). Therefore, the correct interval is 180 days.