最新的RedHat Red Hat Certified Specialist in OpenShift Advanced Cluster Management - EX432免費考試真題
Create Kustomization File
正確答案:
See the solution below in Explanation.
Explanation:
* Create an empty kustomization file:
* touch overlays/production/kustomization.yaml
* Validate it exists:
* ls -l overlays/production
Why this matters:
* kustomization.yaml is the entrypoint file Kustomize uses to build overlays.
Explanation:
* Create an empty kustomization file:
* touch overlays/production/kustomization.yaml
* Validate it exists:
* ls -l overlays/production
Why this matters:
* kustomization.yaml is the entrypoint file Kustomize uses to build overlays.
Bind Cluster to ClusterSet
Task information: Add cluster-dev to the development ClusterSet.
Task information: Add cluster-dev to the development ClusterSet.
正確答案:
See the solution below in Explanation.
Explanation:
* Confirm the cluster is present on the hub:
* oc get managedcluster
* Bind cluster-dev to development:
* clusteradm clusterset bind --clusterset development --cluster cluster-dev
* Verify membership (common checks):
* oc get managedclustersetbindings -A
* oc get managedclusterset development -o yaml
* oc get managedcluster cluster-dev -o yaml | grep -i clusterset -n
Why this matters:
* ClusterSet binding is what allows RBAC/users/apps/policies scoped to that ClusterSet to target the cluster.
Explanation:
* Confirm the cluster is present on the hub:
* oc get managedcluster
* Bind cluster-dev to development:
* clusteradm clusterset bind --clusterset development --cluster cluster-dev
* Verify membership (common checks):
* oc get managedclustersetbindings -A
* oc get managedclusterset development -o yaml
* oc get managedcluster cluster-dev -o yaml | grep -i clusterset -n
Why this matters:
* ClusterSet binding is what allows RBAC/users/apps/policies scoped to that ClusterSet to target the cluster.
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.
正確答案:
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.
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
正確答案:
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.
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)
正確答案:
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).