EX280 Cluster Installation And Management Practice Test 4 — 15 Questions

Question 1

An administrator is inspecting an OpenShift 4.14 cluster and notices that the MachineConfigPool for workers is in a degraded state because a MachineConfig failed to apply. Where should the administrator look to find the exact error encountered by the Machine Config Daemon on the affected nodes?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

Check the logs of the machine-config-daemon pods in the openshift-machine-config-operator namespace.. The Machine Config Daemon runs as a pod on each node in the openshift-machine-config-operator namespace and is responsible for applying rendered MachineConfigs and reporting errors back to the MCO. When a MachineConfig fails to apply and the pool goes degraded, the exact error (e.g., failed systemd unit, invalid Ignition, file conflict) is recorded in the machine-config-daemon pod logs on the affected node.

Answer

Review the OperatorHub catalog source logs in openshift-marketplace.

Answer

Run 'oc adm node-logs --role=worker' to view kernel panic messages.

Answer

Inspect the Cluster Version Operator logs in openshift-cluster-version.

Question 2

Which OpenShift 4.14 command is used to uncordon a worker node and return it to a schedulable state after maintenance?

Accepted Answer

oc adm uncordon. The correct command is `oc adm uncordon <node-name>`. This command removes the unschedulable taint from the node, allowing the scheduler to place new pods on it. It is the standard OpenShift/Kubernetes administrative command for reversing a cordon operation.

Answer

oc node enable

Answer

oc adm schedulable

Answer

oc scale node

Question 3

An administrator wants to check the health and availability status of all core OpenShift 4.14 cluster operators (such as authentication, ingress, and dns). Which command should be used?

Accepted Answer

oc get clusteroperators. In OpenShift 4.x, cluster operators are managed by the Cluster Version Operator and their health is exposed via the clusteroperators resource. Running oc get clusteroperators (or oc get co) lists each operator with AVAILABLE, PROGRESSING, and DEGRADED status columns, which is exactly what the administrator needs to check core operator health.

Answer

oc get csv

Answer

oc get operators --all-namespaces

Answer

oc adm cluster-health

Question 4

What is the primary role of Operator Lifecycle Manager (OLM) in OpenShift 4.14?

Accepted Answer

Managing the installation, upgrades, and RBAC lifecycle of Operators in the cluster.. Operator Lifecycle Manager (OLM) is the OpenShift component that provides a declarative way to install, upgrade, and manage the lifecycle of Operators and their associated RBAC. It introduces Custom Resource Definitions (CRDs) like ClusterServiceVersion (CSV), Subscription, and InstallPlan to automate dependency resolution, version upgrades, and permission grants. OLM ensures Operators are installed with the correct service accounts, roles, and role bindings, and it handles upgrades through channels and approval strategies. Thus, option A accurately captures OLM's primary role.

Answer

Monitoring node CPU and memory utilization thresholds.

Answer

Provisioning physical bare-metal servers for cluster expansion.

Answer

Encrypting etcd database contents at rest.

Question 5

An administrator wants to check why a specific MachineConfigPool is taking a long time to complete an update. Which status condition on the MachineConfigPool indicates that nodes are currently being updated?

Accepted Answer

Updating=True. The MachineConfigPool (MCP) status includes a condition of type 'Updating'. When this condition's status is 'True', it explicitly indicates that the pool is actively applying configuration changes to its nodes. This is the standard condition used by the Machine Config Operator (MCO) to signal that an update is in progress. Therefore, option A is correct.

Answer

RollingOut=Running

Answer

Reconciling=Pending

Answer

Progressing=Active

Question 6

Which namespace contains the Machine Config Operator (MCO) and its associated daemon pods in OpenShift 4.14?

Accepted Answer

openshift-machine-config-operator. The Machine Config Operator (MCO) in OpenShift 4.14 runs in the `openshift-machine-config-operator` namespace. This namespace hosts the MCO deployment and its associated daemon pods (machine-config-daemon) that apply machine configurations to nodes. The other namespaces serve different cluster functions.

Answer

openshift-infra

Answer

openshift-machine-api

Answer

openshift-cluster-version

Question 7

Which component in OpenShift 4.14 manages the creation and deletion of compute machines (VMs or physical servers) on cloud providers or bare metal?

Accepted Answer

Machine API Operator. The Machine API Operator manages the lifecycle of compute machines (VMs or physical servers) by creating and deleting Machine objects, which are backed by cloud provider or bare metal integrations. It runs in the openshift-machine-api namespace and works with the Cluster API to provision nodes.

Answer

Operator Lifecycle Manager

Answer

Machine Config Operator

Answer

Cluster Version Operator

Question 8

An administrator needs to verify that the cluster autoscaler is successfully scaling worker nodes in response to pending pods. Which custom resource should the administrator inspect to check the autoscaler configuration and status?

Accepted Answer

ClusterAutoscaler and MachineAutoscaler. The ClusterAutoscaler and MachineAutoscaler custom resources are used to configure and check the status of the cluster autoscaler in OpenShift. The ClusterAutoscaler defines the overall autoscaling behavior, while MachineAutoscaler specifies which MachineSets are eligible for scaling. Inspecting these resources reveals whether scaling is occurring and any issues.

Answer

NodeScalingOperator resource

Answer

MachineConfigPool autoscaler status

Answer

ClusterVersion autoscaling spec

Question 9

An administrator needs to check the status of all MachineSets in an OpenShift 4.14 cluster to see how many worker machines are currently provisioned and running. Which command should be used?

Accepted Answer

oc get machinesets -A (or within openshift-machine-api). MachineSets are the OpenShift 4 resource that manages the desired and current number of machines per availability zone for a pool. Running 'oc get machinesets -A' (or scoped to openshift-machine-api) lists all MachineSets with their desired, current, and ready replica counts, which is exactly what the administrator needs to see how many worker machines are provisioned and running.

Answer

oc adm get machines

Answer

oc get cluster-infrastructure

Answer

oc get machineconfigpools

Question 10

An administrator wants to inspect the ignition configuration generated for worker nodes by the Machine Config Operator. Which command or resource should the administrator examine?

Accepted Answer

Inspect the rendered MachineConfig objects (e.g., rendered-worker-*) managed by the MCO.. The Machine Config Operator (MCO) generates rendered MachineConfig objects named rendered-worker-* (and rendered-master-*) that contain the final, merged ignition configuration for each machine pool. These rendered objects are the authoritative source for inspecting what ignition config will actually be applied to worker nodes, combining all MachineConfigs, kubelet configs, and container runtime settings. Inspecting these rendered objects via 'oc get machineconfig rendered-worker-<hash> -o yaml' reveals the complete ignition payload, including systemd units, files, and kernel arguments.

Answer

Run 'oc adm inspect ignition-configs'.

Answer

Check the ConfigMap named 'ignition-worker' in the default namespace.

Answer

View the ClusterVersion status conditions.

Question 11

What is the primary function of a MachineSet in an OpenShift 4.14 cluster running on a cloud provider?

Accepted Answer

To ensure a specified number of identical machine instances are running and healthy.. A MachineSet's primary function is to maintain a declared number of identical Machine objects (and therefore Nodes) in an OpenShift 4 cluster. It is the cloud-provider-aware controller that reconciles desired replica count with actual running instances, replacing failed or deleted machines automatically.

Answer

To load balance ingress traffic across worker nodes.

Answer

To manage persistent volume claims across storage backends.

Answer

To group cluster nodes by operating system kernel version.

Question 12

An administrator has added a new custom worker MachineConfigPool and wants existing worker nodes to be migrated into this new pool based on specific labels. How does an administrator move a node from the default worker pool to a custom MachineConfigPool?

Accepted Answer

Apply the corresponding role label to the node (e.g., 'oc label node worker-01 node-role.kubernetes.io/custom-worker='').. To move a node from the default worker pool to a custom MachineConfigPool, you apply the corresponding role label to the node. For example, labeling a node with 'node-role.kubernetes.io/custom-worker=' will make the MachineConfigOperator include it in the custom-worker pool. This is the standard method for node pool migration.

Answer

Modify the cluster-wide node migration ConfigMap.

Answer

Edit the MachineSet to change its target pool name.

Answer

Run 'oc adm migrate node worker-01 --to-pool=custom-worker'.

Question 13

Which component in OpenShift 4.14 serves as the API entry point for managing MachineAPI resources like Machines and MachineSets?

Accepted Answer

Machine API Operator. The Machine API Operator is the component that manages the lifecycle of MachineAPI resources such as Machines, MachineSets, and MachineHealthChecks. It deploys and reconciles the machine-api controllers and CRDs, making it the API entry point for cluster node provisioning in OpenShift 4.

Answer

Cluster Version Operator

Answer

Machine Config Operator

Answer

Operator Lifecycle Manager

Question 14

An administrator wants to verify if the OpenShift cluster upgrade to version 4.14 has successfully completed for all core components. Which status field in the ClusterVersion resource should show 'True' for the progressing and available conditions?

Accepted Answer

Available=True and Progressing=False. The ClusterVersion resource exposes two key conditions: Available and Progressing. When an upgrade finishes successfully, the cluster reports Available=True (the cluster is healthy and all components are operational) and Progressing=False (no upgrade or configuration change is currently in flight). This combination is the canonical signal that the OpenShift 4.14 upgrade has completed for all core components.

Answer

Completed=True and Ready=True

Answer

Available=False and Progressing=True

Answer

Upgraded=True and Finished=True

Question 15

Which OpenShift 4.14 command allows an administrator to gather cluster-wide diagnostic logs and configuration data for support cases?

Accepted Answer

oc adm must-gather. The command 'oc adm must-gather' collects a comprehensive set of cluster diagnostics, including logs, resource definitions, and configuration data from all relevant components. It is the standard tool for gathering information for Red Hat support cases. It runs a pod on the cluster that collects data and saves it to a local directory.

Answer

oc adm collect-logs

Answer

oc support dump

Answer

oc cluster-debug bundle