RedHat EX432 Actual Free Exam Questions & Community Discussion
Configure Observability (MultiClusterObservability) with object storage credentials
Correct Answer:
See the solution below in Explanation.
Explanation:
* Create the object storage secret (you'll be given endpoint/access keys in an exam):
oc -n open-cluster-management-observability create secret generic thanos-object-storage \
--from-file=thanos.yaml=/path/to/thanos.yaml
* Create or edit MultiClusterObservability CR to enable observability (storage class, retention, etc.).
* Verify observability pods in the observability namespace and check dashboards/metrics. Why this matters: Monitoring health/performance with ACM observability is a common learning objective in ACM training.
Explanation:
* Create the object storage secret (you'll be given endpoint/access keys in an exam):
oc -n open-cluster-management-observability create secret generic thanos-object-storage \
--from-file=thanos.yaml=/path/to/thanos.yaml
* Create or edit MultiClusterObservability CR to enable observability (storage class, retention, etc.).
* Verify observability pods in the observability namespace and check dashboards/metrics. Why this matters: Monitoring health/performance with ACM observability is a common learning objective in ACM training.
Create a "deny" baseline policy: ensure a prohibited Namespace does NOT exist
Correct Answer:
See the solution below in Explanation.
* Create a ConfigurationPolicy using mustnothave complianceType (common policy pattern).
* Bind to placement.
* Confirm noncompliance if the namespace exists; enforce removes it if remediation is enforce.
* Create a ConfigurationPolicy using mustnothave complianceType (common policy pattern).
* Bind to placement.
* Confirm noncompliance if the namespace exists; enforce removes it if remediation is enforce.
Enable and verify ACM "Search" and query for a resource across clusters
Correct Answer:
See the solution below in Explanation.
Explanation:
* Ensure ACM hub components are installed and healthy.
* In ACM console, open Search and query for:
* a namespace name
* a specific deployment
* Validate results show cluster origin and resource details.
Why this matters:
Search is a core ACM operational workflow for multi-cluster visibility.
Explanation:
* Ensure ACM hub components are installed and healthy.
* In ACM console, open Search and query for:
* a namespace name
* a specific deployment
* Validate results show cluster origin and resource details.
Why this matters:
Search is a core ACM operational workflow for multi-cluster visibility.
Create a policy to enforce "etcd encryption enabled" and verify compliance status
Correct Answer:
See the solution below in Explanation.
* In ACM console: Governance # Create policy # ETCD Encryption template and set to enforce .
* Target clusters via Placement.
* Confirm policy status: Compliant / NonCompliant per cluster.
* In ACM console: Governance # Create policy # ETCD Encryption template and set to enforce .
* Target clusters via Placement.
* Confirm policy status: Compliant / NonCompliant per cluster.
Set TimeWindow for App (Web Console)
Task information: Add timeWindow to Subscription spec (active window Friday 09:00-17:00)
Task information: Add timeWindow to Subscription spec (active window Friday 09:00-17:00)
Correct Answer:
See the solution below in Explanation.
Explanation:
* 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).
Explanation:
* 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).
0
0
0
10