Exam Bundle

The incident timeline identifies the exact application artifact and Kubernetes rollout revision running when the fault occurred. That observed result would support another specific correction: Publish immutable versioned image references and retain release metadata linking a commit to its deployed digest. The other scenario concerns: A team creates a Deployment with an identical application tag for every release and cannot correlate an incident to code. The current Brookside Manufacturing problem is: An application requires blue-green deployment but the team updates the shared Service selector before testing the green environment. The evidence required here is: The green version passes health and acceptance tests before clients are directed to it, with a working rollback path.

A simulated failed rollout restores a known good revision and its exact image digest is still retrievable. That observed result would support another specific correction: Retain suitable Deployment revision history and keep verified release images available for controlled rollback. The other scenario concerns: A delivery team deletes older ReplicaSets after every rollout and later discovers there is no supported revision to undo. The current Brookside Manufacturing problem is: An application requires blue-green deployment but the team updates the shared Service selector before testing the green environment. The evidence required here is: The green version passes health and acceptance tests before clients are directed to it, with a working rollback path.

Dev, staging and production show their intended parameter differences without untracked live drift. That observed result would support another specific correction: Use declarative environment overlays or configuration values under version control with a reproducible promotion process. The other scenario concerns: An application is configured in three environments through manual edits that leave different values undocumented. The current Brookside Manufacturing problem is: An application requires blue-green deployment but the team updates the shared Service selector before testing the green environment. The evidence required here is: The green version passes health and acceptance tests before clients are directed to it, with a working rollback path.

Use the HPA's supported desired behavior and define min/max replicas rather than continually overriding controller intent. That choice addresses a different foundational issue: An engineer scales an application manually during every traffic spike while an approved HPA already controls its replica target. The issue at Juniper Media is instead: An application requires blue-green deployment but the team updates the shared Service selector before testing the green environment. It does not establish the required correction; the decisive verification would be: The green version passes health and acceptance tests before clients are directed to it, with a working rollback path.

Retain suitable Deployment revision history and keep verified release images available for controlled rollback. That choice addresses a different foundational issue: A delivery team deletes older ReplicaSets after every rollout and later discovers there is no supported revision to undo. The issue at Juniper Media is instead: An application requires blue-green deployment but the team updates the shared Service selector before testing the green environment. It does not establish the required correction; the decisive verification would be: The green version passes health and acceptance tests before clients are directed to it, with a working rollback path.

Explain that GitOps uses version-controlled desired state with controlled reconciliation and separate authorization boundaries. That choice addresses a different foundational issue: A platform team describes GitOps as granting every repository reader administrative kubectl access to the cluster. The issue at Juniper Media is instead: An application requires blue-green deployment but the team updates the shared Service selector before testing the green environment. It does not establish the required correction; the decisive verification would be: The green version passes health and acceptance tests before clients are directed to it, with a working rollback path.

The release can be reproduced from version-controlled inputs and the target Deployment reports its new image version. That observed result would support another specific correction: Use a repeatable deployment pipeline that publishes a versioned image and updates declarative Kubernetes manifests. The other scenario concerns: An organization merges code frequently but deploys new versions by manually copying files into running containers. The current Juniper Media problem is: An application requires blue-green deployment but the team updates the shared Service selector before testing the green environment. The evidence required here is: The green version passes health and acceptance tests before clients are directed to it, with a working rollback path.

The pipeline rejects a failing commit before publishing or deploying an unverified application image. That observed result would support another specific correction: Establish automated build and test validation in CI, with a separate approved continuous delivery or deployment stage. The other scenario concerns: A release team pushes untested images directly into production and calls the sequence continuous integration. The current Juniper Media problem is: An application requires blue-green deployment but the team updates the shared Service selector before testing the green environment. The evidence required here is: The green version passes health and acceptance tests before clients are directed to it, with a working rollback path.

The release changes Pod replica count without asserting new nodes were added unless a separate capacity mechanism runs. That observed result would support another specific correction: Distinguish workload replica scaling from underlying cluster/node autoscaling in the delivery design. The other scenario concerns: A release engineer increases Deployment replicas and describes the change as horizontal node autoscaling. The current Juniper Media problem is: An application requires blue-green deployment but the team updates the shared Service selector before testing the green environment. The evidence required here is: The green version passes health and acceptance tests before clients are directed to it, with a working rollback path.

Supply supported resource or custom metrics with appropriate requests and a working metrics adapter for autoscaling. That choice addresses a different foundational issue: A team tries to use an HPA without any usable metrics source and assumes it will infer load from container image size. The issue at Highland Education is instead: A release engineer increases Deployment replicas and describes the change as horizontal node autoscaling. It does not establish the required correction; the decisive verification would be: The release changes Pod replica count without asserting new nodes were added unless a separate capacity mechanism runs.

Include appropriate readiness and startup checks as part of a tested declarative release specification. That choice addresses a different foundational issue: An operator applies a new Deployment manifest but removes a container health check that guarded the previous release. The issue at Highland Education is instead: A release engineer increases Deployment replicas and describes the change as horizontal node autoscaling. It does not establish the required correction; the decisive verification would be: The release changes Pod replica count without asserting new nodes were added unless a separate capacity mechanism runs.

Run and validate a separate green version before atomically switching the intended traffic selection. That choice addresses a different foundational issue: An application requires blue-green deployment but the team updates the shared Service selector before testing the green environment. The issue at Highland Education is instead: A release engineer increases Deployment replicas and describes the change as horizontal node autoscaling. It does not establish the required correction; the decisive verification would be: The release changes Pod replica count without asserting new nodes were added unless a separate capacity mechanism runs.

A repository change follows review and audit controls while ordinary read access grants no direct cluster administrator privilege. That observed result would support another specific correction: Explain that GitOps uses version-controlled desired state with controlled reconciliation and separate authorization boundaries. The other scenario concerns: A platform team describes GitOps as granting every repository reader administrative kubectl access to the cluster. The current Highland Education problem is: A release engineer increases Deployment replicas and describes the change as horizontal node autoscaling. The evidence required here is: The release changes Pod replica count without asserting new nodes were added unless a separate capacity mechanism runs.

The new version first receives a bounded subset of requests and is expanded only after acceptance signals pass. That observed result would support another specific correction: Use a supported canary or progressive delivery strategy with measured traffic and explicit rollback criteria. The other scenario concerns: A rollout requires gradual exposure to a risky new version but the team switches all production requests instantly. The current Highland Education problem is: A release engineer increases Deployment replicas and describes the change as horizontal node autoscaling. The evidence required here is: The release changes Pod replica count without asserting new nodes were added unless a separate capacity mechanism runs.

Multiple apps render consistent manifests from one maintained package while retaining their approved environment settings. That observed result would support another specific correction: Use a reusable and versioned Helm chart or appropriate configuration template with explicit per-app values. The other scenario concerns: A project copies the same long Kubernetes manifest into twenty application repositories and struggles with consistent upgrades. The current Highland Education problem is: A release engineer increases Deployment replicas and describes the change as horizontal node autoscaling. The evidence required here is: The release changes Pod replica count without asserting new nodes were added unless a separate capacity mechanism runs.

Publish immutable versioned image references and retain release metadata linking a commit to its deployed digest. That choice addresses a different foundational issue: A team creates a Deployment with an identical application tag for every release and cannot correlate an incident to code. The issue at Eastshore Energy is instead: A release engineer increases Deployment replicas and describes the change as horizontal node autoscaling. It does not establish the required correction; the decisive verification would be: The release changes Pod replica count without asserting new nodes were added unless a separate capacity mechanism runs.

Explain that Kustomize customizes declarative manifests before API submission, rather than acting as a cluster runtime. That choice addresses a different foundational issue: A team changes a Kustomize overlay expecting it to create a runtime configuration service on a worker. The issue at Eastshore Energy is instead: A release engineer increases Deployment replicas and describes the change as horizontal node autoscaling. It does not establish the required correction; the decisive verification would be: The release changes Pod replica count without asserting new nodes were added unless a separate capacity mechanism runs.

Use a repeatable deployment pipeline that publishes a versioned image and updates declarative Kubernetes manifests. That choice addresses a different foundational issue: An organization merges code frequently but deploys new versions by manually copying files into running containers. The issue at Eastshore Energy is instead: A release engineer increases Deployment replicas and describes the change as horizontal node autoscaling. It does not establish the required correction; the decisive verification would be: The release changes Pod replica count without asserting new nodes were added unless a separate capacity mechanism runs.

The new version first receives a bounded subset of requests and is expanded only after acceptance signals pass. That observed result would support another specific correction: Use a supported canary or progressive delivery strategy with measured traffic and explicit rollback criteria. The other scenario concerns: A rollout requires gradual exposure to a risky new version but the team switches all production requests instantly. The current Eastshore Energy problem is: A release engineer increases Deployment replicas and describes the change as horizontal node autoscaling. The evidence required here is: The release changes Pod replica count without asserting new nodes were added unless a separate capacity mechanism runs.

The pipeline verifies that new Pods become ready before they receive normal production Service traffic. That observed result would support another specific correction: Include appropriate readiness and startup checks as part of a tested declarative release specification. The other scenario concerns: An operator applies a new Deployment manifest but removes a container health check that guarded the previous release. The current Eastshore Energy problem is: A release engineer increases Deployment replicas and describes the change as horizontal node autoscaling. The evidence required here is: The release changes Pod replica count without asserting new nodes were added unless a separate capacity mechanism runs.

The release can be reproduced from version-controlled inputs and the target Deployment reports its new image version. That observed result would support another specific correction: Use a repeatable deployment pipeline that publishes a versioned image and updates declarative Kubernetes manifests. The other scenario concerns: An organization merges code frequently but deploys new versions by manually copying files into running containers. The current Eastshore Energy problem is: A release engineer increases Deployment replicas and describes the change as horizontal node autoscaling. The evidence required here is: The release changes Pod replica count without asserting new nodes were added unless a separate capacity mechanism runs.

Establish automated build and test validation in CI, with a separate approved continuous delivery or deployment stage. That choice addresses a different foundational issue: A release team pushes untested images directly into production and calls the sequence continuous integration. The issue at Maplewood Schools is instead: A team tries to use an HPA without any usable metrics source and assumes it will infer load from container image size. It does not establish the required correction; the decisive verification would be: The HPA displays valid current metrics and adjusts replicas after an authorized load change.

Use the HPA's supported desired behavior and define min/max replicas rather than continually overriding controller intent. That choice addresses a different foundational issue: An engineer scales an application manually during every traffic spike while an approved HPA already controls its replica target. The issue at Maplewood Schools is instead: A team tries to use an HPA without any usable metrics source and assumes it will infer load from container image size. It does not establish the required correction; the decisive verification would be: The HPA displays valid current metrics and adjusts replicas after an authorized load change.

Explain that GitOps uses version-controlled desired state with controlled reconciliation and separate authorization boundaries. That choice addresses a different foundational issue: A platform team describes GitOps as granting every repository reader administrative kubectl access to the cluster. The issue at Maplewood Schools is instead: A team tries to use an HPA without any usable metrics source and assumes it will infer load from container image size. It does not establish the required correction; the decisive verification would be: The HPA displays valid current metrics and adjusts replicas after an authorized load change.

The production rollout starts with image pulls succeeding and no missing-credential failure during the first Pod startup. That observed result would support another specific correction: Add pre-deployment checks for registry access, required Secrets and namespace permissions before promotion. The other scenario concerns: A software team promotes manifests without checking whether container registry credentials exist in the target environment. The current Maplewood Schools problem is: A team tries to use an HPA without any usable metrics source and assumes it will infer load from container image size. The evidence required here is: The HPA displays valid current metrics and adjusts replicas after an authorized load change.

Multiple apps render consistent manifests from one maintained package while retaining their approved environment settings. That observed result would support another specific correction: Use a reusable and versioned Helm chart or appropriate configuration template with explicit per-app values. The other scenario concerns: A project copies the same long Kubernetes manifest into twenty application repositories and struggles with consistent upgrades. The current Maplewood Schools problem is: A team tries to use an HPA without any usable metrics source and assumes it will infer load from container image size. The evidence required here is: The HPA displays valid current metrics and adjusts replicas after an authorized load change.

The green version passes health and acceptance tests before clients are directed to it, with a working rollback path. That observed result would support another specific correction: Run and validate a separate green version before atomically switching the intended traffic selection. The other scenario concerns: An application requires blue-green deployment but the team updates the shared Service selector before testing the green environment. The current Maplewood Schools problem is: A team tries to use an HPA without any usable metrics source and assumes it will infer load from container image size. The evidence required here is: The HPA displays valid current metrics and adjusts replicas after an authorized load change.

Validate the template rendering and configuration values before applying the resulting Kubernetes resources. That choice addresses a different foundational issue: A release build fails because a Helm values file references a nonexistent key and the team deploys unrendered templates anyway. The issue at Brookside Manufacturing is instead: A team tries to use an HPA without any usable metrics source and assumes it will infer load from container image size. It does not establish the required correction; the decisive verification would be: The HPA displays valid current metrics and adjusts replicas after an authorized load change.

Describe Helm as a packaging and release tool that renders and manages Kubernetes resource definitions. That choice addresses a different foundational issue: A team believes Helm charts run containers by themselves and expects an installed chart to replace Kubernetes controllers. The issue at Brookside Manufacturing is instead: A team tries to use an HPA without any usable metrics source and assumes it will infer load from container image size. It does not establish the required correction; the decisive verification would be: The HPA displays valid current metrics and adjusts replicas after an authorized load change.

Explain that GitOps uses version-controlled desired state with controlled reconciliation and separate authorization boundaries. That choice addresses a different foundational issue: A platform team describes GitOps as granting every repository reader administrative kubectl access to the cluster. The issue at Brookside Manufacturing is instead: A team tries to use an HPA without any usable metrics source and assumes it will infer load from container image size. It does not establish the required correction; the decisive verification would be: The HPA displays valid current metrics and adjusts replicas after an authorized load change.

A representative rollout keeps the agreed minimum number of ready replicas available throughout the update. That observed result would support another specific correction: Configure suitable rolling update availability parameters and readiness probes to preserve service continuity. The other scenario concerns: A rolling update becomes unavailable because all old Pods are removed before any replacements pass readiness. The current Brookside Manufacturing problem is: A team tries to use an HPA without any usable metrics source and assumes it will infer load from container image size. The evidence required here is: The HPA displays valid current metrics and adjusts replicas after an authorized load change.

The green version passes health and acceptance tests before clients are directed to it, with a working rollback path. That observed result would support another specific correction: Run and validate a separate green version before atomically switching the intended traffic selection. The other scenario concerns: An application requires blue-green deployment but the team updates the shared Service selector before testing the green environment. The current Brookside Manufacturing problem is: A team tries to use an HPA without any usable metrics source and assumes it will infer load from container image size. The evidence required here is: The HPA displays valid current metrics and adjusts replicas after an authorized load change.

A simulated failed rollout restores a known good revision and its exact image digest is still retrievable. That observed result would support another specific correction: Retain suitable Deployment revision history and keep verified release images available for controlled rollback. The other scenario concerns: A delivery team deletes older ReplicaSets after every rollout and later discovers there is no supported revision to undo. The current Brookside Manufacturing problem is: A team tries to use an HPA without any usable metrics source and assumes it will infer load from container image size. The evidence required here is: The HPA displays valid current metrics and adjusts replicas after an authorized load change.