Free EX180 sample questions

Correct answer: oc login https://api.ocp.fintechcorp.com:6443 -u admin

The correct command to authenticate to an OpenShift cluster using the CLI is `oc login`. You specify the API server URL and can optionally pass the username with `-u`. This command prompts for a password and automatically updates the kubeconfig file with the new cluster context and authentication token. The other commands are syntactically incorrect or do not exist in the OpenShift CLI.

Correct answer: oc config use-context

The `oc config use-context` command allows you to switch between different contexts stored in your kubeconfig file. A context is a combination of a cluster, a user, and a namespace. Since the administrator is already authenticated, switching the context instantly points their CLI to the production cluster without needing to log in again.

Correct answer: oc explain DeploymentConfig.spec.strategy

The `oc explain` command is designed specifically to explore the API documentation of Kubernetes and OpenShift resources directly from the CLI. By typing `oc explain DeploymentConfig.spec.strategy`, the developer will see a description of the field, its type, and its nested sub-fields.

Correct answer: oc describe pod payment-gateway-7b99c5

The `oc describe pod` command provides a detailed, human-readable overview of the pod's lifecycle. Under the 'Containers' section, it shows the 'State' (current) and 'Last State' (previous), which includes the exact Exit Code and Reason for the termination that caused the CrashLoopBackOff. While `oc logs --previous` shows the logs, it does not explicitly state the container exit code. flowchart TD A[Pod in CrashLoopBackOff] --> B{What information is needed?} B -->|Application Output| C[oc logs --previous] B -->|Exit Code & State| D[oc describe pod] D --> E[Look at 'Last State' section]

Correct answers: oc get svc frontend-svc -o yaml | yq 'del(.metadata.resourceVersion, .metadata.uid, .metadata.creationTimestamp)' > service.yaml; oc get svc frontend-svc -o yaml > service.yaml (and manually remove metadata)

Using `oc get -o yaml` combined with a YAML processor like `yq` is the standard modern approach to strip cluster-specific metadata, as the old `oc export` command has been deprecated and removed from OpenShift 4.x CLIs.

Using `oc get svc frontend-svc -o yaml` will export the resource, though it requires manual cleanup of cluster-specific metadata (since `oc export` is deprecated/removed in newer OCP versions). Another valid approach is using `oc get` with the `--export` flag (if supported in the specific CLI version) or parsing with tools like `yq` or `jq`.

Correct answer: oc adm must-gather

The `oc adm must-gather` command is the standard OpenShift utility used to collect comprehensive diagnostic information (logs, resource definitions, cluster state) across the entire cluster. This data is packaged into a tarball that can be attached to a Red Hat Support ticket.