M1.7 module quiz
Ten questions. 80% to pass (8 of 10). Open book, unlimited retakes.
Answers are collapsed under each question. Answer first, then check.
Q1
A ROSA cluster runs on AWS. In ZopNight it connects:
A. Through the AWS account that hosts it, exactly like EKS
B. As its own cloud account against an OpenShift Cluster Manager organisation
C. Through the Red Hat marketplace integration listing
D. As a Kubernetes cluster registered under the EKS provider instead
Show answer
Correct: B. Every discovered resource carries provider = openshift, so filtering the resource list by aws deliberately does not return them even though the instances underneath are AWS instances Red Hat manages.
Q2
The workload view on a newly discovered ROSA cluster returns 424. This means:
A. The OCM credential lacks the permission
B. The cluster is currently unreachable
C. Cluster access has not been provisioned yet
D. Discovery has not finished its first pass
Show answer
Correct: C. An OCM credential authenticates to a different service in a different trust domain and cannot read the cluster’s Kubernetes API. On EKS, GKE and AKS the account’s own principal can already reach it, which is why this step has no equivalent there.
Q3
Which connection method writes to the customer’s cluster?
A. Automatic
B. Cluster login
C. Service account
D. All three
Show answer
Correct: A. Automatic creates an htpasswd identity provider, a user and a group membership granting cluster-admins, through OCM. In the other two the customer creates the identity and hands over a credential.
Q4
A ROSA cluster running external authentication can use:
A. All three methods
B. Automatic and cluster login
C. None; external authentication is unsupported
D. Service account only
Show answer
Correct: D. Both other methods go through OpenShift’s OAuth server, which a cluster on external authentication does not have in play. The service-account method never touches OAuth.
Q5
Classic ROSA “machine pools” and hosted-control-plane “node pools” appear in ZopNight as:
A. One type, openshift-machinepool
B. Two separate resource types
C. Children with no type of their own
D. Only classic pools are discovered
Show answer
Correct: A. Normalising them means a filter, report or group works across both topologies without the reader needing to know which one a cluster uses.
Q6
Which five OpenShift-native kinds appear in the workload view?
A. Pods, Nodes, Namespaces, Secrets and ConfigMaps
B. Operators, Subscriptions, CatalogSources and CSV objects
C. Routes, DeploymentConfigs, BuildConfigs, ImageStreams, Projects
D. Templates, Quotas, LimitRanges, SCCs and Egress
Show answer
Correct: C. They are live-only, read from the cluster API rather than persisted as resource rows, and shown beside their Kubernetes counterparts rather than in a vendor section.
Q7
A ROSA cluster whose API server is private is:
A. Excluded from discovery entirely until it becomes reachable again
B. Flagged, with OCM-side discovery, cost and configuration still working
C. Reachable again once network access is granted
D. Hidden from the resource list until it recovers
Show answer
Correct: B. PrivateLink is fixed at install time on modern ROSA, so this is terminal. Flagging rather than hiding tells the team the situation is permanent instead of looking like a discovery gap.
Q8
How many cluster-autoscaler settings are editable on a hosted control plane?
A. Four
B. All of them
C. Only the scale-down group
D. None
Show answer
Correct: A. maxNodesTotal, maxPodGracePeriod, podPriorityThreshold and maxNodeProvisionTime. The rest, including the whole scale-down group, are classic-only in ROSA.
Q9
Adding or deleting a machine pool through ZopNight is:
A. Available to Admins only
B. Refused, because both are provisioning
C. Available on classic clusters only
D. Available with a governed override
Show answer
Correct: B. Creating a pool launches instances that did not exist; deleting one terminates every node in it. The integration changes the shape of things that exist and does not bring them into existence or destroy them.
Q10
Can a ROSA machine pool be attached to a ZopNight schedule?
A. Yes, like an EKS node group
B. Only on classic topology
C. Only with the automatic connection method
D. No, and this will not change
Show answer
Correct: D. Worker nodes are Red Hat-managed, so stopping them falls outside the service boundary. Resizing a pool through OCM is a configuration change rather than scheduling.
What’s next
Back to Red Hat OpenShift (ROSA).