In the context of distributing connections across multiple broker VMs (such as Citrix Delivery Controllers or Horizon Connection Servers) without introducing complex third-party infrastructure dependencies like strict SDN overlays (Option A), Round-robin DNS is the standard supported method for connection distribution mentioned in basic Nutanix EUC architecture guides.
While enterprise production environments often use dedicated External Load Balancers (like Citrix ADC), Option A implies the mandatory use of Flow Virtual Networking (an overlay SDN solution) to achieve this, which is not a standard requirement for simple broker load balancing. Therefore, among the available choices, creating multiple DNS A-records for the broker FQDN (Round-robin DNS) is the valid mechanism to distribute incoming user traffic across the available broker nodes.

Comprehensive and Detailed Explanation From Exact Extract of Nutanix End User Computing documents:
According to the latest Nutanix Security Guide (AOS 6.x and later) regarding SCMA (Security Configuration Management Automation):
* OS Evolution: Modern Nutanix Controller VMs (CVMs) in current Long Term Support (LTS) releases (AOS 6.5 and above) utilize an operating system based on RHEL 8 / CentOS 8.
* STIG Compliance: Consequently, the built-in SCMA policies are updated to check and enforce compliance against the RHEL 8 STIG (Security Technical Implementation Guide).
* Correction Note: Older documentation (AOS 5.x) referenced the RHEL 7 STIG. However, per your request for "latest knowledge" applicable to current supported environments, the CVM is compliant with RHEL 8 STIGs. If this question appears on a legacy exam version, the answer might still be listed as C (RHEL 7), but B is the technically correct answer for modern Nutanix software.

To enable Secure Boot and vTPM on a Nutanix AHV cluster, specific VM configuration requirements must be met. According to the Nutanix AHV Administration and Security guides, Secure Boot prevents malicious code from loading during the boot process by ensuring that only signed drivers and OS loaders are used.
When configuring a VM for Secure Boot, the machine type must be set to q35. The standard legacy machine type (i440fx) does not support the necessary features for Secure Boot and vTPM operations in this context.
Documentation for creating or updating a VM with these features via the Acropolis CLI (aCLI) explicitly includes the parameter machine_type=q35 in the command string (e.g., vm.create vm-name machine_type=q35 uefi_boot=true secure_boot=true virtual_tpm=true). Furthermore, if an administrator attempts to update an existing VM to enable Secure Boot without this machine type, the operation will fail or require the conversion, as Secure Boot and vTPM are supported specifically on the Q35 virtual hardware platform combined with UEFI boot mode.
Legacy BIOS (Option C) is explicitly unsupported for Secure Boot, as UEFI is a strict prerequisite. Hardware TPM pass-through (Option D) is not used; instead, AHV utilizes a software-based vTPM that keeps the crypto keys independent of the underlying hardware to allow for VM mobility.
Relevance of the video: The video provides a step-by-step visual guide on enabling Credential Guard and Secure Boot for Windows VMs on Nutanix AHV, which directly illustrates the configuration steps and requirements discussed in the question, including the necessary VM settings.
Enabling Credential Guard for AHV Windows VMs

Frame is a cloud-based desktop-as-a-service platform that allows users to access Windows applications and desktops from any device1. A license server is a server that hosts a network licensing manager for software that requires licenses to run2. Frame supports using a utility server as a license server for Frame desktops1. A utility server is a stand-alone, general purpose Windows server that can be configured and managed from the Frame dashboard1.
https://docs.frame.nutanix.com/platform/admin/utility-servers/

Comprehensive and Detailed Explanation From Exact Extract of Nutanix End User Computing documents:
According to Nutanix Validated Designs (NVD) for Citrix DaaS:
* Control Plane: The requirement to "reduce brokering infrastructure footprint" dictates the use of Citrix DaaS (formerly Citrix Cloud), which offloads the Delivery Controllers and SQL databases to the Citrix cloud service, leaving only the lightweight Cloud Connectors on-premises.
* Placement: In a large multisite architecture using the standard "Block and Pod" design, Nutanix recommends separating Management/Infrastructure functions from Workload functions.
* Best Practice: Cloud Connectors are critical infrastructure components. They should be deployed on the AHV Infrastructure Clusters (Management Clusters) in each resource location, rather than the Workload clusters, to ensure they are protected from resource contention caused by user desktops and to maintain a clean separation of duties.