When deploying NKP to AWS, the bootstrap process requires AWS credentials to interact with AWS APIs for provisioning resources like EC2 instances. The NKPA course specifies that the nkp CLI supports the -- aws-profile flag to specify a custom AWS profile for authentication. This profile, defined in the AWS credentials file (~/.aws/credentials), contains the access key and secret key for the desired AWS account.
The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: "To deploy NKP on AWS with custom credentials, use the --aws-profile=<profile-name> flag during the nkp create bootstrap command to reference a specific AWS profile." This approach leverages the AWS CLI's profile management, ensuring secure and flexible credential handling. For example, the command would be nkp create bootstrap --aws-profile=my- profile --kubeconfig bootstrap-cluster.conf.
Incorrect Options:
* B. --cloud-credentials=<my-profile></my-profile>: This flag is not used by the nkp CLI. The NKPA course specifies --aws-profile for AWS.
* C. --with-aws-bootstrap-credentials=true: This flag does not exist in the NKPA documentation for NKP bootstrap.
* D. --aws-access-key=<aws access="" key=""> --aws-secret-key=<aws secret="" key=""></aws><
/aws>: While these flags may be used in some tools, the NKPA course recommends using --aws-profile to avoid hardcoding sensitive credentials.
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on AWS Deployment.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on Bootstrap Configuration.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com AWS CLI Documentation: https://docs.aws.amazon.com/cli

As outlined in the NKPA 6.10 documentation under "Customizing Resource Requests and Limits for Logging," to override the default resource values for the logging operator, a ConfigMap named logging- operator-logging-overrides in the kommander namespace is used. The values.yaml in the ConfigMap should precisely define fluentd resource limits and requests in a valid YAML format.
The correct YAML format is:
yaml
Copy
apiVersion: v1
kind: ConfigMap
metadata:
name: logging-operator-logging-overrides
namespace: kommander
data:
values.yaml: |
fluentd:
resources:
limits:
cpu: 4
memory: 4Gi
requests:
cpu: 4
memory: 4Gi
This ensures that the desired CPU and memory resources are correctly applied for the fluentd daemon, avoiding parsing errors and meeting the high-demand logging needs.
Reference:
Nutanix Kubernetes Platform Administration (NKPA) 6.10 - "Configuring Logging Resources" NCP-CN 6.10 Study Guide - "Overriding Fluentd Resources Using ConfigMap"
=======

The NKPA course details the deployment of an NKP Management cluster on AWS using the nkp install kommander command, which installs the Kommander component responsible for fleet management. For a testing environment with minimal resource usage, the engineer can optimize the installation process by adjusting parameters that control timeouts and initialization settings, reducing overhead and ensuring the deployment completes efficiently on smaller infrastructure.
The two relevant parameters are:
* --wait-timeout (Option B): This parameter sets the maximum time the nkp install kommander command waits for the Kommander components to become ready. In a testing environment with minimal resources, components may take longer to start due to limited CPU and memory. Reducing the wait timeout (e.g., --wait-timeout=10m) ensures the command does not hang indefinitely, allowing the engineer to troubleshoot if needed. The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: "Use
--wait-timeout with nkp install kommander to adjust the waiting period for component readiness, useful in low-resource environments."
* --init (Option D): This parameter initializes the Kommander installation with default settings optimized for minimal resource usage, suitable for a testing environment. It ensures that Kommander deploys with a lightweight configuration, reducing the resource footprint (e.g., fewer replicas, lower resource requests). The NKPA course notes: "The --init flag with nkp install kommander sets up a minimal configuration for testing purposes, minimizing resource usage on AWS." Incorrect Options:
* A. --request-timeout: This parameter is not relevant to nkp install kommander. It is typically used for API request timeouts, not installation optimization.
* C. --yaml: This parameter would specify a custom YAML configuration file, but the question asks for minimal resource usage, which is better achieved with --init for default lightweight settings.
:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Deploying Kommander on AWS.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on Building NKP Clusters.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com

For deployments in air-gapped environments where there is no external Internet connectivity, the --airgapped parameter is required. This instructs the NKP deployment to rely solely on internal resources, using pre- staged images and local container registries, ensuring that no external network dependencies cause deployment failures.
References: Nutanix Kubernetes Platform Administration Guide - Air-gapped Cluster Deployment Requirements

The NKPA course outlines the default behaviors of NKP when deploying workload clusters within a workspace, regardless of the provisioning environment (e.g., AWS, Nutanix, Azure). When a workload cluster is deployed in AWS, NKP ensures consistency across the workspace by applying the following default behaviors:
* The NKP workload cluster will receive all of the GitOps sources that have been assigned to the NKP workspace (Option A): NKP uses GitOps with Flux to manage cluster configurations and applications. The course explains that GitOps sources (e.g., Git repositories) assigned to a workspace are automatically applied to all clusters in that workspace, ensuring consistent configuration and application deployment. The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: "New workload clusters inherit all GitOps sources configured for the workspace, enabling Flux to synchronize configurations from the specified repositories."
* The NKP workload cluster will be deployed all of the applications that have been enabled on this NKP workspace (Option D): NKP Platform Applications (e.g., Prometheus, Rook Ceph) enabled in the workspace are automatically deployed to new workload clusters. The NKPA course notes: "When a workload cluster is created, NKP deploys all platform applications enabled in the workspace to ensure consistent functionality across clusters." Incorrect Options:
* B. The NKP workload cluster will receive all of the NKP RBAC policy: RBAC policies are defined at the workspace or project level and applied to users or groups, not automatically to clusters. Clusters inherit RBAC through user access, not as a default deployment behavior.
* C. The NKP workload cluster will also be assigned to all of the NKP projects: Clusters are assigned to specific projects manually, not automatically to all projects in a workspace.
:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Workload Cluster Deployment.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on Workspace Management.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com