Free EX432 Questions for RedHat Red Hat Certified Specialist in OpenShift Advanced Cluster Management EX432 Exam as PDF & Practice Test Engine
Create MultiClusterHub (CLI Alternative)
Task information: Apply the MultiClusterHub custom resource if not using Web Console.
Task information: Apply the MultiClusterHub custom resource if not using Web Console.
Correct Answer:
See the solution below in Explanation.
Explanation:
* 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.
Explanation:
* 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.
Deploy GitOps Application (Subscription YAML)
Correct Answer:
See the solution below in Explanation.
Explanation:
* Apply the subscription/application manifest:
* oc apply -f application-subscription.yaml
* Confirm resources were created:
* oc get applications.app.k8s.io -A
* oc get subscriptions.apps.open-cluster-management.io -A
* oc describe application.app.k8s.io my-app -n < namespace >
* Watch placement/propagation (varies by model used in the lab):
* oc get placement -A
* oc get placementrule -A
Why this matters:
* ACM "application" deployment commonly uses Subscription/Placement (legacy model) or newer Placement resources, enabling multi-cluster rollout from Git sources.
Explanation:
* Apply the subscription/application manifest:
* oc apply -f application-subscription.yaml
* Confirm resources were created:
* oc get applications.app.k8s.io -A
* oc get subscriptions.apps.open-cluster-management.io -A
* oc describe application.app.k8s.io my-app -n < namespace >
* Watch placement/propagation (varies by model used in the lab):
* oc get placement -A
* oc get placementrule -A
Why this matters:
* ACM "application" deployment commonly uses Subscription/Placement (legacy model) or newer Placement resources, enabling multi-cluster rollout from Git sources.
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.
Install RHACS Operator (Web Console)
Correct Answer:
See the solution below in Explanation.
Explanation:
* In OpenShift Web Console, go to Operators # OperatorHub .
* Search for Advanced Cluster Security .
* Select Red Hat Advanced Cluster Security for Kubernetes (RHACS) .
* Click Install and follow the wizard (namespace/channel per lab).
* After operator installation, create RHACS components (as the hint indicates):
* Install/Deploy Central (the management plane)
* Install/Deploy SecuredCluster (sensor/collector on clusters)
* Confirm operator and pods are running:
* Operators # Installed Operators
* oc get pods -n < rhacs-namespace >
Why this matters:
* RHACS adds container security posture management, vulnerability management, and runtime policy enforcement.
Explanation:
* In OpenShift Web Console, go to Operators # OperatorHub .
* Search for Advanced Cluster Security .
* Select Red Hat Advanced Cluster Security for Kubernetes (RHACS) .
* Click Install and follow the wizard (namespace/channel per lab).
* After operator installation, create RHACS components (as the hint indicates):
* Install/Deploy Central (the management plane)
* Install/Deploy SecuredCluster (sensor/collector on clusters)
* Confirm operator and pods are running:
* Operators # Installed Operators
* oc get pods -n < rhacs-namespace >
Why this matters:
* RHACS adds container security posture management, vulnerability management, and runtime policy enforcement.
Create a Placement that selects clusters in a ManagedClusterSet only
Correct Answer:
See the solution below in Explanation.
Explanation:
* Ensure namespace has the correct ManagedClusterSetBinding.
* Create placement in that namespace; only clusters visible via bound ClusterSet can be selected.
* Verify placementdecision includes only clusters from that set.
This ties together ClusterSets (grouping) and Placement (selection).
Explanation:
* Ensure namespace has the correct ManagedClusterSetBinding.
* Create placement in that namespace; only clusters visible via bound ClusterSet can be selected.
* Verify placementdecision includes only clusters from that set.
This ties together ClusterSets (grouping) and Placement (selection).
0
0
0
10