NCP-CN Exam Dumps and Practice Questions

The development team should configure Namespace-level RBAC (Role-Based Access Control) in the NKP GUI.

Why this is correct:

• Limited Permissions: RBAC allows precise control over what actions team members can perform at the namespace level
• Task Alignment: The specific permissions needed are:
  • Deploy/update applications → requires Deployment creation and update permissions
  • Scale deployments → requires Deployment scale permissions
  • View logs and metrics → requires read permissions for logs and metrics
• Namespace Isolation: Namespace-level RBAC restricts access to their specific namespace only, preventing unauthorized changes in other environments
• Fine-Grained Control: Roles can be crafted to grant only the necessary permissions (e.g., developer role) without cluster-admin privileges
• NKP GUI Integration: The NKP GUI provides a user-friendly way to create and manage namespace-level RBAC policies

Namespace-level RBAC is the appropriate access control mechanism for limiting developer permissions to their specific namespace and preventing unauthorized actions in other environments.

To upgrade an AWS Kubernetes cluster from version 1.28.1 to 1.29.9, the engineer should take two actions: (1) Upgrade the management cluster control plane (master components) to a compatible version that supports the target worker version, ensuring the version skew is within acceptable limits (typically control plane can be one minor version ahead of workers), and (2) Upgrade the workload cluster using NKP's upgrade mechanisms, which may involve using the Cluster API or updating the cluster resource definition, and then systematically upgrading worker nodes either through rolling updates or cluster recreation. Both the control plane and worker nodes must be upgraded, and the upgrade path should be verified to be supported (not all versions support direct jumps - intermediate versions may be required).

When attaching existing EKS clusters to NKP, persistent volume errors typically occur because the cluster lacks the necessary storage provisioning mechanism. EKS clusters need the EBS CSI (Container Storage Interface) driver addon installed to dynamically provision EBS-backed persistent volumes. Without it, PersistentVolumeClaim requests will fail. The Platform Engineer should install the EBS CSI driver addon on the EKS cluster and ensure appropriate storage classes are created to enable persistent volume functionality.

To create an NKP cluster on vSphere with multiple worker node pools with different node specifications, the proper approach is to use NKP CLI with node pool configurations that specify the vCPU, node count, and pool name for each pool.

Why this is correct:

• Node Pool Configuration: NKP CLI supports creating multiple node pools in a single cluster definition, each with distinct specifications
• Individual Pool Settings: Each node pool can be configured with:
  • Pool name (e.g., worker-pool-1, worker-pool-2, worker-pool-3)
  • Node count (6, 3, and 3 respectively)
  • vCPU specification (10, 8, and 6 respectively)
• vSphere Provisioning: When using vSphere provisioning, the NKP CLI translates these specifications into vSphere VM templates with the appropriate resource allocations
• Proper Workflow: The konvoy create cluster command accepts a cluster configuration file that defines all three node pools with their distinct specifications
• Single Cluster Creation: All pools are created as part of a single cluster deployment, not through separate cluster commands

The NKP CLI with proper node pool configuration in the cluster definition file is the correct method for creating heterogeneous node pools on vSphere.