Free Practice Questions for RedHat EX432 Exam

In the hub cluster Web Console, go to Infrastructure → Clusters (ACM console navigation).

Click Import cluster .

Provide a name (the UI may request details like distribution/credentials depending on flow).

The wizard will provide a command to run on the managed cluster you want to import.

Copy that import command.

Log into the managed cluster (spoke) using oc and run the copied command.

Back on the hub, wait until the cluster status becomes Ready / Managed .

Why these steps matter:

Import registers the managed cluster, installs the klusterlet/agent components, and enables policy/app placement management.

Create an empty kustomization file:

touch overlays/production/kustomization.yaml

Validate it exists:

ls -l overlays/production

Why this matters:

kustomization.yaml is the entrypoint file Kustomize uses to build overlays.

Create the ManagedClusterSet:

oc create managedclusterset production

Validate:

oc get managedclusterset

oc describe managedclusterset production

Why this matters:

Separating development and production clusters is common for governance/RBAC isolation.

Create Placement in team-dev:

cat < < 'EOF' | oc apply -f -

apiVersion: cluster.open-cluster-management.io/v1beta1

kind: Placement

metadata:

name: dev-clusters

namespace: team-dev

spec:

predicates:

- requiredClusterSelector:

labelSelector:

matchExpressions:

- key: environment

operator: In

values: ["dev"]

EOF

Verify placement decisions:

oc get placement -n team-dev

oc get placementdecision -n team-dev

Why this matters:

Placement is used broadly for policy targeting and multi-cluster app rollout .

Grant view role:

oc adm policy add-cluster-role-to-user open-cluster-management:managedclusterset:view:development user-b

Validate:

oc get clusterrolebinding | grep -i development | grep -i user-b

Why this matters:

Provides read-only access to development ClusterSet resources, improving separation of duties.

Confirm the cluster is present on the hub:

oc get managedcluster

Bind cluster-dev to development:

clusteradm clusterset bind --clusterset development --cluster cluster-dev

Verify membership (common checks):

oc get managedclustersetbindings -A

oc get managedclusterset development -o yaml

oc get managedcluster cluster-dev -o yaml | grep -i clusterset -n

Why this matters:

ClusterSet binding is what allows RBAC/users/apps/policies scoped to that ClusterSet to target the cluster.

Edit the subscription/app definition to include a time window (active or blocked window).

Attempt a change outside the window and observe behavior (no rollout until window).

Confirm rollout during window.

Use a policy-based deployment model that installs RHACS components consistently across clusters (operator + secured cluster).

Bind policy to placement selecting target clusters.

Validate RHACS Sensor/Collector present in expected namespace on managed clusters.

Policy collections exist demonstrating RHACS installation patterns via policy framework.

Write a Policy → ConfigurationPolicy enforcing a ConfigMap (name, namespace, data keys).

Bind to placement.

Verify on a managed cluster:

oc get configmap -n < ns >

oc describe configmap -n < ns > < name >