Study guide

10.3 X-Ray, Collector, and the Objective 1.3 Tool Inventory

Nutanix Certified Associate NCA

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Nutanix Cloud Platform & HCI Foundations

1.1 Nutanix NCA Exam Overview, Format, and Objectives 1.2 Hyperconverged Infrastructure (HCI) vs. Traditional 3-Tier Architecture 1.3 The Nutanix Enterprise Cloud Portfolio (NCI, NUS, NCM, EUC, NC2)

2 Chapter 2: Platform Architecture & Distributed Core Services

2.1 Hardware Building Blocks: Nodes, Blocks, Clusters, and Quorum 2.2 Controller VM (CVM) Architecture, Datapath, and Autopathing 2.3 Core Distributed Services: Cassandra, Stargate, Curator, Zookeeper, and Genesis

3 Chapter 3: Prism Administration & Cluster Operations

3.1 Prism Element vs. Prism Central Architecture and Interface Navigation 3.2 Entity Management, Categories, and Role-Based Access Control 3.3 Nutanix Licensing Tiers, Add-ons, and Pulse Telemetry

4 Chapter 4: AOS Distributed Storage Fabric & Data Placement

4.1 Storage Pools, Storage Containers, and vDisk Virtual Architecture 4.2 Redundancy Factor (RF2 vs. RF3), Failure Domains, and Fault Tolerance 4.3 Data Locality Mechanics and Intelligent Lifecycle Management (ILM)

5 Chapter 5: Storage Optimization & Business Continuity

5.1 Storage Efficiency: Compression, Deduplication, and Erasure Coding (EC-X) 5.2 Space-Efficient Redirect-on-Write (ROW) Snapshots and Zero-Byte Clones 5.3 Protection Domains, Consistency Groups, and Disaster Recovery Replication

6 Chapter 6: AHV Virtual Machine Lifecycle Management

6.1 AHV VM Provisioning, Resource Allocation (vCPU, vRAM, Disks), and Boot Types 6.2 Nutanix Image Service and Virtual Machine Templates 6.3 Nutanix Guest Tools (NGT) Architecture, Features, and Deployment 6.4 AHV High Availability (HA), Acropolis Dynamic Scheduling (ADS), and Affinity Rules

7 Chapter 7: AHV Networking & Flow Security Fundamentals

7.1 AHV Virtual Networking Architecture, Open vSwitch (OVS), and Bridges 7.2 Host Network Uplinks, Virtual Switch Configuration, and NIC Bonding Modes 7.3 Virtual Networks: Managed vs. Unmanaged Networks and IPAM 7.4 Nutanix Flow Network Security & Microsegmentation Fundamentals

8 Chapter 8: Cluster Maintenance, Health Monitoring & Support

8.1 Nutanix Cluster Health Monitoring, Alerts, and Events Engine 8.2 Nutanix Cluster Check (NCC) Architecture and Execution 8.3 Life Cycle Manager (LCM) and Rolling Non-Disruptive Upgrades 8.4 Nutanix Support Ecosystem: Diagnostics, Log Gathering, and Support Bundles

9 Chapter 9: Recognizing Nutanix Solutions, Hypervisors & the Product Portfolio

9.1 Supported Hypervisors for NCI and Feature Supportability 9.2 NCI Core Components, Configurations, and Common Deployment Scenarios 9.3 Nutanix Unified Storage: Files, Objects, and Volumes Use Cases 9.4 Nutanix Database Service (NDB) and Database Automation 9.5 Nutanix Kubernetes Platform, Enterprise AI, and End-User Computing

10 Chapter 10: Nutanix Tools — Migration, Deployment, and Validation

10.1 Nutanix Move: Cross-Hypervisor and Cloud Migration 10.2 Foundation and Foundation Central: Imaging and Cluster Deployment 10.3 X-Ray, Collector, and the Objective 1.3 Tool Inventory

11 Chapter 11: Cluster Configuration, Security & Hardware Maintenance

11.1 Cluster Services Configuration: DNS, NTP, SMTP, and SNMP 11.2 Cluster Security Options: Lockdown, Encryption, and the Recycle Bin 11.3 Node Maintenance Mode, Host Shutdown, and Cluster Shutdown 11.4 Cluster Expansion: Node Types and In-Node Expansion Capabilities 11.5 Out-of-Band Management and Remote Console Access

12 Chapter 12: Storage, Network, and Software Administration Tasks

12.1 Volume Groups, vDisk Placement, and Live vDisk Migration 12.2 Network Visualizer, Physical Switch Monitoring, and Network Segmentation 12.3 The Software Compatibility Matrix and Upgrade Path Planning 12.4 Taking and Managing VM Snapshots in Prism 12.5 License Operations: State, Assignment, Reclamation, and Expiry

13 Chapter 13: Performance Analysis, Reporting & Support Operations

13.1 Prism Analysis: Metric Charts, Entity Charts, and Custom Reports 13.2 Custom Alert Policies and Behavioural Anomaly Detection 13.3 Interpreting Workload Performance: CPU Contention, CPU Ready, Memory, and I/O Latency 13.4 Creating Support Cases, Required Documentation, and Insights

10.3 X-Ray, Collector, and the Objective 1.3 Tool Inventory

Key Takeaways Explain This Topic AI

X-Ray is an automated testing framework that benchmarks HCI performance and resilience, running scenarios such as node failure during load rather than raw synthetic I/O alone.

Collector gathers inventory and utilization data from an existing VMware environment to support Nutanix sizing before any migration begins.

Collector runs pre-sales and pre-migration; Move runs the migration itself, so the two are sequential rather than alternatives.

Objective 1.3 names exactly seven tools: Move, NGT, Foundation and Foundation Central, the Witness Service/VM, Self-Service Restore, X-Ray, and Collector.

Each of the seven maps to one distinct phase: sizing, deployment, migration, guest integration, arbitration, self-service recovery, and validation.

Last updated: September 2026

10.3 X-Ray, Collector, and the Objective 1.3 Tool Inventory

Objective 1.3 names seven tools. Five of them appear elsewhere in this guide where their function naturally belongs. This section teaches the remaining two — X-Ray and Collector — and then assembles all seven into one recognition table, because the most common way this objective is tested is a straight "which tool would you use" scenario.

X-Ray: Benchmarking Performance and Resilience

X-Ray is an automated testing framework for hyperconverged infrastructure. It is free, deploys as a virtual appliance, and runs test scenarios against a target cluster.

What makes X-Ray distinctive is the second half of its remit. Conventional storage benchmarking tools measure throughput and latency under a synthetic load and report a number. X-Ray does that, but it also tests resilience — how the platform behaves when something breaks while the load is running .

Representative scenarios:

Performance under a defined workload profile , such as an OLTP-like or VDI-like mix, reported as throughput and latency over time.

Node failure during load. X-Ray fails a node mid-test and charts what happens to application performance while the cluster rebuilds. A platform that posts an excellent peak number but collapses during a rebuild looks very different under this test.

Rolling upgrade during load , showing the performance impact of a non-disruptive upgrade on running workloads.

Noisy neighbour , showing whether one aggressive VM degrades others.

The results are charted over the test duration rather than reduced to a single figure, which is the point: the shape of the curve during a failure is the information a synthetic benchmark hides.

Tip

Use-case sentence to remember: X-Ray is how you compare HCI platforms — or validate your own cluster — on both performance and behaviour during failure. If a scenario mentions evaluating vendors, proving resilience claims, or measuring the impact of a node failure on running applications, the answer is X-Ray.

Collector: Sizing From the Existing Estate

Collector answers the question that comes before any Nutanix purchase: what do we actually have today, and how big does the Nutanix cluster need to be?

Collector connects to an existing VMware environment — typically vCenter — and gathers inventory and utilization data : how many VMs there are, their configured CPU, memory, and disk, and crucially their actual consumption over a collection period.

That distinction between configured and consumed is the whole value. Estates are routinely over-provisioned, and sizing a new platform from configured values produces a cluster far larger and more expensive than necessary. Collector supplies measured data so sizing reflects real demand.

Characteristics to recognize:

It is a free, read-only data-gathering tool. It changes nothing in the source environment.

It runs before any migration — during evaluation and design.

Its output feeds Nutanix sizing for the proposed cluster.

Collector and Move Are Sequential, Not Alternatives

A frequent point of confusion, and a good distractor:

Phase Tool Question it answers

Evaluate and size Collector What do we have, and how much Nutanix do we need?

Deploy Foundation How do these nodes become a cluster?

Validate X-Ray Does it perform and survive failure as claimed?

Migrate Move How do the workloads get onto AHV?

Collector never moves a VM. Move never sizes a cluster.

The Complete Objective 1.3 Tool Inventory

All seven tools, each mapped to the phase it serves and to where this guide teaches it:

Tool Purpose Phase Covered in

Collector Gathers inventory and real utilization from an existing VMware estate to size Nutanix Pre-sales / design This section

Foundation / Foundation Central Images bare-metal nodes and creates clusters; Foundation Central does it remotely at scale Deployment Section 10.2

  • X-Ray Automated performance and resilience testing of HCI Validation This section
  • Move Migrates VMs onto AHV from ESXi, Hyper-V, AWS, and Azure Migration Section 10.1

NGT (Nutanix Guest Tools) In-guest agent enabling application-consistent snapshots, VM mobility, and self-service restore Guest integration Section 6.3

Self-Service Restore (SSR) Lets a VM owner recover their own files from a snapshot without an administrator Day-2 recovery Section 6.3

Witness Service / VM Arbitrates leadership for two-node clusters and Metro deployments to prevent split brain Availability Sections 2.1 and 9.2

Important

Two of these depend on each other and are frequently paired in questions. Self-Service Restore requires NGT to be installed and enabled in the guest, because SSR works through the in-guest agent. A question that describes a user unable to restore their own files from a snapshot is very often an NGT question in disguise.

Quick Discrimination Drill

Work through these until the mapping is automatic:

  • Prove that application latency stays acceptable when a node fails mid-workload. → X-Ray
  • Determine how much CPU and memory the existing 900 VMs actually consume. → Collector
  • Turn 12 new bare-metal nodes into a cluster. → Foundation
  • Do the same at 40 stores without travelling. → Foundation Central
  • Move those 900 VMs from vSphere onto AHV. → Move
  • Take an application-consistent snapshot of a SQL Server VM. → NGT
  • Let a user recover a file they deleted this morning, themselves. → SSR , which requires NGT
  • Stop a two-node branch cluster from splitting brain. → Witness VM

Loading diagram... The Seven Objective 1.3 Tools by Platform Lifecycle Phase