In Nutanix AHV networking, the default bond mode for a virtual switch is Active-Backup. In this mode, all traffic flows through a single active physical uplink, while other uplinks remain in standby mode to be used only in the event of a failure. This explains the observation that "only one of the physical NICs... is carrying VM traffic." To utilize multiple physical uplinks simultaneously and balance the traffic, the administrator must change the bond mode to an Active-Active configuration. In AHV, this is achieved by configuring the bond mode to Balance-SLB (Source Load Balancing) or Balance-TCP (LACP). These modes distribute VM traffic across all available physical interfaces in the bond, thereby balancing the load.

In the context of migrating or setting up Citrix MCS workloads on Nutanix AHV, the workflow relies on the Machine Catalog as the provisioning unit.4 After the administrator converts the base image (Master Image) to the Nutanix AHV format, the correct procedure to deploy "many VMs" (non-persistent pooled workloads) is to create a New Machine Catalog within Citrix Studio.5 During this creation process, the administrator selects the converted image (or a snapshot of it) as the template source.6 MCS then utilizes this single image to clone and provision the multiple non-persistent VMs requested. Therefore, provisioning "New catalogs on AHV with the converted image" is the accurate description of the required task.

Comprehensive and Detailed Explanation From Exact Extract of Nutanix End User Computing documents:
According to Nutanix VDI Troubleshooting and Performance Tuning best practices:
* Symptom Analysis: "Sluggish mouse and keyboard response" is a classic symptom of high CPU contention or high Latency on the host or VM. Since the environment was previously stable ("No additional virtual desktops added") and the change was "dramatic," it points to a new process consuming resources unexpectedly.
* The "Agent" Factor: In non-persistent VDI environments, a common cause for sudden performance degradation affecting an "entire department" is an Antivirus or Security Agent running a scheduled scan or a signature update simultaneously across all clones. This creates a "storm" of IOPS and CPU usage (often called an AV storm), starving the user sessions of the resources needed for basic input processing (mouse/keyboard).
* Why not others?
* Unoptimized master image (B): This would cause poor performance from day one, not a
"dramatic change" after 60 days of stability.
* Legacy drivers (C): Drivers do not degrade suddenly; they would cause issues from the time of installation.
* Over-provisioning (D): This usually results in gradual degradation as user concurrency increases, not a sudden cliff-edge drop in performance if user counts haven't changed.

The schedule has two rows: one for Weekdays and one for Tuesday and Thursday.
Each row has a column for Instances, which indicates how many instances should be running during that time range.
Each row also has a column for Time Range, which indicates the start and end time for running the instances.
The time range is expressed in 24-hour format, where 00:00 means midnight and 24:00 means midnight of the next day.
According to the exhibit, the schedule Dev has the following settings:
* On Weekdays (Monday to Friday), five instances are running from 09:00 am till 05:00 pm.
* On Tuesday and Thursday, five instances are running from 00:00 am till 24:00 pm.

Comprehensive and Detailed Explanation From Exact Extract of Nutanix End User Computing documents:
According to Citrix Virtual Apps and Desktops architecture documentation utilized in Nutanix EUC designs:
* VDA Functionality: The Virtual Delivery Agent (VDA) is the essential software component that must be installed on every machine (virtual or physical) that delivers applications or desktops.
* FMA Role: The VDA registers with the Delivery Controller (Broker) and manages the FMA (FlexCast Management Architecture) connection between the machine and the user device. It establishes and manages the HDX connection, allowing the Citrix Workspace app (on the client side) to connect directly to the desktop session.
* Distinction:
* Citrix Workspace app is installed on the client device (endpoint), not the virtual desktop.
* VirtIO drivers are lower-level drivers for disk/network I/O virtualization on AHV, not FMA connection brokers.
* NGT provides Nutanix-specific fabric features (SSR, FLR), not Citrix session connectivity.