Exam Bundle

The application's Pod appears under the expected namespace while the original default-namespace query remains empty. That observed result would support another specific correction: Specify the correct namespace or inspect all permitted namespaces when looking for a resource. The other scenario concerns: A user lists Pods without a namespace and concludes an application is missing although it runs in another namespace. The current Brookside Manufacturing problem is: An operator runs a potentially destructive manifest update without seeing which objects will change. The evidence required here is: The planned resource delta is visible without mutating cluster state, and the approved apply matches it.

The intended resource creates cleanly in the target cluster without conflicting immutable server-generated metadata. That observed result would support another specific correction: Remove server-managed identity and concurrency fields from portable declarative manifests before applying to another cluster. The other scenario concerns: A user copies a resource manifest between clusters while retaining server-generated uid and resourceVersion metadata. The current Brookside Manufacturing problem is: An operator runs a potentially destructive manifest update without seeing which objects will change. The evidence required here is: The planned resource delta is visible without mutating cluster state, and the approved apply matches it.

The diagnostic record includes the object's properties and related events instead of only its name and status summary. That observed result would support another specific correction: Use get for inventory and describe for resource details, events, and selected conditions when inspecting a resource. The other scenario concerns: An engineer cannot distinguish kubectl get from kubectl describe and reads only a short status column during a fault. The current Brookside Manufacturing problem is: An operator runs a potentially destructive manifest update without seeing which objects will change. The evidence required here is: The planned resource delta is visible without mutating cluster state, and the approved apply matches it.

Differentiate deleting an individual object from deleting its parent namespace, and inspect namespace contents before cleanup. That choice addresses a different foundational issue: A namespace cleanup removes one configuration object but leaves the namespace and its workload resources intact unexpectedly. The issue at Juniper Media is instead: An operator runs a potentially destructive manifest update without seeing which objects will change. It does not establish the required correction; the decisive verification would be: The planned resource delta is visible without mutating cluster state, and the approved apply matches it.

Inspect the active kubeconfig context and explicitly select the authorized cluster before applying changes. That choice addresses a different foundational issue: An operator runs kubectl without selecting the intended cluster context and modifies a development workload by mistake. The issue at Juniper Media is instead: An operator runs a potentially destructive manifest update without seeing which objects will change. It does not establish the required correction; the decisive verification would be: The planned resource delta is visible without mutating cluster state, and the approved apply matches it.

Describe a ResourceQuota as enforcement of namespace consumption limits, not a node capacity provisioning request. That choice addresses a different foundational issue: A team assumes Kubernetes automatically provisions external cloud infrastructure for every ResourceQuota it creates. The issue at Juniper Media is instead: An operator runs a potentially destructive manifest update without seeing which objects will change. It does not establish the required correction; the decisive verification would be: The planned resource delta is visible without mutating cluster state, and the approved apply matches it.

Excess namespace resource creation is rejected by quota even though the cluster's physical nodes remain unchanged. That observed result would support another specific correction: Describe a ResourceQuota as enforcement of namespace consumption limits, not a node capacity provisioning request. The other scenario concerns: A team assumes Kubernetes automatically provisions external cloud infrastructure for every ResourceQuota it creates. The current Juniper Media problem is: An operator runs a potentially destructive manifest update without seeing which objects will change. The evidence required here is: The planned resource delta is visible without mutating cluster state, and the approved apply matches it.

The second approved manifest update adjusts the existing resource without creating a duplicate object. That observed result would support another specific correction: Use a declarative apply workflow for managed desired-state updates and confirm the resulting resource state. The other scenario concerns: A new administrator applies a manifest using a command that only creates new objects and fails when the named resource already exists. The current Juniper Media problem is: An operator runs a potentially destructive manifest update without seeing which objects will change. The evidence required here is: The planned resource delta is visible without mutating cluster state, and the approved apply matches it.

The Node listing works without a namespace filter while namespaced application resources remain scoped correctly. That observed result would support another specific correction: Recognize Nodes as cluster-scoped and use resource commands consistent with the object's scope. The other scenario concerns: A resource list shows both cluster-scoped and namespace-scoped items and an operator attempts to fetch a Node in a namespace. The current Juniper Media problem is: An operator runs a potentially destructive manifest update without seeing which objects will change. The evidence required here is: The planned resource delta is visible without mutating cluster state, and the approved apply matches it.

Request the resource with kubectl get using a machine-readable YAML or JSON output format. That choice addresses a different foundational issue: A platform analyst wants the exact YAML representation of an existing resource but repeatedly screenshots terminal output. The issue at Highland Education is instead: A platform team thinks Kubernetes Events are durable enough to serve as its only historical audit log for all administrator actions. It does not establish the required correction; the decisive verification would be: An authorized API change remains attributable in retained audit records after related Events have expired.

Use a declarative apply workflow for managed desired-state updates and confirm the resulting resource state. That choice addresses a different foundational issue: A new administrator applies a manifest using a command that only creates new objects and fails when the named resource already exists. The issue at Highland Education is instead: A platform team thinks Kubernetes Events are durable enough to serve as its only historical audit log for all administrator actions. It does not establish the required correction; the decisive verification would be: An authorized API change remains attributable in retained audit records after related Events have expired.

Use get for inventory and describe for resource details, events, and selected conditions when inspecting a resource. That choice addresses a different foundational issue: An engineer cannot distinguish kubectl get from kubectl describe and reads only a short status column during a fault. The issue at Highland Education is instead: A platform team thinks Kubernetes Events are durable enough to serve as its only historical audit log for all administrator actions. It does not establish the required correction; the decisive verification would be: An authorized API change remains attributable in retained audit records after related Events have expired.

A controlled individual-object deletion leaves unrelated resources untouched and the expected namespace persists. That observed result would support another specific correction: Differentiate deleting an individual object from deleting its parent namespace, and inspect namespace contents before cleanup. The other scenario concerns: A namespace cleanup removes one configuration object but leaves the namespace and its workload resources intact unexpectedly. The current Highland Education problem is: A platform team thinks Kubernetes Events are durable enough to serve as its only historical audit log for all administrator actions. The evidence required here is: An authorized API change remains attributable in retained audit records after related Events have expired.

The second approved manifest update adjusts the existing resource without creating a duplicate object. That observed result would support another specific correction: Use a declarative apply workflow for managed desired-state updates and confirm the resulting resource state. The other scenario concerns: A new administrator applies a manifest using a command that only creates new objects and fails when the named resource already exists. The current Highland Education problem is: A platform team thinks Kubernetes Events are durable enough to serve as its only historical audit log for all administrator actions. The evidence required here is: An authorized API change remains attributable in retained audit records after related Events have expired.

An authorization check grants the required API action to the intended identity and denies it to an unrelated account. That observed result would support another specific correction: Bind the appropriate Role or ClusterRole to the intended subject using a namespaced or cluster-scoped binding. The other scenario concerns: An administrator expects RBAC rules to automatically grant permissions merely by creating a Role with no RoleBinding. The current Highland Education problem is: A platform team thinks Kubernetes Events are durable enough to serve as its only historical audit log for all administrator actions. The evidence required here is: An authorized API change remains attributable in retained audit records after related Events have expired.

Use the appropriate rollout status inspection and verify ready Pods before marking the release successful. That choice addresses a different foundational issue: A team changes a Deployment manifest but never checks whether rollout completed or became stuck. The issue at Eastshore Energy is instead: A platform team thinks Kubernetes Events are durable enough to serve as its only historical audit log for all administrator actions. It does not establish the required correction; the decisive verification would be: An authorized API change remains attributable in retained audit records after related Events have expired.

Inspect the Deployment's spec replicas and status fields separately from Service endpoint readiness. That choice addresses a different foundational issue: A cluster maintainer increases replicas but mistakes a Service's endpoint count for authoritative desired Deployment replicas. The issue at Eastshore Energy is instead: A platform team thinks Kubernetes Events are durable enough to serve as its only historical audit log for all administrator actions. It does not establish the required correction; the decisive verification would be: An authorized API change remains attributable in retained audit records after related Events have expired.

Use a least-privilege Role and RoleBinding scoped to the project namespace for ordinary namespaced operations. That choice addresses a different foundational issue: A team gives every project full cluster administrator access because the namespace-specific Role syntax is unfamiliar. The issue at Eastshore Energy is instead: A platform team thinks Kubernetes Events are durable enough to serve as its only historical audit log for all administrator actions. It does not establish the required correction; the decisive verification would be: An authorized API change remains attributable in retained audit records after related Events have expired.

The second approved manifest update adjusts the existing resource without creating a duplicate object. That observed result would support another specific correction: Use a declarative apply workflow for managed desired-state updates and confirm the resulting resource state. The other scenario concerns: A new administrator applies a manifest using a command that only creates new objects and fails when the named resource already exists. The current Eastshore Energy problem is: A platform team thinks Kubernetes Events are durable enough to serve as its only historical audit log for all administrator actions. The evidence required here is: An authorized API change remains attributable in retained audit records after related Events have expired.

The report distinguishes installed kubectl version from API server version and documents compatibility correctly. That observed result would support another specific correction: Check client and server version fields independently and follow supported version-skew guidance for client tooling. The other scenario concerns: An infrastructure group believes a kubectl client version mismatch automatically implies the cluster was upgraded. The current Eastshore Energy problem is: A platform team thinks Kubernetes Events are durable enough to serve as its only historical audit log for all administrator actions. The evidence required here is: An authorized API change remains attributable in retained audit records after related Events have expired.

The rollout reports completion and the newly created Pods become ready before the change is closed. That observed result would support another specific correction: Use the appropriate rollout status inspection and verify ready Pods before marking the release successful. The other scenario concerns: A team changes a Deployment manifest but never checks whether rollout completed or became stuck. The current Eastshore Energy problem is: A platform team thinks Kubernetes Events are durable enough to serve as its only historical audit log for all administrator actions. The evidence required here is: An authorized API change remains attributable in retained audit records after related Events have expired.

Check client and server version fields independently and follow supported version-skew guidance for client tooling. That choice addresses a different foundational issue: An infrastructure group believes a kubectl client version mismatch automatically implies the cluster was upgraded. The issue at Maplewood Schools is instead: A user copies a resource manifest between clusters while retaining server-generated uid and resourceVersion metadata. It does not establish the required correction; the decisive verification would be: The intended resource creates cleanly in the target cluster without conflicting immutable server-generated metadata.

Use a declarative apply workflow for managed desired-state updates and confirm the resulting resource state. That choice addresses a different foundational issue: A new administrator applies a manifest using a command that only creates new objects and fails when the named resource already exists. The issue at Maplewood Schools is instead: A user copies a resource manifest between clusters while retaining server-generated uid and resourceVersion metadata. It does not establish the required correction; the decisive verification would be: The intended resource creates cleanly in the target cluster without conflicting immutable server-generated metadata.

Recognize Nodes as cluster-scoped and use resource commands consistent with the object's scope. That choice addresses a different foundational issue: A resource list shows both cluster-scoped and namespace-scoped items and an operator attempts to fetch a Node in a namespace. The issue at Maplewood Schools is instead: A user copies a resource manifest between clusters while retaining server-generated uid and resourceVersion metadata. It does not establish the required correction; the decisive verification would be: The intended resource creates cleanly in the target cluster without conflicting immutable server-generated metadata.

The recorded output contains structured metadata and specification fields that can be reviewed without screenshots. That observed result would support another specific correction: Request the resource with kubectl get using a machine-readable YAML or JSON output format. The other scenario concerns: A platform analyst wants the exact YAML representation of an existing resource but repeatedly screenshots terminal output. The current Maplewood Schools problem is: A user copies a resource manifest between clusters while retaining server-generated uid and resourceVersion metadata. The evidence required here is: The intended resource creates cleanly in the target cluster without conflicting immutable server-generated metadata.

The second approved manifest update adjusts the existing resource without creating a duplicate object. That observed result would support another specific correction: Use a declarative apply workflow for managed desired-state updates and confirm the resulting resource state. The other scenario concerns: A new administrator applies a manifest using a command that only creates new objects and fails when the named resource already exists. The current Maplewood Schools problem is: A user copies a resource manifest between clusters while retaining server-generated uid and resourceVersion metadata. The evidence required here is: The intended resource creates cleanly in the target cluster without conflicting immutable server-generated metadata.

Excess namespace resource creation is rejected by quota even though the cluster's physical nodes remain unchanged. That observed result would support another specific correction: Describe a ResourceQuota as enforcement of namespace consumption limits, not a node capacity provisioning request. The other scenario concerns: A team assumes Kubernetes automatically provisions external cloud infrastructure for every ResourceQuota it creates. The current Maplewood Schools problem is: A user copies a resource manifest between clusters while retaining server-generated uid and resourceVersion metadata. The evidence required here is: The intended resource creates cleanly in the target cluster without conflicting immutable server-generated metadata.

Use the appropriate rollout status inspection and verify ready Pods before marking the release successful. That choice addresses a different foundational issue: A team changes a Deployment manifest but never checks whether rollout completed or became stuck. The issue at Brookside Manufacturing is instead: A user copies a resource manifest between clusters while retaining server-generated uid and resourceVersion metadata. It does not establish the required correction; the decisive verification would be: The intended resource creates cleanly in the target cluster without conflicting immutable server-generated metadata.

Recognize Nodes as cluster-scoped and use resource commands consistent with the object's scope. That choice addresses a different foundational issue: A resource list shows both cluster-scoped and namespace-scoped items and an operator attempts to fetch a Node in a namespace. The issue at Brookside Manufacturing is instead: A user copies a resource manifest between clusters while retaining server-generated uid and resourceVersion metadata. It does not establish the required correction; the decisive verification would be: The intended resource creates cleanly in the target cluster without conflicting immutable server-generated metadata.

Specify the correct namespace or inspect all permitted namespaces when looking for a resource. That choice addresses a different foundational issue: A user lists Pods without a namespace and concludes an application is missing although it runs in another namespace. The issue at Brookside Manufacturing is instead: A user copies a resource manifest between clusters while retaining server-generated uid and resourceVersion metadata. It does not establish the required correction; the decisive verification would be: The intended resource creates cleanly in the target cluster without conflicting immutable server-generated metadata.

The controller creates Pods on the previously working image and no longer restarts the faulty version. That observed result would support another specific correction: Use the Deployment's supported rollout undo or an explicitly reverted desired image version. The other scenario concerns: An operator rolls back a broken release by deleting all Pods without changing the controller's bad image specification. The current Brookside Manufacturing problem is: A user copies a resource manifest between clusters while retaining server-generated uid and resourceVersion metadata. The evidence required here is: The intended resource creates cleanly in the target cluster without conflicting immutable server-generated metadata.

An authorized API change remains attributable in retained audit records after related Events have expired. That observed result would support another specific correction: Use durable API audit logging and monitoring for security history rather than relying solely on short-lived Events. The other scenario concerns: A platform team thinks Kubernetes Events are durable enough to serve as its only historical audit log for all administrator actions. The current Brookside Manufacturing problem is: A user copies a resource manifest between clusters while retaining server-generated uid and resourceVersion metadata. The evidence required here is: The intended resource creates cleanly in the target cluster without conflicting immutable server-generated metadata.

The recorded output contains structured metadata and specification fields that can be reviewed without screenshots. That observed result would support another specific correction: Request the resource with kubectl get using a machine-readable YAML or JSON output format. The other scenario concerns: A platform analyst wants the exact YAML representation of an existing resource but repeatedly screenshots terminal output. The current Brookside Manufacturing problem is: A user copies a resource manifest between clusters while retaining server-generated uid and resourceVersion metadata. The evidence required here is: The intended resource creates cleanly in the target cluster without conflicting immutable server-generated metadata.