EX432 sample questions

Question 1

Because pod restarts on the hub cluster have been wiping out the search index database in a 180-cluster fleet, a cluster administrator needs to configure persistent storage (`20Gi` using the `gp3-csi` storage class) for the RHACM 2.13 search service. How should this configuration be applied, and what PersistentVolumeClaim (PVC) is created as a result?

Accepted Answer

Modify the `Search` custom resource named `search-v2-operator` in the `open-cluster-management` namespace to set `spec.dbStorage.size: 20Gi` and `spec.dbStorage.storageClassName: gp3-csi`, which creates a PVC named `gp3-csi-search`.

Answer

Edit the `MultiClusterHub` resource to set `spec.search.persistence.size: 20Gi` and `spec.search.persistence.storageClass: gp3-csi`, which creates a PVC named `search-postgres-pvc`.

Answer

Create a ConfigMap named `search-collector-config` in `open-cluster-management-agent-addon` with `dbStorageSize: 20Gi` and `storageClassName: gp3-csi`, which creates a PVC named `search-v2-gp3-csi`.

Answer

Annotate the `search-postgres` Deployment directly with `search.open-cluster-management.io/storage-class: gp3-csi`, because the `Search` operator does not manage database storage fields in its CRD.

Question 2

A governance engineer updates a parent `Policy` resource (`policy.open-cluster-management.io/v1`) so that its top-level `spec.remediationAction` is set to `enforce`. Inside `spec.policy-templates`, the policy contains two `ConfigurationPolicy` objects: - Template 1 checks a `ConfigMap` with `remediationAction: InformOnly` and `complianceType: mustonlyhave`. - Template 2 checks a `RoleBinding` with `remediationAction: inform` and `complianceType: musthave`. When the updated parent `Policy` is propagated to a non-compliant managed cluster, how does the configuration policy controller process the two templates?

Accepted Answer

Template 1 remains in inform mode and only reports violations because `InformOnly` prevents parent policy enforcement, whereas Template 2 is overridden by the parent policy and enforced.

Answer

Template 1 is enforced because `mustonlyhave` requires active remediation, whereas Template 2 fails validation because `inform` is case-sensitive.

Answer

Both Template 1 and Template 2 are enforced on the managed cluster because the parent `Policy` `spec.remediationAction` overrides all child template settings.

Answer

Neither Template 1 nor Template 2 is enforced because a parent `Policy` cannot override a child `ConfigurationPolicy` that explicitly declares a `remediationAction` field.

Question 3

In a `ConfigurationPolicy` specification (`policy.open-cluster-management.io/v1`), the `_____` parameter determines whether related Kubernetes objects on the managed cluster are deleted (`DeleteAll` or `DeleteIfCreated`) or retained (`None`) when the policy is deleted.

Accepted Answer

pruneObjectBehavior

Answer

cleanupAction

Answer

cascadeDeletePolicy

Answer

orphanPropagation

Question 4

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?

Accepted Answer

Deploy in a dedicated `open-cluster-management` namespace with an OperatorGroup targeting `open-cluster-management` and a Subscription specifying `name: advanced-cluster-management`, `channel: release-2.13`, and `source: redhat-operators`.

Answer

Deploy in the `local-cluster` namespace with an OperatorGroup targeting `local-cluster` and a Subscription specifying `name: multiclusterhub-operator` and `channel: release-2.13`.

Answer

Deploy in the `openshift-operators` namespace using the global `AllNamespaces` OperatorGroup and a Subscription named `rhacm-operator` tracking channel `stable-2.13`.

Answer

Deploy in the `open-cluster-management-hub` namespace without an OperatorGroup and create a Subscription specifying `name: advanced-cluster-management` from `sourceNamespace: openshift-config`.

Question 5

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?

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

Answer

The `MultiClusterHub` resource is cluster-scoped and cannot be applied while a `namespace` attribute is present in its `metadata` block.

Answer

The `MultiClusterHub` resource requires `apiVersion: cluster.open-cluster-management.io/v1beta2`; update the API version in the manifest and reapply the file immediately.

Answer

The `multicluster-engine` operator must be installed manually from OperatorHub before OLM registers the `MultiClusterHub` custom resource definition.

Question 6

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-operators CatalogSource 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?

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

Answer

Delete the `local-cluster` namespace so `MultiClusterHub` re-evaluates catalog sources alphabetically, and deploy a separate `MultiClusterHub` instance dedicated to the `cluster-backup` component.

Answer

Set `spec.priority` on `internal-certified-mirror` to `100` so that lower numbers take precedence, and enable `app-lifecycle` in the `MultiClusterHub` specification because both `app-lifecycle` and `cluster-backup` are disabled by default.

Answer

Annotate the `MultiClusterHub` resource with `installer.open-cluster-management.io/mce-catalog: redhat-operators`, and create a `KlusterletAddonConfig` in `open-cluster-management` with `clusterBackup.enabled: true`.

EX432 Red Hat Certified Specialist in OpenShift Advanced Cluster Management Exam Practice Questions

Create an account to continue.

Create an account to continue.

Related exams