20+ practice questions focused on Application Deployment And Lifecycle — one of the most tested topics on the Red Hat Certified OpenShift Administrator (EX280, OpenShift Container Platform 4.14+) (EX280) exam. Each question includes a detailed explanation so you learn why the right answer is correct.
Start Application Deployment And Lifecycle PracticeA 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?
Explanation: For an S2I BuildConfig, pull credentials for private base images are configured in the BuildConfig's strategy section, specifically under `strategy.sourceStrategy.pullSecret` (for S2I) or `strategy.dockerStrategy.pullSecret` (for Docker strategy). This secret is used by the builder pod to authenticate to the registry.
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?
Explanation: The cluster-wide image configuration resource (image.config.openshift.io/cluster) contains the registrySources section where insecure registries are listed. This configuration is consumed by the internal registry, build pods, and kubelet to determine which registries should be contacted without TLS verification. By defining the insecure registry here, all builds and pods across the cluster can pull from it without certificate errors.
An administrator is troubleshooting a failed OpenShift build. Which THREE resources or logs should the administrator check to diagnose the failure? (Choose three.)
Explanation: Option A is correct because running `oc logs build/<build-name>` retrieves the aggregated logs of the build pod, showing the exact output of the build steps and any errors that caused the failure. Option C is correct because inspecting the BuildConfig with `oc get bc/<name> -o yaml` reveals the build strategy (Source, Docker, or Custom), source references, triggers, and output configuration, which are common sources of build misconfiguration. Option E is correct because `oc get events` in the namespace surfaces scheduling failures, image pull errors, quota or limit issues, and other Kubernetes-level events that explain why a build pod could not run or complete. Option B is not relevant because storage class definitions are cluster-scoped and only matter if the build uses a volume that depends on them, which is not indicated here. Option D is not relevant because the default OAuth client secret relates to authentication and identity provider configuration, not to build execution or build pod failures.
An administrator needs to configure a Deployment strategy in OpenShift. Which THREE deployment strategy types are natively supported by standard Kubernetes/OpenShift Deployments? (Choose three.)
Explanation: Option A is correct because OpenShift's DeploymentConfig resource natively supports the Rolling strategy (with parameters like maxSurge and maxUnavailable), which is the equivalent of the RollingUpdate strategy used by standard Kubernetes Deployments. Option C is correct because Recreate is a natively supported strategy in both Kubernetes Deployments and OpenShift DeploymentConfigs, terminating all existing pods before creating new ones, which is useful when the application cannot run multiple versions concurrently. Option E is correct because RollingUpdate is the default strategy for standard Kubernetes Deployments (and thus OpenShift Deployments), incrementally replacing pods to maintain availability during an update. Option B is not correct because BlueGreen is not a native strategy type; it must be implemented manually or via routes/services and additional tooling such as Argo Rollouts. Option D is not correct because Canvas is not a deployment strategy in Kubernetes or OpenShift; it is unrelated to the Deployment spec's strategy field.
A production Deployment using the Rolling update strategy is failing its readiness probe during a rollout, causing the update to block and eventually time out. You need to inspect the reason for the rollout failure using the OpenShift CLI without deleting the failing pods immediately. Which oc command provides the most direct diagnostic information regarding the rollout status and blockage reason?
Explanation: 'oc rollout status deployment/<name>' streams the rollout progress and reports the specific reason the rollout is blocked, such as 'Waiting for deployment spec update to be observed' or 'deployment <name> is not progressing: ReplicaSet has timed out progressing'. It is the most direct CLI command for diagnosing rollout blockage without deleting pods.
+15 more Application Deployment And Lifecycle questions available
Practice all Application Deployment And Lifecycle questions1. Baseline your knowledge
Start with 10 questions to gauge your current understanding of Application Deployment And Lifecycle. This tells you whether you need a concept refresher or just practice.
2. Review every explanation
For each question — right or wrong — read the full explanation. Understanding why an answer is correct is more valuable than knowing the answer itself.
3. Focus on exam traps
Application Deployment And Lifecycle questions on the EX280 frequently use trap wording. Look for subtle differences in answers that test your precision, not just general knowledge.
4. Reach 80% consistently
Do repeated sessions until you score 80%+ three times in a row. Then move to mixed-mode practice to test cross-topic recall under realistic conditions.
The exact number varies per candidate. Application Deployment And Lifecycle is tested as part of the Red Hat Certified OpenShift Administrator (EX280, OpenShift Container Platform 4.14+) (EX280) blueprint. Practicing with targeted Application Deployment And Lifecycle questions ensures you can handle any format or difficulty that appears.
Yes. Courseiva provides free EX280 practice questions across all exam topics and domains. The platform includes topic-based practice, mock exams, missed-question review, bookmarked questions, and readiness tracking — no account required.
Difficulty is subjective, but Application Deployment And Lifecycle is a high-priority exam concept tested in multiple ways — direct recall, scenario analysis, and command-output interpretation. Consistent practice is the best way to build confidence.
Launch a full Application Deployment And Lifecycle practice session with instant scoring and detailed explanations.
Start Application Deployment And Lifecycle Practice →