Free RedHat EX432 Practice Test & Real Exam Questions
Install RHACS secured cluster services on managed clusters using a governance policy approach
Correct Answer:
See the solution below in Explanation.
Explanation:
* 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.
Explanation:
* 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.
Create System Policy (Web Console) in RHACS
Task information: Criteria: Image OS = debian:10, Enforcement: Build & Deploy
Task information: Criteria: Image OS = debian:10, Enforcement: Build & Deploy
Correct Answer:
See the solution below in Explanation.
Explanation:
* Open the RHACS (Central) console (typically via a route created by Central).
* Navigate to: Platform Configuration # System Policies .
* Click Create Policy .
* Set the policy criteria:
* Add a rule/condition such as Image OS = debian:10 (as required by the lab)
* Set enforcement to apply at Build & Deploy stages.
* Build prevents images from being admitted into pipeline/registries depending on integration.
* Deploy prevents or flags deployments that violate policy.
* Save the policy.
* (Optional validation) Trigger a test deployment/image that matches debian:10 to confirm alerts
/enforcement behavior.
Why this matters:
* Enforcing at build+deploy catches risky images earlier and prevents policy violations from reaching runtime.
Explanation:
* Open the RHACS (Central) console (typically via a route created by Central).
* Navigate to: Platform Configuration # System Policies .
* Click Create Policy .
* Set the policy criteria:
* Add a rule/condition such as Image OS = debian:10 (as required by the lab)
* Set enforcement to apply at Build & Deploy stages.
* Build prevents images from being admitted into pipeline/registries depending on integration.
* Deploy prevents or flags deployments that violate policy.
* Save the policy.
* (Optional validation) Trigger a test deployment/image that matches debian:10 to confirm alerts
/enforcement behavior.
Why this matters:
* Enforcing at build+deploy catches risky images earlier and prevents policy violations from reaching runtime.
Switch a policy from enforce # inform (report-only) and validate behavior
Correct Answer:
See the solution below in Explanation.
Explanation:
* Patch remediation to inform:
oc patch policy policy-ensure-audit-namespace -n team-dev --type=merge -p '{"spec":{"remediationAction":" inform"}}'
* Verify:
oc get policy policy-ensure-audit-namespace -n team-dev -o yaml | grep remediationAction -n
* Observe compliance changes (policy will report but not auto-fix).
Explanation:
* Patch remediation to inform:
oc patch policy policy-ensure-audit-namespace -n team-dev --type=merge -p '{"spec":{"remediationAction":" inform"}}'
* Verify:
oc get policy policy-ensure-audit-namespace -n team-dev -o yaml | grep remediationAction -n
* Observe compliance changes (policy will report but not auto-fix).
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).
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.
