RedHat Red Hat Certified Specialist in OpenShift Advanced Cluster Management - EX432 Exam Practice Test
Install RHACM Operator (Web Console)
Correct Answer:
See the solution below in Explanation.
Explanation:
* Log in to the OpenShift Web Console as a cluster-admin user.
* Go to Operators # OperatorHub .
* OperatorHub is the catalog of available operators.
* In the search box, type: Advanced Cluster Management .
* Click Advanced Cluster Management for Kubernetes (Red Hat ACM).
* Click Install .
* In the install wizard:
* Update channel : choose the recommended/stable channel for your lab.
* Installation mode : typically "All namespaces on the cluster" (default).
* Installed Namespace : select or create open-cluster-management .
* Click Install and wait for the operator to show Succeeded in:
* Operators # Installed Operators .
Why these steps matter:
* Installing the ACM operator creates the CRDs/controllers required to run the Hub components (MultiClusterHub) that manage/import other clusters.
Explanation:
* Log in to the OpenShift Web Console as a cluster-admin user.
* Go to Operators # OperatorHub .
* OperatorHub is the catalog of available operators.
* In the search box, type: Advanced Cluster Management .
* Click Advanced Cluster Management for Kubernetes (Red Hat ACM).
* Click Install .
* In the install wizard:
* Update channel : choose the recommended/stable channel for your lab.
* Installation mode : typically "All namespaces on the cluster" (default).
* Installed Namespace : select or create open-cluster-management .
* Click Install and wait for the operator to show Succeeded in:
* Operators # Installed Operators .
Why these steps matter:
* Installing the ACM operator creates the CRDs/controllers required to run the Hub components (MultiClusterHub) that manage/import other clusters.
Grant a team group "edit" access to the namespace that has a ClusterSetBinding
Correct Answer:
See the solution below in Explanation.
Explanation:
* 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.
Explanation:
* 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.
Create a compliance dashboard view: group policies by PolicySet and export results
Correct Answer:
See the solution below in Explanation.
* 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.
* 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.
Create a Placement that selects clusters by OpenShift version label and exclude a region
Correct Answer:
See the solution below in Explanation.
Explanation:
* 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.
Explanation:
* 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.
Create a PolicySet and include multiple policies for a baseline
Correct Answer:
See the solution below in Explanation.
Explanation:
* Create PolicySet referencing existing policies:
cat < < 'EOF' | oc apply -f -
apiVersion: policy.open-cluster-management.io/v1beta1
kind: PolicySet
metadata:
name: baseline-dev
namespace: team-dev
spec:
policies:
- policy-ensure-audit-namespace
# Add more policies here as you create them
EOF
* Verify:
oc get policyset -n team-dev
Why this matters:
PolicySets group policies to apply/track as a unit-common governance practice.
Explanation:
* Create PolicySet referencing existing policies:
cat < < 'EOF' | oc apply -f -
apiVersion: policy.open-cluster-management.io/v1beta1
kind: PolicySet
metadata:
name: baseline-dev
namespace: team-dev
spec:
policies:
- policy-ensure-audit-namespace
# Add more policies here as you create them
EOF
* Verify:
oc get policyset -n team-dev
Why this matters:
PolicySets group policies to apply/track as a unit-common governance practice.