A development team decided to employ an efficient monitoring system with Grafana-logging, which was successfully...

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 - --workspace , 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.