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.

Deploy an application using Subscription + PlacementRule (legacy model)

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.

Switch a policy from enforce # inform (report-only) and validate behavior

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

Create MultiClusterHub (CLI Alternative)
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.

Set TimeWindow for App (Web Console)
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).