최신RedHat Red Hat Certified Specialist in OpenShift Advanced Cluster Management - EX432무료샘플문제
문제1
Bind Cluster to ClusterSet
Task information: Add cluster-dev to the development ClusterSet.
Bind Cluster to 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.
문제2
Apply a kustomize overlay for production and deploy resources to production clusters
Apply a kustomize overlay for production and deploy resources to production clusters
정답:
See the solution below in Explanation.
Explanation:
* Create overlays/production/kustomization.yaml referencing base resources.
* Build overlay:
kustomize build overlays/production | oc apply -f -
(If kustomize isn't present, use oc kustomize if available.)
* Verify resources created and placed only on production clusters via placement rules.
Explanation:
* Create overlays/production/kustomization.yaml referencing base resources.
* Build overlay:
kustomize build overlays/production | oc apply -f -
(If kustomize isn't present, use oc kustomize if available.)
* Verify resources created and placed only on production clusters via placement rules.
문제3
Install multicluster engine operator (standalone) and create a MultiClusterEngine
Install multicluster engine operator (standalone) and create a MultiClusterEngine
정답:
See the solution below in Explanation.
Explanation:
* Web Console # Operators # OperatorHub
* Search for multicluster engine (or Multicluster Engine Operator ).
* Install the operator into its recommended namespace (commonly multicluster-engine).
* Create the MultiClusterEngine custom resource (CLI method shown below):
cat < < 'EOF' | oc apply -f -
apiVersion: multicluster.openshift.io/v1
kind: MultiClusterEngine
metadata:
name: multiclusterengine
spec: {}
EOF
* Verify the engine reconciles:
oc get multiclusterengine
oc get pods -n multicluster-engine
Why this matters:
ACM can use the multicluster engine operator for cluster lifecycle functions; Red Hat documents cluster lifecycle with multicluster engine as a core capability.
Explanation:
* Web Console # Operators # OperatorHub
* Search for multicluster engine (or Multicluster Engine Operator ).
* Install the operator into its recommended namespace (commonly multicluster-engine).
* Create the MultiClusterEngine custom resource (CLI method shown below):
cat < < 'EOF' | oc apply -f -
apiVersion: multicluster.openshift.io/v1
kind: MultiClusterEngine
metadata:
name: multiclusterengine
spec: {}
EOF
* Verify the engine reconciles:
oc get multiclusterengine
oc get pods -n multicluster-engine
Why this matters:
ACM can use the multicluster engine operator for cluster lifecycle functions; Red Hat documents cluster lifecycle with multicluster engine as a core capability.
문제4
Create a policy to enforce "etcd encryption enabled" and verify compliance status
Create a policy to enforce "etcd encryption enabled" and verify compliance status
정답:
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.
문제5
Import Cluster (Web Console)
Import Cluster (Web Console)
정답:
See the solution below in Explanation.
Explanation:
* In the hub cluster Web Console, go to Infrastructure # Clusters (ACM console navigation).
* Click Import cluster .
* Provide a name (the UI may request details like distribution/credentials depending on flow).
* The wizard will provide a command to run on the managed cluster you want to import.
* Copy that import command.
* Log into the managed cluster (spoke) using oc and run the copied command.
* Back on the hub, wait until the cluster status becomes Ready / Managed .
Why these steps matter:
* Import registers the managed cluster, installs the klusterlet/agent components, and enables policy/app placement management.
Explanation:
* In the hub cluster Web Console, go to Infrastructure # Clusters (ACM console navigation).
* Click Import cluster .
* Provide a name (the UI may request details like distribution/credentials depending on flow).
* The wizard will provide a command to run on the managed cluster you want to import.
* Copy that import command.
* Log into the managed cluster (spoke) using oc and run the copied command.
* Back on the hub, wait until the cluster status becomes Ready / Managed .
Why these steps matter:
* Import registers the managed cluster, installs the klusterlet/agent components, and enables policy/app placement management.