Manage and deploy Red Hat Advanced Cluster Management for Kubernetes (RHACM) · Deploy RHACM using Red Hat OpenShift Container Platform Operator Lifecycle Management
Before provisioning a new multi-cluster hub via the command line on Red Hat OpenShift Container Platform 4.18, an infrastructure engineer drafts the Operator Lifecycle Management (OLM) manifests for Red Hat Advanced Cluster Management (RHACM) 2.13. Which combination of namespace, OperatorGroup, and Subscription attributes adheres to the supported installation requirements?
Answer and explanation
Correct answer: B
Red Hat Advanced Cluster Management must be installed in its own dedicated namespace, which defaults to open-cluster-management. The OLM OperatorGroup in that namespace must specify open-cluster-management under spec.targetNamespaces, and the Subscription resource (operators.coreos.com/v1alpha1) must use spec.name: advanced-cluster-management, spec.channel: release-2.13, spec.source: redhat-operators, and spec.sourceNamespace: openshift-marketplace. Installing into openshift-operators or local-cluster is unsupported because RHACM requires single-namespace operator scoping, and local-cluster is reserved exclusively for the self-managed hub cluster representation.
Question 2
Intermediate
Manage and deploy Red Hat Advanced Cluster Management for Kubernetes (RHACM) · Deploy RHACM using Red Hat OpenShift Container Platform Operator Lifecycle Management
While automating the deployment of Red Hat Advanced Cluster Management 2.13 on an OpenShift 4.18 hub cluster, a systems administrator concatenates the Namespace, OperatorGroup, Subscription, and MultiClusterHub manifests into a single YAML file and runs oc apply -f rhacm-install.yaml. The command creates the first three resources but fails on the fourth with the error:
error: unable to recognize "rhacm-install.yaml": no matches for kind "MultiClusterHub" in version "operator.open-cluster-management.io/v1"
What is the root cause of this failure and how should the deployment workflow be corrected?
Answer and explanation
Correct answer: C
When a Subscription is created, Operator Lifecycle Management (OLM) must resolve the catalog, generate an InstallPlan, register the CustomResourceDefinitions (CRDs), and start the operator pods. Applying the MultiClusterHub custom resource (operator.open-cluster-management.io/v1) before OLM registers the CRD produces the no matches for kind "MultiClusterHub" error. Administrators must first apply the Namespace, OperatorGroup, and Subscription, verify that the operator installation has succeeded, and then apply the MultiClusterHub CR, waiting up to 10 minutes for oc get mch to report Running.
Question 3
Advanced
Manage and deploy Red Hat Advanced Cluster Management for Kubernetes (RHACM) · Deploy RHACM using Red Hat OpenShift Container Platform Operator Lifecycle Management
A financial services institution operates an OpenShift Container Platform 4.18 hub cluster in a partially restricted network. Earlier in the quarter, the platform team added a custom CatalogSource named internal-certified-mirror in the openshift-marketplace namespace to test internal operator builds. When defining internal-certified-mirror, the team omitted the spec.priority field. The standard redhat-operatorsCatalogSource is also present in openshift-marketplace with its default configuration, and it contains the latest approved Red Hat packages.
Now, the lead cluster architect is deploying Red Hat Advanced Cluster Management (RHACM) 2.13 in the open-cluster-management namespace. In addition to installing the RHACM operator and creating the MultiClusterHub custom resource, the architect requires the hub to support OADP-based cluster and virtual machine backup workflows.
During the deployment of MultiClusterHub, the architect notices that the multicluster engine for Kubernetes operator subscription is attempting to pull from internal-certified-mirror instead of redhat-operators, and the backup controllers are not deployed after MultiClusterHub reaches Running. Which set of actions resolves both issues?
Answer and explanation
Correct answer: A
When MultiClusterHub installs the multicluster engine for Kubernetes operator, it automatically selects the CatalogSource with the highest spec.priority value. Because the default redhat-operatorsCatalogSource has a priority of -100 and a custom CatalogSource without a specified priority defaults to 0, MultiClusterHub prefers internal-certified-mirror (0 > -100). Setting internal-certified-mirror priority below -100 (or increasing redhat-operators priority above 0) ensures redhat-operators is selected. Furthermore, while app-lifecycle is enabled by default in MultiClusterHub, cluster-backup is disabled (False) by default and must be explicitly enabled in the MultiClusterHub resource.
Question 4
Beginner
Manage and deploy Red Hat Advanced Cluster Management for Kubernetes (RHACM) · Deploy RHACM using Red Hat OpenShift Container Platform Operator Lifecycle Management
True or False: Configuring installPlanApproval: Automatic in the advanced-cluster-management OLM Subscription automatically transitions the operator across minor release channels (for example, from release-2.12 to release-2.13) without requiring an administrator to update spec.channel.
Answer and explanation
Correct answer: A
Setting installPlanApproval: Automatic only applies z-stream updates published within the currently subscribed release channel (such as release-2.13). Moving to a newer minor release of Red Hat Advanced Cluster Management requires an administrator to explicitly change the spec.channel value in the Subscription resource.
Question 5
Intermediate
Manage clusters by using Red Hat Advanced Cluster Management for Kubernetes (RHACM) · Create, upgrade, import and remove a cluster
Security regulations at a defense contractor prohibit storing target cluster administrator tokens or kubeconfig files inside an auto-import-secret on the RHACM 2.13 hub cluster. After creating the ManagedCluster (hubAcceptsClient: true) and KlusterletAddonConfig resources for a new cluster named sec-east-01, which sequence of CLI commands must the engineer execute to complete the manual import?
Answer and explanation
Correct answer: A
When a ManagedCluster resource and its namespace (sec-east-01) are created on the hub cluster, the import controller generates a Secret named -import in the namespace. To import the cluster manually, the administrator extracts and base64-decodes .data.crds\.yaml (to klusterlet-crd.yaml) and .data.import\.yaml (to import.yaml) from the sec-east-01-import Secret on the hub. Next, the administrator authenticates to the managed cluster and applies klusterlet-crd.yaml first so the Klusterlet CRDs exist before applying import.yaml. Applying import.yaml first fails because the custom resource definitions are not yet registered on the target cluster.
Manage clusters by using Red Hat Advanced Cluster Management for Kubernetes (RHACM) · Create, upgrade, import and remove a cluster
To orchestrate an unattended OpenShift version upgrade on an imported cluster named edge-west-04 using RHACM 2.13 via the CLI, an administrator defines a ClusterCurator custom resource (cluster.open-cluster-management.io/v1beta1). Where must this resource be created and which specification fields trigger the cluster upgrade?
Answer and explanation
Correct answer: B
ClusterCurator (apiVersion: cluster.open-cluster-management.io/v1beta1) is an RHACM lifecycle curation resource that must be created in the managed cluster's namespace (edge-west-04) on the hub cluster with metadata.name: edge-west-04. Setting spec.desiredCuration: upgrade instructs the curator controller to run the upgrade workflow using the target parameters specified under spec.upgrade, including channel (e.g., stable-4.18), desiredUpdate (the target release version), and monitorTimeout (in minutes).
Register free for 6 more questions
Or unlock all 153 EX432 questions with explanations, timed mode and flashcards.
