Free RedHat EX432 Practice Exam with Questions & Answers

Ensure you are logged into the hub cluster:

oc whoami

oc project open-cluster-management

Create/apply the MultiClusterHub CR:

oc apply -f multiclusterhub.yaml

Verify it was created:

oc get multiclusterhub -A

oc describe multiclusterhub -n open-cluster-management

Watch pods come up (typical namespaces include open-cluster-management, open-cluster- management-hub, etc. depending on ACM version/config):

oc get pods -n open-cluster-management -w

Why these steps matter:

The MultiClusterHub CR is the “hub installation” object. The operator reconciles it and installs/maintains hub services.

Put the NetworkPolicy manifest under object-templates in a ConfigurationPolicy.

Bind to a Placement for dev clusters.

Verify NetworkPolicy exists on all targeted clusters.

Label clusters for prod:

oc label managedcluster cluster-prod1 environment=prod --overwrite

oc label managedcluster cluster-prod2 environment=prod --overwrite

Create Placement with numberOfClusters: 2:

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

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

kind: Placement

metadata:

name: prod-two-clusters

namespace: team-prod

spec:

numberOfClusters: 2

predicates:

- requiredClusterSelector:

labelSelector:

matchLabels:

environment: prod

EOF

Validate placement decisions:

oc get placementdecision -n team-prod

Web Console → Operators → OperatorHub

Search for multicluster engine (or Multicluster Engine Operator ).

Install the operator into its recommended namespace (commonly multicluster-engine).

Create the MultiClusterEngine custom resource (CLI method shown below):

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

apiVersion: multicluster.openshift.io/v1

kind: MultiClusterEngine

metadata:

name: multiclusterengine

spec: {}

EOF

Verify the engine reconciles:

oc get multiclusterengine

oc get pods -n multicluster-engine

Why this matters:

ACM can use the multicluster engine operator for cluster lifecycle functions; Red Hat documents cluster lifecycle with multicluster engine as a core capability.

Create PolicySet to group related policies.

Use Governance UI to filter by PolicySet and view compliance per cluster.

Export/report (or capture output via CLI oc get policy -o wide) depending on lab capability.

In ACM console go to Applications .

Select the application you deployed.

Open the Editor view (YAML editor) for the Subscription object.

Under spec, add a timeWindow section similar to what the lab requests:

windowtype: active

day: Friday

hours: 09:00-17:00

Save/apply the changes.

Verify the Subscription YAML now contains the time window and observe that deployment actions respect the scheduling window.

Why this matters:

Time windows let you control when changes roll out (useful for change-management, business hours, and maintenance windows).

Create a namespace for the team:

oc new-project team-dev

Create ManagedClusterSetBinding to bind ClusterSet development into team-dev:

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

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

kind: ManagedClusterSetBinding

metadata:

name: development

namespace: team-dev

spec:

clusterSet: development

EOF

Verify:

oc get managedclustersetbinding -n team-dev

Why this matters:

ClusterSet binding is foundational for scoping access and enabling teams to work only with clusters in their set.

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.

Create a Channel (Git) and Subscription referencing it (example pattern).

In exams, you’re usually given a repo URL and target namespace.

Ensure there is a placement rule/placement selecting clusters.

Apply manifests:

oc apply -f channel.yaml

oc apply -f subscription.yaml

Verify resources:

oc get channels.apps.open-cluster-management.io -A

oc get subscriptions.apps.open-cluster-management.io -A

oc get application.app.k8s.io -A

Why this matters:

Multi-cluster application lifecycle is part of ACM operations, and EX480 explicitly covers managing multi-cluster environments with ACM.

Create the ManagedClusterSet:

oc create managedclusterset development

Confirm it exists:

oc get managedclusterset

oc describe managedclusterset development

Why these steps matter:

ClusterSets are an ACM grouping primitive used for RBAC scoping , governance targeting, and multi-cluster app placement.