EX280 Application Deployment And Lifecycle — Timed 40 Questions

Question 1

An administrator needs to deploy a packaged Helm chart onto an OpenShift 4.14 cluster from a private Helm repository. Which oc command should be used to install the chart while securely managing repository credentials?

40 minute time limit — choose an answer to begin.

Accepted Answer

helm install my-release private-repo/chart-name --repo https://charts.example.com. The 'oc helm' CLI wrapper does not exist natively as 'oc helm'; however, Helm v3 integrates directly with Kubernetes/OpenShift clusters using standard 'helm install' or by configuring Helm repository add commands before installing. Alternatively, using 'oc apply' with pre-rendered manifests or 'helm install' directly against the cluster context is standard. Let's look at the standard Helm workflow used in OpenShift contexts.

Answer

oc adm helm install my-release private-repo/chart-name

Answer

oc create helmchart --name=my-release --source=private-repo

Answer

oc new-app --helm-chart=private-repo/chart-name

Question 2

How do you define a command to run immediately before a container starts, such as a database migration?

Accepted Answer

pre-deployment hook. A 'pre' lifecycle hook in the Deployment strategy allows you to run commands before the deployment starts.

Answer

startup-command

Answer

init-container

Answer

post-deployment hook

Question 3

An OpenShift administrator needs to trigger a rollback of a Deployment to its previous working revision after a failed update. Which oc command should be used?

Accepted Answer

oc rollout undo deployment/my-app. The oc rollout undo command reverts a deployment back to a previous revision in the rollout history.

Answer

oc update deployment/my-app --revision=previous

Answer

oc revert deployment/my-app

Answer

oc rollback deployment/my-app

Question 4

A developer has created a Kustomization file that applies a namespace prefix and some patches to base Kubernetes manifests. How can the developer apply these manifests to an OpenShift cluster using standard oc tooling without installing standalone Kustomize?

Accepted Answer

oc apply -k ./directory. The oc apply command includes built-in support for Kustomize via the -k flag, which processes a directory containing a kustomization.yaml file.

Answer

oc create -f kustomization.yaml

Answer

oc run -k ./directory

Answer

oc kustomize apply ./directory

Question 5

A DeploymentConfig in OpenShift has a Rolling strategy defined. Which parameter in the strategy configuration controls the maximum number of pods that can be created above the desired replica count during the update?

Accepted Answer

maxSurge. maxSurge controls how many pods can be scheduled above the desired number of pods during a rolling update.

Answer

interval

Answer

updatePeriodSeconds

Answer

maxUnavailable

Question 6

An administrator needs to deploy a Helm chart into an OpenShift cluster while overriding specific chart values using a local YAML file. Which Helm CLI command should be executed?

Accepted Answer

helm install my-release my-chart --values overrides.yaml. The helm install command with the -f or --values flag allows supplying a YAML file to override default chart values.

Answer

helm push my-chart --override overrides.yaml

Answer

helm deploy my-release my-chart --values overrides.yaml

Answer

helm apply -f overrides.yaml my-chart

Question 7

An administrator needs to view the rollout history of a DeploymentConfig named web-frontend. Which command accomplishes this?

Accepted Answer

oc rollout history dc/web-frontend. The oc rollout history command displays the revision history for a Deployment or DeploymentConfig.

Answer

oc describe dc/web-frontend

Answer

oc get revisions dc/web-frontend

Answer

oc log rollout dc/web-frontend

Question 8

A BuildConfig uses an S2I strategy and needs to pull private base images from a secured external container registry. Where must the administrator configure the pull credentials so the builder pod can authenticate?

Accepted Answer

In the BuildConfig spec under strategy.dockerStrategy.pullSecret or source/strategy configuration. BuildConfig objects use pushSecret or pullSecret configurations, specifically output.pushSecret for pushing images and source.secrets or a service account for pulling source/base images, but standard registry access for builds is often tied to the builder service account or a specified pushSecret/pullSecret. More precisely, pullSecret in the source or strategy block allows authenticating to registries.

Answer

In the ImageStream tag policy

Answer

In the Route resource annotations

Answer

In the global cluster OAuth configuration

Question 9

A developer wants to track multiple versions and tags of container images within an OpenShift cluster efficiently. Which OpenShift resource provides this capability?

Accepted Answer

ImageStream. ImageStreams allow developers to combine and track multiple versions of container images through tags without needing to manage the raw registry image references directly.

Answer

Route

Answer

DeploymentConfig

Answer

BuildConfig

Question 10

An administrator needs to deploy a containerized web application using a Git repository as the source without writing a Dockerfile. Which OpenShift build strategy should be used?

Accepted Answer

Source-to-Image (S2I) strategy. The Source-to-Image (S2I) build strategy builds reproducible container images from source code without requiring a Dockerfile, injecting the source code into a builder image.

Answer

Docker strategy

Answer

Custom strategy

Answer

Pipeline strategy

Question 11

A developer wants to inspect the generated Kubernetes manifests from a Helm chart without actually installing the chart into the OpenShift cluster. Which Helm command should be used?

Accepted Answer

helm template my-release my-chart. The helm template command renders the chart locally and outputs the resulting manifest YAML to stdout without installing it.

Answer

helm dry-run my-release my-chart

Answer

helm show chart my-chart

Answer

helm inspect values my-chart

Question 12

During an S2I build, an administrator needs to pass sensitive build arguments, such as subscription keys, without hardcoding them into the BuildConfig or exposing them in the final image history. How should this be handled?

Accepted Answer

Using build secrets mounted via the source secret or build strategy configuration. Secret mounting during builds allows referencing Kubernetes Secrets as build secrets that are available during the build process but not persisted in the output image layers.

Answer

Storing them in an ImageStream annotation

Answer

Defining them as plain environment variables in the BuildConfig spec

Answer

Injecting them via the Route host header

Question 13

An administrator needs to perform a canary deployment strategy using standard OpenShift Deployment resources (not DeploymentConfigs). What is the standard Kubernetes/OpenShift native mechanism to route a small percentage of traffic to the canary deployment?

Accepted Answer

Using an OpenShift Route with weighted backend services pointing to stable and canary Services. Standard Deployments do not have native percentage-based traffic splitting; an administrator must use a Service with multiple underlying selector labels alongside a Service Mesh, Ingress controller, or an OpenShift Route with weight configurations pointing to distinct Services. Specifically, OpenShift Routes support splitting traffic via weighted backends across multiple Services.

Answer

Setting the traffic-split annotation on the Deployment resource

Answer

Configuring weight parameters directly in the Deployment spec rollingUpdate strategy

Answer

Enabling canary mode in the ImageStream tag metadata

Question 14

A developer has deployed a Helm chart in OpenShift and needs to list all currently installed Helm releases in the current namespace. Which command should be used?

Accepted Answer

helm list. The helm list command shows all active Helm releases in the current namespace.

Answer

helm get releases

Answer

helm status

Answer

helm search installed

Question 15

An OpenShift cluster administrator needs to ensure that custom S2I builder images stored in an insecure internal registry can be successfully pulled by build pods without failing TLS verification. Where must the insecure registry be defined?

Accepted Answer

In the cluster Image resource configuration (imageregistry.config.openshift.io/cluster or image.config.openshift.io). Insecure registries must be configured in the cluster-wide Image.config.openshift.io/cluster resource (or registry configuration) so the container runtime and build machinery trust the registry.

Answer

In the OAuth client definition

Answer

In the individual BuildConfig strategy environment variables

Answer

In the Project request template metadata

Question 16

An administrator wants to pause rollouts on a DeploymentConfig named backend-api to make multiple configuration changes without triggering intermediate builds or rollouts. Which command pauses the rollout?

Accepted Answer

oc rollout pause dc/backend-api. The oc rollout pause command suspends rollout updates on a Deployment or DeploymentConfig.

Answer

oc patch dc/backend-api --type=json -p='[{"op": "add", "path": "/spec/paused", "value": true}]'

Answer

oc suspend dc/backend-api

Answer

oc stop rollout dc/backend-api

Question 17

An administrator needs to configure a BuildConfig so that whenever a new image is pushed to a dependent ImageStream tag, a new build is automatically triggered. Which trigger type must be added to the BuildConfig?

Accepted Answer

ImageChange. An ImageChange build trigger automatically starts a new build when the referenced ImageStream tag changes.

Answer

Webhook

Answer

Periodic

Answer

ConfigChange

Question 18

An administrator needs to completely remove a Helm release named my-redis from the cluster, including its history. Which Helm command should be executed?

Accepted Answer

helm uninstall my-redis. The helm uninstall command removes the release and its associated history from the cluster.

Answer

helm remove my-redis

Answer

helm delete my-redis --purge

Answer

helm drop my-redis

Question 19

A developer is using Kustomize to manage environment overlays (dev and prod) for an OpenShift application. Where should the common base resources be referenced in the prod/kustomization.yaml file?

Accepted Answer

Under the resources: key. Kustomize overlays reference shared base manifests using the resources field pointing to the relative path of the base directory.

Answer

Under the includes: key

Answer

Under the bases: key

Answer

Under the overlays: key

Question 20

An administrator is configuring a DeploymentConfig in OpenShift and wants to set up automated triggers for new rollouts. Which TWO trigger types are natively supported in a DeploymentConfig spec? (Choose two.)

Accepted Answer

ConfigChange. DeploymentConfigs support ConfigChange (triggering when the DeploymentConfig template changes) and ImageChange (triggering when a referenced ImageStream tag updates).

Answer

PeriodicTrigger

Answer

WebhookTrigger

Answer

GitTrigger