Online Access Free EX432 Exam Questions

See the solution below in Explanation.
Explanation:
* Create a Channel (Git) and Subscription referencing it (example pattern).
* In exams, you're usually given a repo URL and target namespace.
* Ensure there is a placement rule/placement selecting clusters.
* Apply manifests:
oc apply -f channel.yaml
oc apply -f subscription.yaml
* Verify resources:
oc get channels.apps.open-cluster-management.io -A
oc get subscriptions.apps.open-cluster-management.io -A
oc get application.app.k8s.io -A
Why this matters:
Multi-cluster application lifecycle is part of ACM operations, and EX480 explicitly covers managing multi- cluster environments with ACM.

See the solution below in Explanation.
Explanation:
* Identify the managed cluster:
oc get managedcluster
* If required in your environment, remove dependent placements/policies/apps targeting it (exam often expects you to check "why deletion stuck").
* Delete managed cluster:
oc delete managedcluster cluster-dev
* Watch finalizers and cleanup:
oc get managedcluster cluster-dev -o yaml | grep finalizers -n
Why this matters:
Proper lifecycle operations (import/manage/detach) is core EX432/EX480 scope.

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

See the solution below in Explanation.
Explanation:
* Create Placement in team-dev:
cat < < 'EOF' | oc apply -f -
apiVersion: cluster.open-cluster-management.io/v1beta1
kind: Placement
metadata:
name: dev-clusters
namespace: team-dev
spec:
predicates:
- requiredClusterSelector:
labelSelector:
matchExpressions:
- key: environment
operator: In
values: ["dev"]
EOF
* Verify placement decisions:
oc get placement -n team-dev
oc get placementdecision -n team-dev
Why this matters:
Placement is used broadly for policy targeting and multi-cluster app rollout .

See the solution below in Explanation.
* Put the NetworkPolicy manifest under object-templates in a ConfigurationPolicy.
* Bind to a Placement for dev clusters.
* Verify NetworkPolicy exists on all targeted clusters.