Free EX432 sample questions

Correct answer: The RHACM operator has not yet finished installing and registering the `MultiClusterHub` CRD; wait until the operator CSV succeeds and the CRD is established before applying the `MultiClusterHub` manifest, then monitor `oc get mch` until status reaches `Running`.

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

Correct answer: Set `spec.priority` on `internal-certified-mirror` to a value lower than `-100` (or raise `redhat-operators` priority above `0`), and enable the `cluster-backup` component in the `MultiClusterHub` specification because it is disabled (`False`) by default.

When `MultiClusterHub` installs the `multicluster engine for Kubernetes` operator, it automatically selects the `CatalogSource` with the highest `spec.priority` value. Because the default `redhat-operators` `CatalogSource` 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.

Correct answer: False

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.

Correct answer: Extract `.data.crds\.yaml` and `.data.import\.yaml` from the `sec-east-01-import` Secret in namespace `sec-east-01` on the hub, decode both from base64, log in to `sec-east-01`, and apply `klusterlet-crd.yaml` followed by `import.yaml`.

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. sequenceDiagram participant Admin as Administrator participant Hub as RHACM Hub Cluster participant Managed as Managed Cluster (sec-east-01) Admin->>Hub: Create ManagedCluster & KlusterletAddonConfig Hub->>Hub: Generate Secret sec-east-01-import in ns sec-east-01 Admin->>Hub: Extract & base64-decode crds.yaml and import.yaml Admin->>Managed: oc apply -f klusterlet-crd.yaml Admin->>Managed: oc apply -f import.yaml Managed->>Hub: Klusterlet agent registers (JOINED & AVAILABLE)

Correct answer: In the `edge-west-04` cluster namespace on the hub cluster, setting `spec.desiredCuration: upgrade` along with `spec.upgrade.channel`, `spec.upgrade.desiredUpdate`, and `spec.upgrade.monitorTimeout`.

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

Correct answer: Create a `ManagedClusterSetBinding` named `pos-clusters` in the `retail-apps` namespace with `spec.clusterSet: pos-clusters` using an account that has `create` permission on `managedclustersets/bind` for `pos-clusters`.

A `ManagedClusterSet` (`cluster.open-cluster-management.io/v1beta2`) is a cluster-scoped resource, whereas a `Placement` (`cluster.open-cluster-management.io/v1beta1`) is namespace-scoped. Before a `Placement` in `retail-apps` can select any clusters belonging to `pos-clusters`, a `ManagedClusterSetBinding` must be created in `retail-apps` where both `metadata.name` and `spec.clusterSet` equal `pos-clusters`. Creating this binding requires RBAC `create` permissions on the `managedclustersets/bind` subresource for `resourceNames: ["pos-clusters"]`.