The exhibit shows the NKP UI with the "Create Cluster" option grayed out in a new workspace, indicating that a prerequisite for cluster creation is missing. The NKPA course explains that to create a new Kubernetes cluster in a workspace, an Infrastructure Provider must be configured for that workspace. An Infrastructure Provider defines the underlying infrastructure (e.g., Nutanix AHV, AWS, vSphere) where the cluster will be provisioned, and without it, the Create Cluster option remains disabled in the UI.
The NKP Ultimate license supports creating clusters across various infrastructures, but the workspace must be associated with an Infrastructure Provider to enable cluster creation. The Nutanix Cloud Native (NCP-CN)
6.10 Study Guide states: "Before creating a cluster in a new workspace, ensure an Infrastructure Provider is configured for the workspace in the NKP UI; otherwise, the Create Cluster option will be grayed out." The engineer should navigate to the Infrastructure Providers section in the NKP UI (typically under the Global or Administration view), create a provider (e.g., for Nutanix AHV, AWS, or vSphere), and associate it with the workspace. Once this is done, the Create Cluster option will become available.
Incorrect Options:
* A. Create the cluster only using YAML and not the GUI: The issue is not with the GUI itself but with the missing Infrastructure Provider, which affects both GUI and CLI cluster creation. YAML alone does not resolve this.
* B. Attach existing clusters instead of creating a new cluster: Attaching existing clusters is an alternative but does not address the requirement to create a new cluster.
* D. Ensure NKP is upgraded to a minimum version of 2.12: The NKP Ultimate license implies a recent version, and the course does not indicate that version 2.12 is specifically required for this functionality. The issue is configuration-related, not version-related.
:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Cluster Creation Prerequisites.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on Workspace Configuration.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com

As per the NKPA 6.10 documentation under "Application Backup and Recovery with Velero," Velero is the out-of-the-box backup and restore solution integrated with NKP. To schedule application backups at a specific frequency (in this case, every six hours, equivalent to four times daily), the recommended approach is to use the Velero CLI to create a backup schedule.
The procedure involves:
* Using the Velero CLI to create a scheduled backup targeting the specific Kubernetes namespace (victory-finance) rather than the entire workspace.
* Specifying the frequency as --schedule="0 */6 * * *" (every six hours).
* Providing the cluster's kubeconfig for authentication.
Exact extract from the documentation:
"Velero's CLI can be used to create backup schedules for application-specific workloads. Use the namespace parameter to target the namespace where the applications are deployed, and set the cron-like schedule to the desired frequency." Reference:
Nutanix Kubernetes Platform Administration (NKPA) 6.10 - "Using Velero CLI to Create Backup Schedules" NCP-CN 6.10 Study Guide - "Application-Level Backup Best Practices"
=======

The NKPA course emphasizes that NKP's fleet management capabilities allow administrators to manage multiple Kubernetes clusters, including lightweight clusters on edge devices, by attaching them to an NKP workspace. With the NKP Ultimate license tier, the administrator has access to advanced fleet management features, including GitOps-based application deployment across attached clusters.
The most efficient way to lifecycle manage application deployments across the 30 edge devices is to create a new workspace and attach the 30 edge devices to this workspace using the Attach Cluster functionality (Option D). Once attached, NKP can use GitOps (via Flux) to push applications to all clusters in the workspace simultaneously, ensuring consistent deployment and lifecycle management. The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: "For managing edge devices with lightweight Kubernetes, attach the clusters to an NKP workspace using the Attach Cluster feature, enabling centralized application deployment and lifecycle management via GitOps." The administrator can use the kubeconfig files to attach each cluster via the NKP UI or CLI (e.g., nkp attach cluster).
Incorrect Options:
* A. Create a GitHub configuration for each device: This is manual and inefficient compared to NKP's centralized GitOps management.
* B. Create a script to automate deployment: Scripting is error-prone and lacks NKP's built-in fleet management capabilities.
* C. Delete lightweight Kubernetes and deploy new clusters: This is unnecessary, as NKP can manage existing clusters, including lightweight ones.
:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Fleet Management.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on Attaching Clusters.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com

As stated in the NKPA 6.10 documentation, when using external storage (such as AWS S3) with Loki for log storage, AWS credentials must be provided securely. This typically involves creating a Kubernetes Secret containing the static AWS credentials (access key ID and secret access key), which are referenced in the override ConfigMap to authenticate Loki's S3 storage backend.
Key reference from documentation:
"For Loki to store logs in an S3 bucket, AWS credentials must be created as a Kubernetes secret and referenced in the storage configuration." Reference:
Nutanix Kubernetes Platform Administration (NKPA) 6.10 - "Loki External Storage Configuration" NCP-CN 6.10 Study Guide - "Using External Storage Backends with Logging"

The output indicates that an AppDeployment resource named grafana-logging was created in the kommander- default-workspace namespace, which corresponds to an NKP workspace. The NKPA course explains that NKP Platform Applications, such as Grafana Logging, are deployed using the nkp create appdeployment command. This command creates an AppDeployment resource that deploys the specified application (e.g., Grafana Logging) across all clusters in a workspace.
The command in Option A, nkp create appdeployment grafana-logging --app grafana-logging-6.57.4 -- workspace default-workspace, matches the output:
* grafana-logging is the name of the AppDeployment.
* --app grafana-logging-6.57.4 specifies the application and version.
* --workspace default-workspace targets the workspace, which corresponds to the namespace kommander-default-workspace in the output (the kommander- prefix is a standard NKP namespace convention).
The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: "To deploy a platform application like Grafana Logging, use nkp create appdeployment <app-name> --app <app-id>-<version> --workspace
<workspace-name>, which creates an AppDeployment resource in the workspace namespace." This command aligns with the output provided.
Incorrect Options:
* B. export WORKSPACE_NAMESPACE and nkp create package-bundle: There is no nkp create package-bundle command in NKP for deploying applications. The correct command is nkp create appdeployment.
* C. kubectl get appdeployment: This retrieves the status of an AppDeployment, not creates it. The output indicates creation, not retrieval.
* D. kubectl get helmreleases: This retrieves HelmRelease resources, not AppDeployments, and does not create the Grafana Logging deployment.
:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Platform Application Deployment.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on Day 2 Operations.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com