The NKPA course explains that by default, NKP creates new AWS infrastructure (VPC, subnets, ELBs) when deploying a cluster on AWS. However, NKP supports deploying clusters on existing AWS infrastructure by providing custom configurations. The recommended method using the NKP CLI is to create an overrides file specifying the pre-existing VPC, subnets, and ELB, and then pass this file to the nkp create cluster aws command using the --overrides parameter.
The overrides file (e.g., aws-infra-overrides.yaml) contains details like vpcID, subnetIDs, and loadBalancerIDs, which NKP uses to deploy the cluster on the specified infrastructure instead of creating new resources. For example:
yaml
CollapseWrap
Copy
aws:
vpcID: vpc-12345678
subnetIDs:
- subnet-12345678
- subnet-87654321
loadBalancerIDs:
- elb-12345678
The engineer then runs: nkp create cluster aws --overrides aws-infra-overrides.yaml.
The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: "To deploy an NKP cluster on existing AWS infrastructure, create an overrides file with the pre-existing VPC, subnets, and ELB details, and use the -- overrides parameter with the nkp create cluster aws command to apply the custom configuration." This method ensures the AWS team's requirement is met while leveraging NKP's CLI for deployment.
Incorrect Options:
* A. nkp adopt infrastructure aws: There is no nkp adopt infrastructure command in NKP for this purpose.
* C. Use the NKP UI: While the UI allows specifying infrastructure details, the question focuses on the CLI-based deployment, and the UI method is less relevant here.
* D. Include parameters directly in nkp create cluster aws: The nkp create cluster aws command does not support direct parameters for VPC, subnets, and ELB; it requires an overrides file.
:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on AWS Cluster Deployment.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on Building NKP Clusters.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com

The Nutanix Kubernetes Platform (NKP) uses workspaces to provide isolated environments for different teams or projects, allowing each team to manage its own clusters, applications, and resources independently.
According to the NKPA course, creating a new workspace is a key Day 2 operation to support multi-tenancy and isolated development environments, such as those required for the microservices in this scenario.
The course specifies that to create a new workspace, users must navigate to the workspace selection dropdown list in the top menu bar of the NKP user interface (UI) and select Create Workspace. This action opens a form where administrators can define the workspace name, description, and associated resources (e.
g., clusters, users, and policies). The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: "To create a new workspace in NKP, go to the workspace selection dropdown in the UI and select 'Create Workspace' to configure an isolated environment for a team or project." This process ensures that each microservice team has its own isolated environment for development and testing, with access restricted to their specific workspace.
Incorrect Options:
* A. From the Cluster selection, select Add Cluster: Adding a cluster creates a new Kubernetes cluster within an existing workspace, not a new workspace. The NKPA course distinguishes between cluster and workspace creation.
* C. From the workspace selection dropdown list in the top menu bar, select Add Workspace: The NKPA course and UI use "Create Workspace" as the standard terminology, not "Add Workspace."
* D. From the Administration selection dropdown list in Infrastructure Providers, select Add Infrastructure Provider: This option is for configuring infrastructure providers (e.g., AWS, vSphere) for NKP, not for creating workspaces.
:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Workspace Management.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on Day 2 Operations.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com

The kube-prometheus-stack is a key component of NKP's monitoring stack, providing tools for metrics collection, visualization, and alerting. The NKPA course explains that Alertmanager, a component of the kube-prometheus-stack, is responsible for handling alerts generated from Prometheus metrics. It aggregates, deduplicates, and routes notifications to the appropriate channels (e.g., email, Slack, PagerDuty), ensuring that the Platform Engineer stays informed of critical events and anomalies in the NKP cluster, such as node failures, resource exhaustion, or application errors.
The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: "Alertmanager in the kube-prometheus-stack processes alerts from Prometheus, enabling administrators to stay informed of cluster events through configured notification channels." By configuring Alertmanager with appropriate routing rules and receivers, the engineer can receive real-time notifications about cluster events, driving proactive management and productivity.
Incorrect Options:
* A. prometheus-operator: The operator manages Prometheus and related resources but does not directly handle event notifications.
* B. service monitors: Service monitors define how Prometheus scrapes metrics, not how events are communicated.
* D. node-exporter: Node-exporter collects node-level metrics, not event notifications.
:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Monitoring and Alerting.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on Day 2 Operations.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com Prometheus Documentation: https://prometheus.io/docs/alerting/alertmanager

Comprehensive and Detailed Explanation:
The correct procedure for deleting an NKP cluster involves using the nkp delete cluster command with the appropriate cluster name and namespace. This ensures that not only the Kubernetes resources but also the corresponding NKP resources (e.g., nodepools, Kommander integration) are deleted cleanly and consistently.
Simply deleting the VMs does not clean up the associated NKP management objects. This approach is detailed in the NKP documentation for cluster lifecycle management, emphasizing the need to use the provided CLI commands for full removal.
References: NCP-CN-6.10 Course Material - Cluster Deletion Commands

The NKPA course covers user authentication for NKP clusters as part of Day 2 operations, emphasizing integration with external identity providers (IdPs) to manage user access securely. NKP uses Dex, an OpenID Connect (OIDC) identity provider, to facilitate authentication by acting as a connector between the Kubernetes cluster and external IdPs, such as LDAP, SAML, or OAuth-based systems.
The course explains that to set up user authentication, a Platform Engineer must configure a Dex connector to the user base's identity provider. Dex integrates with the Kubernetes API server to enable OIDC-based authentication, allowing users to log in using their IdP credentials. The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: "NKP supports user authentication through Dex, which provides OIDC integration with external identity providers, enabling single sign-on (SSO) for cluster access." The process involves deploying Dex as a platform application, configuring the IdP connector (e.g., specifying client IDs, secrets, and endpoints), and updating the Kubernetes API server to use OIDC authentication.
Incorrect Options:
* A. Enable Gatekeeper and create a connector to the user base's identity provider: Gatekeeper is a Kubernetes policy engine used for enforcing admission control policies, not for authentication. The NKPA course does not associate Gatekeeper with user authentication.
* B. Disable native NKP authentication, enable Traefik, and create a connector to the user base's identity provider: Traefik is an ingress controller for managing external traffic, not authentication.
Disabling native authentication is unnecessary, as NKP supports OIDC alongside native methods. The NKPA course does not mention Traefik in the context of authentication.
* C. Create a MetalLB connector to the user base's identity provider: MetalLB is a load balancer for bare-metal Kubernetes clusters, not an authentication component. This option is irrelevant, as per the NKPA course.
:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on User Authentication and Authorization.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on NKP Day 2 Operations.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com Dex Documentation: https://dexidp.io