NCA-7.5 Nutanix Certified Associate (NCA) 7.5 Exam Questions and Answers

Replication Factor is configured on a storage container. It determines how many copies of the data associated with that container are maintained across the Nutanix distributed storage fabric. The official Prism 7.5 definition states that replication factor is the number of copies of data maintained on a storage container within a cluster. For example, RF2 maintains two copies, whereas RF3 maintains three copies and consequently requires a cluster capable of providing the corresponding fault-tolerance level.

A storage pool aggregates physical storage resources, but it does not independently establish the replication policy for guest data. A protection domain defines which entities are protected and controls snapshot or replication schedules for disaster recovery; it is not the administrative location for configuring local data-copy count. “Replication Policy” is therefore a distractor representing data-protection behavior rather than an AOS storage entity.

Replication factor also affects usable capacity because additional copies consume physical storage. Administrators must therefore align the container’s replication factor with the cluster’s available fault domains and required resilience. Prism requires RF3 to be configured individually for the applicable containers after the cluster supports the necessary fault-tolerance level.

NHCF/NCA reference: Cluster storage configuration, storage containers, distributed storage, and data resilience. Official references: Replication Factor and Replication Factor Configuration .

===============

Deduplication reduces storage consumption by identifying duplicate data blocks and consolidating them so that redundant physical copies do not need to be retained. AOS uses fingerprints to recognize eligible duplicate blocks. Capacity deduplication applies this process to persistent data within a storage container, reducing the physical space consumed by workloads containing substantial repeated content.

Compression is different: it encodes a data block into a smaller representation but does not eliminate identical blocks by replacing them with a shared instance. Erasure Coding reduces the storage overhead associated with maintaining replicated cold data by substituting parity information for certain redundant copies. It is a resilience and capacity-efficiency mechanism, not duplicate-block elimination. Capacity Tiering concerns placement across storage tiers and does not consolidate identical content.

Deduplication should be enabled selectively because fingerprint generation and metadata processing introduce overhead. It is most beneficial for workloads with significant duplicate data, such as appropriate persistent-desktop or full-clone environments. Workloads already using space-efficient Nutanix clones may receive limited additional benefit.

The defining phrase in the question is “eliminating identical data blocks,” which is the standard function of deduplication.

NHCF/NCA reference: AOS storage efficiency, capacity deduplication, compression, and erasure coding. Official references: Deduplication and Storage Components .

===============

The alert title is the navigation control used to open the alert details page. That page consolidates the information needed to investigate the condition, including the alert description, severity, creation time, affected entity, possible causes, and recommended corrective actions. Nutanix documentation states that an administrator displays an alert’s details by clicking its title.

The Source Entity link leads to information about the affected object—for example, a disk, controller VM, host, or cluster. Entity information may be useful later in the investigation, but it is not the direct route to the alert-specific cause and resolution guidance requested in the question. The selection box merely selects the record for supported bulk or administrative operations. Email Configuration controls alert-notification delivery and does not diagnose the active alert.

Copying the title into a public search engine is also inferior to using the contextual information already maintained in Prism. Search results may apply to different software releases or environmental conditions, whereas the details page is connected to the actual alert instance and entity. Therefore, clicking the alert title is the fastest supported diagnostic path. References: Prism Central – Alerts Summary View and Prism 7.5 – Alert Details . NHCF alignment: interpreting and investigating alerts.

===============

The LCM Framework must be current before the remaining dark-site software or firmware upgrade workflow is performed. The framework supplies the orchestration logic, compatibility metadata processing, inventory functionality, and update mechanisms that Life Cycle Manager uses to evaluate and execute component upgrades. An outdated framework may not correctly recognize newer bundles, dependencies, compatibility rules, or supported upgrade paths.

For the recommended dark-site sequence, Nutanix directs administrators to perform an LCM inventory first. That operation checks the installed environment and updates the LCM Framework when the required framework bundle is available. Nutanix further specifies that no other software component should be upgraded during this initial framework step. NCC is upgraded and run afterward so that current health checks can be executed before broader maintenance proceeds.

Foundation VM is principally associated with imaging, discovering, and deploying Nutanix nodes; it is not the first component in an established cluster’s LCM upgrade order. MSP is likewise not the controlling lifecycle framework for this procedure. Therefore, the correct operational sequence begins with the LCM Framework. Reference: LCM – Recommended Upgrade Order for the Dark Site Method . NHCF alignment: software maintenance, LCM inventory, and lifecycle sequencing.

===============

The Remote Support Tunnel establishes a controlled remote connection through which authorized Nutanix Support personnel can access a cluster and assist with diagnosis and troubleshooting. The customer retains control over whether the tunnel is enabled, and it can be opened for a defined period rather than operating as an unrestricted permanent connection. Nutanix documentation describes the feature as a remote support connection and allows administrators to start the tunnel for a limited duration.

The tunnel is part of the support workflow rather than a workload data service. Moving applications from an on-premises environment to a public cloud is handled through migration products and hybrid-cloud mobility capabilities such as Nutanix Move or Nutanix Cloud Clusters workflows. Replication between sites is provided through protection policies, protection domains, recovery plans, or other disaster-recovery services. Encryption or isolation between guest VMs is addressed through virtual networking, security policies, and microsegmentation—not the support tunnel.

The decisive distinction is the tunnel’s administrative purpose: it gives Nutanix technical support temporary connectivity to investigate cluster problems. Reference: Prism 7.5 – Remote Support Connections . NHCF alignment: leveraging Nutanix support functions and troubleshooting services.

===============

Once CPU consumption, CPU contention and memory utilization have been reviewed and found stable, storage latency becomes the next relevant performance domain. A VM can have adequate compute resources yet remain slow because guest read or write operations are waiting for the storage path. High latency may arise from workload contention, abnormal I/O patterns, a storage-controller issue, or an underlying infrastructure condition.

Prism exposes VM and infrastructure metrics including IOPS, bandwidth, read latency, write latency and total I/O latency. The administrator should correlate the VM’s latency with its IOPS and throughput, then compare those values with storage-container, host and cluster-level metrics over the same interval. This determines whether the delay is isolated to the VM or reflects a broader storage condition.

License expiration may affect access to licensed features, but it is not the primary diagnostic explanation for an actively running VM’s I/O responsiveness. RBAC controls administrative permissions rather than guest workload performance. Container sizing is not a standard immediate troubleshooting metric; the measurable symptom to examine first is latency.

NHCF/NCA reference: Cluster Performance—analysis charts, reports and workload-performance interpretation; NCA Section 4, “Review and interpret workload performance.” Official references: Prism 7.5—Performance Monitoring , Prism Central 7.5—VM Summary Metrics .

===============

The supported Prism Element workflow for gathering diagnostic data is the Collect Logs feature. From the Health dashboard, the administrator opens the Actions menu, selects Collect Logs, identifies the relevant nodes and components, specifies the required time range or collection parameters, and starts the log-collection task. The resulting archive can then be associated with or uploaded for the Nutanix Support case.

Pulse is a proactive support and telemetry capability that periodically provides diagnostic system information to Nutanix. It does not automatically transmit every detailed NCC or component log required for a specific investigation. Nutanix documentation notes that when Pulse data is insufficient for diagnosis, Support may request a separate diagnostic log collection.

“Export Logs” and “Download Logs in Prism Central” are not the documented names of the NCC collection workflow described in the question. The explicit Health dashboard operation is Collect Logs. This process also allows the administrator to control which nodes and components are included, preventing irrelevant data from unnecessarily enlarging the support bundle. Reference: Prism 7.5 – Collecting Logs Using Prism Element . NHCF alignment: collecting support data, using health functions, and collaborating with Nutanix Support.

===============

A Nutanix storage pool is the physical aggregation of disks contributed by the nodes in a cluster. The disks may come from one or more storage tiers, such as NVMe, SSD or HDD, depending on the supported hardware configuration. Each physical storage device belongs to a storage pool, and Nutanix generally recommends a single storage pool per cluster so AOS can optimize capacity and performance across the available devices.

A storage container is a logical subdivision of storage capacity presented from the storage pool. Administrators apply settings such as compression, deduplication and other storage policies at the container level. Therefore, a container consumes capacity from a pool but is not itself the grouping of physical disks.

A volume group is a collection of virtual disks exposed to one or more VMs or external clients as block storage. “Disk group” is not the Nutanix AOS abstraction defined by the question.

The hierarchy is consequently physical disks, then the storage pool, followed by logical storage containers and workload-facing virtual disks or volume groups.

NHCF/NCA reference: Storage Concepts—AOS storage architecture, storage pools, containers and storage tiers; NCA Section 2, “Discuss storage operations.” Official references: Prism 7.5—Storage Components , AOS 7.5—Nutanix Software Configuration .

Nutanix Field Advisories communicate technically significant issues identified in deployed environments. An advisory typically describes the affected products or versions, the conditions under which the issue occurs, its potential operational impact and any available workaround, mitigation or permanent resolution. Option D therefore represents the advisory’s purpose accurately.

Field Advisories are part of the operational knowledge used by Nutanix Support and Insights. Insights discoveries can compare cluster telemetry and configuration information against known Field Advisories to determine whether a particular environment may be exposed. Where possible, the resulting discovery includes recommended corrective action or directs the administrator to the relevant upgrade, configuration change or support process.

Product announcements and pricing information are commercial communications, not Field Advisories. Certified hardware information is maintained through compatibility lists and platform qualification resources. New-cluster installation procedures belong in Foundation, deployment and installation documentation.

Administrators should review applicable Field Advisories during routine health reviews and before major maintenance because an advisory can affect upgrade selection, risk assessment and remediation priority.

NHCF/NCA reference: Support Portal, Insights, advisories and proactive support functions; NCA Section 4, “Leverage support functions.” Official references: Support Portal Insights Discovery Overview , Nutanix Insights and Support Knowledge .

===============

Nutanix X-Ray is an automated testing and benchmarking framework that runs repeatable scenarios against hyperconverged infrastructure targets. It uses realistic workload generators and controlled infrastructure events to evaluate performance, resilience, scalability, data integrity, and availability. Its scenarios can simulate conditions such as VM cloning, snapshots, migrations, node failures, node power-offs, and sustained storage workloads.

X-Ray is intended for evaluation and test environments rather than active production clusters. The resulting metrics and reports allow architects and administrators to compare configurations and determine how an environment behaves under representative production-style demand and failure conditions.

Nutanix Move migrates workloads between supported platforms and does not benchmark infrastructure behavior. Nutanix Collector gathers environmental information for assessment and sizing activities but does not generate simulated application loads. Nutanix Foundation images nodes and deploys or configures clusters; it is not a performance-testing framework.

The requirement to test behavior under simulated load therefore maps directly to X-Ray’s scenario-based testing model. References: Nutanix X-Ray FAQ and X-Ray 4.4 – Test Scenarios . NHCF alignment: identifying Nutanix assessment, deployment, migration, and testing tools.

===============

Nutanix AOS automatically disables compression when metadata usage becomes high. The Prism 7.5 storage documentation explicitly identifies this condition and states that an alert is generated when automatic disablement occurs. Consequently, option D is the verified answer, replacing the supplied answer A.

Compression requires AOS metadata resources to track compressed extents and the associated data layout. If metadata consumption reaches a protective threshold, continuing compression could place additional pressure on the metadata services required for normal storage operation. AOS therefore prioritizes platform stability and metadata availability by disabling compression and notifying the administrator. The corresponding health alert should be investigated to determine why metadata usage has increased and whether workload characteristics or another storage condition requires remediation.

High write activity may increase storage workload and influence when post-process compression can execute, but it is not the documented automatic-disable trigger in this question. High reads similarly do not directly cause compression to be disabled. High physical-capacity consumption generates its own capacity warnings and corrective requirements but is distinct from the metadata threshold governing compression.

NHCF/NCA reference: Storage Concepts—capacity optimization, compression and storage-container administration; NCA Section 2, “Discuss storage operations.” Official references: Prism 7.5—Compression , Prism 7.5—Storage Alert Reference .

===============

CPU Ready Time measures the percentage of time that a VM’s virtual CPUs are ready to execute but cannot be scheduled on physical CPU resources. It is therefore a direct indicator of processor contention or CPU oversubscription. A VM can show moderate CPU utilization while still suffering poor response times because its vCPUs are waiting for execution time.

Prism Central supports user-defined alert policies based on infrastructure metrics, including VM CPU Ready Time. The administrator can define a threshold and evaluation period so that an alert is generated when scheduling delays exceed an acceptable level during peak demand. This produces proactive notification instead of requiring periodic manual review.

Pulse sends diagnostic information to Nutanix Support but does not create the workload-specific threshold requested. Increasing vCPU allocation without first validating contention may worsen CPU Ready Time because the hypervisor must schedule additional virtual processors. Reviewing average CPU usage is retrospective and does not automatically generate an alert. The most precise control is therefore a custom CPU Ready alert. References: Prism Central 7.5 – Alert Metrics and Intelligent Operations – Chart Metrics .

===============

Nutanix Guest Tools must be installed and configured on the protected Windows VM when required by the AHV Metro and recovery-plan workflow. Nutanix DR documentation specifies supported NGT versions as a guest-level prerequisite for protected entities participating in relevant cross-cluster operations.

NGT supplies guest integration that allows the Nutanix platform to coordinate VM-specific operations during protection and recovery workflows. It can support application-consistent processing, guest communication and the handling of attached resources where applicable. For Windows workloads, installing NGT ensures that the guest participates correctly in the supported Nutanix DR workflow rather than being treated solely as an unmanaged virtual-machine object.

VirtIO supplies the storage and network drivers required for Windows to operate efficiently on AHV, but it is not the Metro-specific guest integration requested by the question. VMware Tools applies to VMware guest integration and is not the corresponding AHV component. The Witness service is an external availability component used to arbitrate failures between Metro sites; it is not installed inside each Windows VM.

NHCF/NCA reference: Nutanix Guest Tools, VM protection and Nutanix Disaster Recovery capabilities; NCA Section 1, “Recognize Nutanix solutions, use cases and features.” Official references: Prism Central 7.5—Creating a Recovery Plan , Prism Central 7.5—Cross-Cluster Live Migration .

===============

UTC is the recommended timezone selection when creating a Linux VM on AHV. Nutanix specifically states that the real-time clock of a Linux VM must operate in UTC. Selecting the UTC timezone ensures that the guest’s hardware-clock interpretation is consistent with Linux conventions and avoids time shifts caused by local timezone or daylight-saving changes.

Time consistency is essential for authentication, application logging, distributed databases, monitoring, certificate validation and event correlation. The guest operating system can still display a regional timezone to users at the application or operating-system level while maintaining its underlying hardware clock in UTC.

“Local” can cause the guest to interpret the virtual hardware clock according to a regional offset, producing incorrect timestamps after migration, reboot or daylight-saving transitions. “Cluster” is not a supported timezone designation for this VM setting. RTC means real-time clock and describes the clock mechanism rather than a selectable geographic timezone.

The VM should also use a reliable NTP source after deployment so its operating-system time remains synchronized.

NHCF/NCA reference: VM Management—creating and configuring Linux virtual machines; NCA Section 2, “Describe VM tasks.” Official references: Prism 7.5—Creating an AHV VM , Prism 7.5—Time-Synchronization Recommendations .

===============

Active-Backup is the default bond configuration for newly created AHV clusters. In this mode, one physical uplink actively forwards traffic while another eligible uplink remains available as a standby. If the active link fails, AHV moves traffic to the backup link, providing straightforward network redundancy without requiring LACP or a switch-side link-aggregation configuration.

The principal advantage of Active-Backup is operational compatibility. Because only one uplink forwards traffic at a given time, the upstream switch ports do not need to be combined into a link aggregation group. However, the configuration does not aggregate the bandwidth of multiple physical NICs during normal operation.

Balance-slb provides active-active source load balancing using MAC pinning and can improve aggregate host bandwidth without requiring LACP. Balance-tcp uses active-active LACP and requires matching configuration on the physical switches. Both are deliberately configured alternatives rather than the default. “No Uplink Bond” would eliminate bond-level redundancy and is not the standard newly created cluster configuration.

NHCF/NCA reference: AHV networking basics, virtual switches, uplinks and bond types; NCA Section 2, “Identify virtual networking tasks.” Official references: Prism 7.5—Network Configuration , Prism Central—Creating a Virtual Switch .

===============

The default scheduled time for LCM automatic inventory and automatic update activity is 3:00 AM. This setting is used when Auto Inventory and Auto Update are enabled for a connected site. Administrators can modify the schedule when 3:00 AM does not align with the organization’s operational or maintenance requirements.

Automatic inventory refreshes LCM’s knowledge of installed software and firmware components and retrieves current update metadata from the configured Nutanix source. Nutanix also specifies that if an inventory operation has already completed within the preceding 12 hours, LCM can skip the scheduled auto-inventory because its component information remains sufficiently current. Automatic update in this setting applies to the supported automatically managed component—particularly Nutanix Cluster Check—rather than authorizing every available AOS, AHV, or firmware upgrade without administrator review.

The other answer choices do not represent the documented default. However, administrators should treat 3:00 AM as a configurable platform default rather than an assumed maintenance window. They must verify the configured schedule, time context, Internet connectivity, and update policy for the specific environment.

NHCF/NCA reference: LCM settings, connected-site configuration, automatic inventory, and automatic NCC updates. Official references: Specifying Connected-Site Settings and LCM Settings for Connected Sites .

Nutanix classifies this condition as Priority 3, or P3. The official support definition describes P3 as a normal-priority case involving a minor inconvenience or an occasional, non-critical issue that requires resolution but has not materially reduced productivity. Its defining language includes: “A non-critical loss of use with medium to low impact.” A short-term workaround is generally available.

P1 is reserved for emergency conditions in which production systems are unavailable or unusable, critical functionality is down, significant data loss is occurring or threatened, and no procedural workaround exists. P2 applies when production remains available but experiences major degradation or the loss of important functionality, materially affecting part of the organization’s operations. P4 covers low-impact informational requests, including questions about documentation, procedures, configuration, or account setup.

The scenario uses the defining P3 wording rather than merely describing a general support question. It therefore cannot be reduced to P4, while its non-critical and limited-impact characteristics exclude P1 and P2. The correct priority is C. Reference: Nutanix Support Policies and Priority Definitions . NHCF alignment: support-case creation, priority selection, and effective escalation practices.

===============

AOS supports live vDisk migration between storage containers while the vDisk remains attached to a powered-on guest VM. The VM does not need to be shut down or deleted. This capability allows administrators to move individual vDisks or all eligible vDisks associated with a VM to a container providing different storage settings.

Storage-container properties can include replication factor, encryption, compression, deduplication, and erasure coding. Migrating a vDisk to another container is therefore a controlled method of changing the storage characteristics applied to that disk without interrupting the running workload.

The operation does not require cluster maintenance mode, and existing snapshots do not universally need to be deleted. However, important restrictions apply. Migration cannot proceed when an applicable Prism Central storage policy is configured for the associated VM. Protected VMs may also need to be removed from their protection domain or protection policy before migration. The target container must have sufficient free capacity, and operations such as cloning, resizing, or taking new snapshots may be blocked while migration is active.

The essential requirement tested is that the VM may remain powered on during the storage-container migration.

NHCF/NCA reference: Storage operations, vDisk placement, storage containers, and live migration. Official references: Live vDisk Migration , Migrating a vDisk , and Storage Policy Limitation .

===============

Nutanix Network Visualizer uses Link Layer Discovery Protocol or Cisco Discovery Protocol to determine the relationship between an AHV host interface and the corresponding first-hop physical-switch port. It can then use configured SNMP access to retrieve additional switch, port and operational statistics. The combined protocol set in option C therefore enables both topology discovery and the display of useful physical-network information.

LLDP is vendor-neutral, while CDP is primarily associated with Cisco networking equipment. Either protocol can advertise the local port identity needed to construct the topology mapping. SNMP supplements that discovery by providing management-plane information obtained from supported switches. Nutanix documentation notes that when LLDP or CDP information is unavailable, SNMP data may be used to assist mapping, although complete and accurate visualization depends on supported devices and appropriate configuration.

BGP and OSPF exchange routing information; they are not the protocol set used by Network Visualizer for host-to-switch discovery. DHCP and PXE provide address allocation and network boot services. STP prevents Layer 2 loops, while VTP distributes VLAN information in certain Cisco environments.

NHCF/NCA reference: Networking—monitoring networks in Prism Element and Prism Central; NCA Section 2, “Identify virtual networking tasks.” Official reference: Prism 7.5—Network Visualization Prerequisites .

===============

Life Cycle Manager supports software updates on a single-node cluster but does not support firmware updates in that configuration. Firmware maintenance commonly requires hardware components, host services, or the node itself to be restarted. A conventional multi-node cluster can move workloads and maintain storage availability through other nodes while one node undergoes maintenance. A one-node cluster has no alternate node to preserve cluster services during that process.

“Software only” is broader and more accurate than “AOS only.” LCM can manage supported Nutanix software components according to the applicable compatibility and upgrade paths; support is not restricted exclusively to AOS. Inventory is also available as an LCM operation, but option B incorrectly implies that inventory is the only supported capability.

The platform restriction is therefore based on update type: software lifecycle operations are supported, while automated firmware updates are excluded because of the unavoidable service interruption and absence of node-level redundancy. Administrators must still confirm component interoperability and supported upgrade paths before initiating any update. Nutanix explicitly states that LCM is supported for software updates on single-node clusters but not for firmware updates. Reference: Prism 7.5 – Single-Node Cluster Requirements and Limitations . NHCF alignment: LCM capabilities, software maintenance, and cluster-specific limitations.

===============

The Nutanix Compatibility and Interoperability Matrix must be consulted before upgrading AOS or the ESXi hypervisor in a vSphere-based Nutanix cluster. The matrix identifies supported combinations of AOS releases, ESXi versions, Prism components, hardware platforms and related software. This prevents the administrator from introducing a hypervisor release that the installed AOS version does not support.

Upgrade planning must consider the current and target versions together. If the target AOS version requires a different supported hypervisor level, the administrator must follow the prescribed upgrade order. Nutanix Lifecycle Manager and one-click upgrade workflows perform compatibility checks, but the matrix remains the authoritative planning resource for confirming the intended version combination.

Nutanix Validated Designs provide architectural and deployment guidance rather than an exhaustive version-compatibility decision. Hardware replacement documentation governs component service procedures. Partner Software Validation may establish support for particular third-party products, but it does not replace Nutanix’s platform compatibility matrix for AOS and ESXi.

NHCF/NCA reference: Life Cycle Management—inventory, software updates, upgrade planning and compatibility validation; NCA Section 3, “Identify software maintenance tasks.” Official references: AOS 7.5—ESXi Host Upgrade , LCM—Recommended Upgrade Order .

===============

Balance-tcp provides active-active link utilization through Link Aggregation Control Protocol and is the strongest choice when the objective is to maximize aggregate VM traffic throughput across multiple physical NICs. The mode distributes traffic using flow information, allowing separate TCP flows—including flows originating from the same VM—to use different physical uplinks. This can increase host and VM bandwidth utilization beyond the capacity of a single uplink when sufficient parallel traffic flows exist.

Balance-tcp requires the corresponding physical-switch ports to be configured as a compatible LACP link aggregation group. The AHV bond and upstream switch configuration must agree; otherwise, connectivity or traffic-distribution failures can occur.

Active-Backup uses only one uplink for forwarding while the other remains available for failover, providing redundancy but not simultaneous bandwidth utilization. Balance-slb is also an active-active mode and does not require switch-side LACP, but its source-load-balancing behavior generally associates traffic sources with particular uplinks and cannot distribute an individual flow across links. “No Uplink Bond” supplies neither link aggregation nor bond-level redundancy.

NHCF/NCA reference: Networking—AHV virtual switches, uplink bonds and physical-network connectivity; NCA Section 2, “Identify virtual networking tasks.” Official references: Prism Central—Creating a Virtual Switch , AHV Networking Recommendations .

===============

A manual, immediate snapshot of an individual VM is created from the VM dashboard in Prism Element. The administrator opens the VM table, selects the target VM and invokes the Take Snapshot action. Prism then creates a point-in-time snapshot containing the VM configuration and the supported virtual-disk state.

This procedure is appropriate when the requirement concerns one VM and the snapshot must be taken immediately. Prism Central Data Protection is used for broader protection policies, recovery points, protection schedules and multi-cluster disaster-recovery operations. Those capabilities are valuable for recurring or policy-based protection but are not the direct manual workflow described in the question.

Connecting to a Controller VM is unnecessary and would bypass the supported administrative interface. The Prism Central Images service manages deployable disk images, ISO files and VM image resources; an image is not a point-in-time snapshot of a running VM.

For application-consistent protection, additional guest-side preparation such as Nutanix Guest Tools may be required. A standard manual snapshot, however, is initiated through the selected VM’s Prism Element actions.

NHCF/NCA reference: VM Management—VM dashboard, VM lifecycle tasks, snapshots and recovery points; NCA Section 2, “Describe VM tasks.” Official references: Prism 7.5—Creating a VM Snapshot Manually , Prism 7.5—Managing an AHV VM .

===============