To configureVMware Cloud Foundation (VCF) Operations for logsso that it can send notifications and metrics, administrators must use theIntegrations workflow inside VCF Operations.
* You configure integrations centrally from theAdministration > Integrationspage in VCF Operations.
* Here you add theVCF Operations for Logs data source, configure credentials, and set up Webhooks for alerts.
* Once integration is completed, VCF Operations for Logs data can be consumed in VCF Operations dashboards and used for notifications and metrics.
This process is not launched directly from "VCF Operations for Logs," but rather fromVCF Operations itself, where all integrations (vCenter, vSAN, NSX, and Logs) are centrally managed.
References:
VMware Cloud Foundation 9.0.2 -Integrating Data Sources with VCF Operations VMware Cloud Foundation 9.0.3 -Configure VCF Operations for logs integration

To allowActive Directory domain users(corp.local) to authenticate in vCenter with domain credentials:
* The correct method is configuringActive Directory over LDAP as an identity source. (D)
* This uses thedefault AD protocol (LDAP/Kerberos)without requiring SAML or OIDC federation.
Other options:
* A. Adding domain controller certificate# Needed for LDAPS but not the main step.
* B. Identity Federation with SAML# Requires federation, not allowed per requirements.
* C. OpenID Connect (OIDC)# Used for external IdPs, not traditional AD auth.
References:
VMware vSphere 9.0 -Configuring Active Directory Identity Sources
VMware Docs: Add AD over LDAP as Identity Source

To supportcontainerized workloads within VMware vSphere Foundation (VVF), the essential component isvSphere Kubernetes Service (vSphere with Tanzu).
* Provides nativeKubernetes integrationwith vSphere clusters.
* Enables runningPods, Tanzu Kubernetes clusters, and containerized workloadson vSphere infrastructure.
Other options:
* VCF Automation (A):Automates VCF lifecycle but not containers.
* VCF Fleet Manager (B):Manages multi-instance environments, not workload containers.
* VCF Operations (C):Provides monitoring/analytics but not container runtime.
References:
VMware vSphere 9.0 -vSphere with Tanzu Overview
VMware Docs: Kubernetes in vSphere (Tanzu)

InVCF Operations, theCertificate Revocation List (CRL) tabis visible only whenStandard Certificate Validationis activated in Global Settings.
* Once enabled, administrators can view the CRL tab and monitor revoked certificates.
Other options:
* A. External Event Based Active Symptoms# Related to alerting, not CRL.
* C. Threshold for Expiration Alert# Configures warnings, not CRL visibility.
* D. Not available under vSphere Foundation license# Incorrect; CRL is available if validation is enabled.
References:
VMware Cloud Foundation 9.0 -Certificate Validation Settings in Operations VMware Docs: Managing Certificates in vROps

To ensurecompromised users cannot access vCenter resources:
* Assign theNo Accessrole at the vCenter level.
* Enable propagationso this restriction applies to all child objects.
* This guaranteeszero permissionsfor SUSPECT_USERS.
Other options:
* B. Administrator with uncheck propagate# Still gives dangerous access at root level.
* C. Disconnect Active Directory# Disrupts all AD users, not just suspect ones.
* D. Read-only role# Still grants access, not acceptable during investigation.
References:
VMware vSphere 9.0 -Roles and Permissions Best Practices
VMware KB 1025569 -Assigning the No Access Role in vCenter