Free RedHat Red Hat Certified Specialist in OpenShift Advanced Cluster Management EX432 Exam Questions

Confirm the policy exists in the namespace:

oc get policy -n team-dev

Confirm Placement exists and selects clusters:

oc get placement -n team-dev

oc get placementdecision -n team-dev

Confirm PlacementBinding points to correct placement + policy:

oc get placementbinding -n team-dev -o yaml

Fix common mistakes:

wrong namespace

placement name mismatch

missing ClusterSetBinding in the namespace

Why this matters:

Policy framework requires placement + binding; missing/incorrect targeting is the #1 real-world issue.

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.

Bind the ClusterSet into the application namespace using ManagedClusterSetBinding.

Create Placement in that namespace selecting the desired clusters.

Deploy application resources tied to that placement (Subscription or GitOps pattern).

Why this matters:

This is the standard multi-tenant ACM pattern for teams.

Create a group (example) and add users:

oc adm groups new dev-team

oc adm groups add-users dev-team user1 user2

Grant namespace access:

oc adm policy add-role-to-group edit dev-team -n team-dev

Validate with a user token/login (or check rolebindings):

oc get rolebinding -n team-dev | grep dev-team

Why this matters:

ACM access patterns commonly combine namespace RBAC + ClusterSetBinding to scope what teams can manage.

Ensure clusters have labels like openshiftVersion=4.18 and region=us-west etc.

Create placement with matchExpressions (include one label, exclude another):

matchExpressions:

- key: openshiftVersion

operator: In

values: ['4.18']

- key: region

operator: NotIn

values: ['us-west']

Validate PlacementDecision.