Nutanix NCP-CN Practice Test Questions Answers

The NKPA course specifies that the Nutanix Image Builder (NIB), used for creating custom machine images for NKP cluster nodes, supports specific Linux distributions that are compatible with Nutanix infrastructure and Kubernetes requirements. For NKP v2.12.x, the supported distributions for NIB are Ubuntu and Rocky Linux, as these are tested and optimized for NKP deployments, ensuring stability and compatibility with Cluster API (CAPI) and Nutanix AHV.

The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “NKP Image Builder (NIB) supports Ubuntu and Rocky Linux as base distributions for creating custom images for NKP cluster nodes, ensuring compatibility with Kubernetes and Nutanix infrastructure.” Ubuntu provides a widely-used, well-supported base with long-term support (LTS) versions, while Rocky Linux is a CentOS replacement that Nutanix has adopted for its reliability and enterprise focus, especially after CentOS 8’s end-of-life in 2021.

Incorrect Options:

B. Fedora: Fedora is not a supported distribution for NIB in NKP, as it is more suited for bleeding-edge development rather than production Kubernetes environments.

D. CentOS: CentOS 8 reached end-of-life in December 2021, and Nutanix has shifted to Rocky Linux as its replacement for NKP image building. The course does not list CentOS as a supported option for NIB in NKP v2.12.x.

The NKP documentation recommends using a combination of RBAC assignments and exported manifests to manage access across multiple clusters. By exporting the role assignments to YAML, the engineer can consistently apply these settings across the different environments, ensuring the new team has the necessary resources and limits. This approach is especially useful for environments with multiple clusters and standardized configurations.

The NKPA course explains that NKP’s fleet management capabilities allow centralized policy federation and management of multiple Kubernetes clusters from a single pane of glass, while workspaces provide isolation for different teams or groups. To meet the requirement of federating policy while separating clusters by group, the IT team needs the NKP Ultimate license, which includes advanced fleet management features.

With NKP Ultimate, the IT team can:

Create three workspaces (one for each group: Fin VD, Fin Insurance, Fin Travel).

Assign the corresponding Kubernetes clusters to each workspace, ensuring isolation between groups.

Use NKP’s fleet management to apply policies (e.g., RBAC, monitoring, logging) across all clusters from a single pane of glass, such as the NKP UI or CLI.

The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “NKP Ultimate provides fleet management for centralized policy federation across multiple clusters, using workspaces to isolate clusters for different teams or groups.” This setup ensures that each group’s clusters are separated while maintaining centralized policy management, aligning with the IT team’s requirements.

Incorrect Options:

B. NKP Starter: The Starter license lacks fleet management and workspace isolation features, making it unsuitable for this scenario.

C. NKP Pro with projects: Projects are sub-divisions within workspaces for resource allocation, not for cluster isolation or fleet management. NKP Pro may not include full fleet management capabilities.

D. NKP Pro with workspaces: While NKP Pro supports workspaces, it may not provide the full fleet management needed for centralized policy federation across all clusters. NKP Ultimate is the better fit.

NKPA 6.10 recommends leveraging workspaces to isolate different tenants (clients) in a multi-tenant environment. LDAP connectors can be scoped to individual workspaces, allowing separate authentication and RBAC configurations per client.

Key reference from documentation:

“In multi-tenant scenarios, create a dedicated workspace for each tenant and configure a unique LDAP connector within that workspace to integrate their identity source.”

The NKPA course details that NKP Platform Applications, such as Grafana Logging, Grafana Loki, and Project Logging, are deployed to Kubernetes clusters to provide monitoring and logging capabilities. To ensure these components are automatically deployed to new workload clusters in a workspace, the administrator must enable them in the Application section under the workspace configuration in the NKP UI.

The course explains that the Application section allows administrators to select and configure platform applications that should be applied to all clusters within a workspace. By enabling Grafana Logging, Grafana Loki (for log aggregation), and Project Logging (for project-specific log management), these components are automatically deployed as part of the cluster provisioning process. The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “To deploy platform applications like Grafana Loki and logging components to new clusters, configure them in the Application section of the workspace settings in the NKP UI.”

Incorrect Options:

A. Enable them in the Insights section under workspace: The Insights section is for analytics and monitoring dashboards, not for deploying logging components.

B. Enable them in the Projects section under workspace: Projects are sub-divisions within workspaces for resource allocation, not for configuring platform applications.

C. Enable them in the Clusters section under workspace: The Clusters section is for managing cluster settings, not for enabling platform applications.