NCP-CN Exam Dumps : Nutanix Certified Professional - Cloud Native (NCP-CN-6.10)

Comprehensive and Detailed Explanation:

The NKP Pro licensing tier includes Fleet Management, which enables centralized lifecycle management of multiple Kubernetes clusters. This feature is critical for managing larger environments, providing visibility and control over fleet-wide configurations and updates. Other features, like AI OPS and advanced observability, are typically associated with higher tiers (e.g., Ultimate).

The NKPA course details that backup and restore functionality in NKP is provided through integration with Velero, which supports backing up persistent volumes, cluster resources, and application data to S3-compatible storage. This functionality is considered an advanced feature and is included in higher-tier NKP licenses: NKP Ultimate and NKP Pro.

NKP Ultimate: This top-tier license includes all NKP features, such as air-gapped deployments, fleet management, and backup/restore capabilities. It is designed for enterprise-grade environments requiring comprehensive disaster recovery.

NKP Pro: This mid-tier license also includes backup and restore functionality, catering to organizations needing robust data protection but not necessarily all the features of the Ultimate tier (e.g., air-gapped support).

The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “Backup and restore functionality, powered by Velero, is available in NKP Pro and NKP Ultimate license tiers, enabling protection of persistent volumes and cluster resources.” These licenses provide the necessary tools and support for configuring Velero with S3-compatible storage, scheduling backups, and performing restores in production environments.

Incorrect Options:

A. NKP Starter: The Starter tier is entry-level and does not include advanced features like backup and restore. It focuses on basic cluster management.

B. NKP Essential: This tier, if it exists in NKP’s licensing model, would be a lower tier and unlikely to include backup/restore functionality, as it is not mentioned in the NKPA course.

According to the NKPA 6.10 documentation, licensing in an NKP cluster is constrained by the total number of vCPUs assigned to all nodes (workers and control planes). In this scenario, the cluster has a maximum of 150 vCPUs available.

The existing output shows 10 worker nodes, each with 8 vCPUs (10×8=80 vCPUs) and 3 control plane nodes, each with 4 vCPUs (3×4=12 vCPUs).

Current vCPU usage: 80 + 12 = 92 vCPUs.

Remaining vCPUs: 150 - 92 = 58 vCPUs.

Option A:

Adding 6 control plane nodes (6×4=24 vCPUs).

This would increase control planes to 9 total (3 existing + 6 new). Control plane nodes would consume 9×4=36 vCPUs.

Worker nodes remain at 80 vCPUs.

Total vCPU usage: 36 + 80 = 116 vCPUs (still under 150 vCPUs).

However, it’s unusual and unnecessary to have 9 control planes in a typical NKP setup. NKPA and NCP-CN best practices indicate typically no more than 3 or 5 control planes for HA. Therefore, this is technically possible but not recommended or standard practice. So not selected.

Option B:

Expanding the existing worker nodepool by 8 nodes (8×8=64 vCPUs).

This would add 64 vCPUs to the current 92 vCPUs:

92 + 64 = 156 vCPUs → exceeds licensing limit.

Correction: The question specifies “expand up to 8 nodes,” so it’s possible to expand by only 7 nodes (7×8=56 vCPUs).

92 + 56 = 148 vCPUs → within licensing limits.

Thus, expanding by up to 7 nodes is valid.

Option C:

Creating a new worker nodepool with 10 nodes (10×8=80 vCPUs).

This would add 80 vCPUs to the existing 92 vCPUs:

92 + 80 = 172 vCPUs → exceeds 150 vCPU licensing limit.

Not valid.

Option D:

Expanding the original worker nodepool by up to 4 nodes (4×8=32 vCPUs) = +32 vCPUs.

Adding a new nodepool of 6 nodes with 4 vCPUs/node (6×4=24 vCPUs) = +24 vCPUs.

Total increase: 32 + 24 = 56 vCPUs.

Total vCPU usage: 92 + 56 = 148 vCPUs → within the 150 vCPU limit.

Thus, valid.

Extract Reference:

NKPA 6.10 – “Cluster Sizing and Licensing”

Nutanix Kubernetes Platform Administration (NKPA) – Licensing Considerations

"The total number of vCPUs for all nodes (control planes and workers) must not exceed the licensed vCPU capacity of the NKP deployment."

This confirms that Options B and D are the two valid approaches to expand the cluster while remaining compliant with licensing constraints.