EX432 試験問題を無料オンラインアクセス

See the solution below in Explanation.
Explanation:
* Grant view role:
* oc adm policy add-cluster-role-to-user open-cluster-management:managedclusterset:view:development user-b
* Validate:
* oc get clusterrolebinding | grep -i development | grep -i user-b
Why this matters:
* Provides read-only access to development ClusterSet resources, improving separation of duties.

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).

See the solution below in Explanation.
Explanation:
* Label clusters for prod:
oc label managedcluster cluster-prod1 environment=prod --overwrite
oc label managedcluster cluster-prod2 environment=prod --overwrite
* Create Placement with numberOfClusters: 2:
cat < < 'EOF' | oc apply -f -
apiVersion: cluster.open-cluster-management.io/v1beta1
kind: Placement
metadata:
name: prod-two-clusters
namespace: team-prod
spec:
numberOfClusters: 2
predicates:
- requiredClusterSelector:
labelSelector:
matchLabels:
environment: prod
EOF
* Validate placement decisions:
oc get placementdecision -n team-prod

See the solution below in Explanation.
Explanation:
* Grant the ClusterSet role (admin on production).
* Log in as user-a and attempt:
* list clusters in production vs development
* create policies in a namespace bound to production
* Confirm authorization errors when accessing development resources.
(ClusterSet RBAC is explicitly part of cluster set management and access scope.)

See the solution below in Explanation.
Explanation:
* Use a policy template approach (OperatorGroup + Subscription + desired namespace) in a ConfigurationPolicy.
* Bind it to a Placement targeting dev clusters.
* Verify operator subscription exists on managed clusters and CSV reaches Succeeded.
Why this matters:
Automating consistent operator installation at scale is a realistic governance task; community policy collections exist demonstrating this model.