EX432 Sample Questions

EX432 Sample Questions & Answers

Free Red Hat Certified Specialist in OpenShift Advanced Cluster Management Exam practice questions with worked answers and explanations. See how the ExamJungle simulator prepares you — then jump into the full test.

Launch the full EX432 simulator →

Showing 6 of 12 free samples.

  1. Question 1Beginner

    Manage and deploy Red Hat Advanced Cluster Management for Kubernetes (RHACM) · Deploy RHACM using Red Hat OpenShift Container Platform Operator Lifecycle Management

    True or False: Configuring installPlanApproval: Automatic in the advanced-cluster-management OLM Subscription automatically transitions the operator across minor release channels (for example, from release-2.12 to release-2.13) without requiring an administrator to update spec.channel.

    Show answer & explanation

    Correct answer: A

    Setting installPlanApproval: Automatic only applies z-stream updates published within the currently subscribed release channel (such as release-2.13). Moving to a newer minor release of Red Hat Advanced Cluster Management requires an administrator to explicitly change the spec.channel value in the Subscription resource.

  2. Question 2Intermediate

    Manage clusters by using Red Hat Advanced Cluster Management for Kubernetes (RHACM) · Create, upgrade, import and remove a cluster

    Security regulations at a defense contractor prohibit storing target cluster administrator tokens or kubeconfig files inside an auto-import-secret on the RHACM 2.13 hub cluster. After creating the ManagedCluster (hubAcceptsClient: true) and KlusterletAddonConfig resources for a new cluster named sec-east-01, which sequence of CLI commands must the engineer execute to complete the manual import?

    Show answer & explanation

    Correct answer: A

    When a ManagedCluster resource and its namespace (sec-east-01) are created on the hub cluster, the import controller generates a Secret named -import in the namespace. To import the cluster manually, the administrator extracts and base64-decodes .data.crds\.yaml (to klusterlet-crd.yaml) and .data.import\.yaml (to import.yaml) from the sec-east-01-import Secret on the hub. Next, the administrator authenticates to the managed cluster and applies klusterlet-crd.yaml first so the Klusterlet CRDs exist before applying import.yaml. Applying import.yaml first fails because the custom resource definitions are not yet registered on the target cluster.

    sequenceDiagram participant Admin as Administrator participant Hub as RHACM Hub Cluster participant Managed as Managed Cluster (sec-east-01) Admin->>Hub: Create ManagedCluster & KlusterletAddonConfig Hub->>Hub: Generate Secret sec-east-01-import in ns sec-east-01 Admin->>Hub: Extract & base64-decode crds.yaml and import.yaml Admin->>Managed: oc apply -f klusterlet-crd.yaml Admin->>Managed: oc apply -f import.yaml Managed->>Hub: Klusterlet agent registers (JOINED & AVAILABLE)
  3. Question 3Intermediate

    Manage clusters by using Red Hat Advanced Cluster Management for Kubernetes (RHACM) · Create, upgrade, import and remove a cluster

    To orchestrate an unattended OpenShift version upgrade on an imported cluster named edge-west-04 using RHACM 2.13 via the CLI, an administrator defines a ClusterCurator custom resource (cluster.open-cluster-management.io/v1beta1). Where must this resource be created and which specification fields trigger the cluster upgrade?

    Show answer & explanation

    Correct answer: B

    ClusterCurator (apiVersion: cluster.open-cluster-management.io/v1beta1) is an RHACM lifecycle curation resource that must be created in the managed cluster's namespace (edge-west-04) on the hub cluster with metadata.name: edge-west-04. Setting spec.desiredCuration: upgrade instructs the curator controller to run the upgrade workflow using the target parameters specified under spec.upgrade, including channel (e.g., stable-4.18), desiredUpdate (the target release version), and monitorTimeout (in minutes).

  4. Question 4Intermediate

    Configure access control for multi-cluster management · Configure objects related to access control in a fleet cluster, such as roles, cluster sets, cluster selectors, and placement rules

    After creating a Placement resource in the retail-apps namespace to select OpenShift clusters from the pos-clusters ManagedClusterSet, a cloud engineer inspects the Placement status and sees NoManagedClusterMatched. The engineer confirms that three healthy OpenShift clusters carry the label cluster.open-cluster-management.io/clusterset: pos-clusters and match the labelSelector in the Placement.

    Based on the architecture shown below, what is required so the Placement in retail-apps can select clusters from pos-clusters?

    graph TB subgraph ClusterScoped["Cluster-Scoped Resources (Hub)"] MCS[ManagedClusterSet: pos-clusters] MC1[ManagedCluster: store-01 vendor=OpenShift] MC2[ManagedCluster: store-02 vendor=OpenShift] MC1 -->|clusterset label| MCS MC2 -->|clusterset label| MCS end subgraph Namespaced["Namespace: retail-apps"] Missing[? Missing Resource ?] PL[Placement: pos-placement matchLabels: vendor=OpenShift] Missing -.-> PL end MCS ==> Missing
    Show answer & explanation

    Correct answer: C

    A ManagedClusterSet (cluster.open-cluster-management.io/v1beta2) is a cluster-scoped resource, whereas a Placement (cluster.open-cluster-management.io/v1beta1) is namespace-scoped. Before a Placement in retail-apps can select any clusters belonging to pos-clusters, a ManagedClusterSetBinding must be created in retail-apps where both metadata.name and spec.clusterSet equal pos-clusters. Creating this binding requires RBAC create permissions on the managedclustersets/bind subresource for resourceNames: ["pos-clusters"].

  5. Question 5AdvancedSelect 2

    Configure access control for multi-cluster management · Configure objects related to access control in a fleet cluster, such as roles, cluster sets, cluster selectors, and placement rules

    Which TWO configurations must be added to a Placement resource (cluster.open-cluster-management.io/v1beta1) so that it selects at most three clusters whose region.open-cluster-management.io cluster claim is eu-central-1, and continues to select those clusters even if network connectivity to them is temporarily lost? (Select TWO)

    Show answer & explanation

    Correct answers: A, D

    In a Placement (cluster.open-cluster-management.io/v1beta1), spec.numberOfClusters: 3 caps the number of selected ManagedCluster decisions at three, while spec.predicates[].requiredClusterSelector.claimSelector.matchExpressions filters clusters based on ClusterClaim properties such as region.open-cluster-management.io. In addition, when a managed cluster loses connectivity with the hub, RHACM automatically applies taints (cluster.open-cluster-management.io/unreachable or cluster.open-cluster-management.io/unavailable). Adding spec.tolerations for those keys with operator: Exists prevents the placement controller from evicting temporarily unreachable clusters from the PlacementDecision.

    In a Placement (cluster.open-cluster-management.io/v1beta1), spec.numberOfClusters: 3 caps the number of selected ManagedCluster decisions at three, while spec.predicates[].requiredClusterSelector.claimSelector.matchExpressions filters clusters based on ClusterClaim properties such as region.open-cluster-management.io. In addition, when a managed cluster loses connectivity with the hub, RHACM automatically applies taints (cluster.open-cluster-management.io/unreachable or cluster.open-cluster-management.io/unavailable). Adding spec.tolerations for those keys with operator: Exists prevents the placement controller from evicting temporarily unreachable clusters from the PlacementDecision.

  6. Question 6Beginner

    Configure access control for multi-cluster management · Understand how to use the multi-cluster management dashboard search engine

    During an incident triage session across thirty managed clusters, an SRE needs to query the RHACM 2.13 console search bar to find all Pod resources in any namespace whose name begins with payment-, whose status is NOT Running, and that have restarted more than once. Which search query syntax returns this exact set of resources?

    Show answer & explanation

    Correct answer: B

    The RHACM search engine supports property:value filters combined with comparison and wildcard operators. Using * performs a partial string match (namespace:payment-*), ! or != excludes a specific string value (status:!Running), and > filters numeric fields strictly greater than the specified number (restarts:>1). SQL-like keywords (NOT, LIKE, WHERE) and regex operators (=~) are not valid RHACM Search syntax.

Ready for the real thing?

The full EX432 simulator has every exam-style question, timed mode, and instant scoring.

Go to the EX432 simulator →