VMware Cloud Foundation 9.0 Administrator 2V0-17.25 Exam Practice Test

Answer : D

Velero is an open-source Kubernetes backup and restore solution integrated into VMware Cloud Foundation for Kubernetes management. The VCF 9.0 Kubernetes Services Documentation describes it as:

''Velero provides backup, recovery, and migration of Kubernetes cluster resources and persistent volumes.''

Key functionality includes:

Backup and restore of Kubernetes objects such as deployments, services, and namespaces.

Data protection for persistent volumes via storage snapshots.

Migration capabilities across clusters.

Analysis of incorrect options:

Publishing DNS records (A) is handled by CoreDNS or external DNS integrations, not Velero.

Monitoring cluster services (B) is the role of Kubernetes health checks and observability tools like Prometheus, not Velero.

Collecting logs and data (C) is done by logging stacks such as Fluent Bit or VCF Operations for Logs.

Therefore, Velero's primary role is backup and restore of Kubernetes clusters.

Answer : C

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

While the workbook is used to collect information, the validation of those inputs is performed by the 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.

===========

Answer : C

The VCF 9.0 Operations Guide -- Views and Reports explains the four types of views available for custom dashboards:

Object Relationship View: Displays dependencies and hierarchy between objects (for example, VMs, hosts, datastores) but does not provide exportable tabular data.

Scoreboard View: Provides a high-level KPI visualization of a few key objects but is not intended for large tabular exports.

List View (Correct): Displays tabular data across many objects, such as CPU, memory, and disk metrics for VMs. The guide states: ''List views are useful when you want to compare metrics across multiple objects and can be exported to CSV for further analysis.''

Trend View: Focuses on historical data and growth over time, but export to CSV is not its primary purpose.

Because the security team requires both tabular comparison of VM resource usage and the ability to export the data to CSV, the List View is the only option that meets both requirements.

===========

Answer : B, C, F

VCF provides integrated automation and orchestration for Day 0--2 operations, including networking: VCF is a ''full-stack IaaS'' with ''automation and orchestration to simplify Day 0, Day 1, and Day 2 tasks.'' VCF supports modern apps: users can provision ''VMs'' and ''Kubernetes workloads'' from self-service services, proving both VM and container support. Multi-tenancy with strong isolation is native: Organizations are ''secure and isolated'' boundaries; All Apps organizations run ''virtual machines (VMs), Kubernetes... multiple tenants with secure infrastructure isolation.''

Incorrect choices: VCF is not limited to vSAN only (supports VMFS/NFS/CNS as documented elsewhere) and does not rely on manual scalability---automation is core. Compliance is provided within the private cloud, not only by a CSP.

Answer : A, E

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

Answer : C, D, E

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

Answer : B, C, F

The VCF 9.0 Operations Policies Guide explains how to extend and scope monitoring policies:

Create a child policy under the existing Organization Policy (C): Policies can inherit settings from parent policies. By creating a child policy under Organization Policy, administrators can apply additional metrics without overriding global policies.

Create a Custom Group (F): Custom Groups allow dynamic membership based on naming conventions or criteria. In this case, business-critical VMs can be grouped automatically by naming schema.

Assign the Custom Group to the new child policy (B): This ensures that the additional metrics only apply to the business-critical VMs in the Custom Group.

Incorrect options:

Custom Datacenters (A, D) are not required; the grouping requirement can be met with Custom Groups.

Creating the policy under Base Settings (E) would apply globally rather than inheriting from the Organization Policy.