01. After a release causes a production problem that demands immediate action, a platform team wants a metric that reflects how quickly they get back to a healthy state.
Which DORA metric captures this?(b)
a) Deployment rework rate, the ratio of deployments that are unplanned but occur as a result of a production incident.
b) Failed deployment recovery time, how long it takes to recover from a deployment that failed and required immediate intervention.
c) Change lead time, which reflects how long a committed change takes to reach production.
d) Deployment frequency, which reflects how often changes are deployed to production.
02. In a DevOps workflow, why do small, frequent changes reduce deployment risk?(c)
a) Large, infrequent releases are inherently safer since every change is reviewed together at one time
b) Deploying less often reduces risk by touching the production environment as rarely as possible
c) A smaller change has a smaller blast radius and a failure is easier to locate
d) Frequent deployments remove the need to test, because defects cannot survive a pipeline that runs often
03. A platform team is designing how it will report the platform's value to leadership. One engineer argues for a single headline number; another argues for a mix of quantitative outcome metrics and qualitative feedback such as satisfaction surveys.
What is the strongest reason to prefer the combined, outcome-focused approach?(d)
a) A single number is always more accurate because it removes the subjectivity that survey responses introduce, so leadership should rely on that one figure alone.
b) Qualitative feedback should replace metrics entirely, since surveys are the only honest source of truth and numbers add nothing of value.
c) Combining measures is needed only to satisfy an external audit, not to understand the platform's value.
d) Any single activity number can be gamed and tends to mislead about real value, so combining quantitative outcome metrics with qualitative feedback gives a truer picture of the platform's impact.
04. During a major incident, one person coordinates the overall response and owns decision-making and communication flow, rather than personally performing the technical fix.
Which role is this?
a) The engineer who applies the hands-on technical fix
b) The incident commander, who coordinates the response
c) The scribe who records the incident timeline
d) The comms lead who handles external updates
05. An operator needs a service account to read nodes, a cluster-scoped resource, across the entire cluster. A namespaced Role and RoleBinding did not grant the access.
Which approach grants the required permission?
a) Bind a ClusterRole that permits reading nodes using a ClusterRoleBinding, because nodes are cluster-scoped rather than namespaced
b) Add the node read permission to the default ServiceAccount, since defaults automatically have cluster scope
c) Use a ClusterRole but bind it with a namespaced RoleBinding rather than a ClusterRoleBinding, which still grants cluster-wide read on nodes
d) Create the same namespaced Role and RoleBinding in every namespace, since repeating them everywhere collectively adds up to cluster-wide coverage of nodes
06. Why does declarative configuration lend itself to GitOps and automation?
a) It can only ever be edited by a single administrator working alone at any one time
b) It keeps the running state inside the cluster, hidden from version control, review, and automated reconciliation
c) It expresses the desired end state in an idempotent form that is diffable, versionable, and supports drift detection
d) It records the exact, ordered sequence of manual commands an operator must type, run, and verify to reach the result
07. Alongside metrics, logs, and traces, platform telemetry often includes a signal made of discrete records of state changes, such as a deployment or a Kubernetes object change, used to correlate with the other signals.
Which signal is being described?
a) Logs, timestamped records emitted by application code
b) Events, records of state changes
c) Traces, the path one request takes across services
d) Metrics, aggregatable numeric time series for trends
08. The Platform Engineering Maturity Model organizes maturity along several aspects. Which two of the following are actual aspects defined by that model?
(Select two.)
a) Profitability
b) Adoption
c) Governance
d) Operations
09. An operator needs a service account to read nodes, a cluster-scoped resource, across the entire cluster. A namespaced Role and RoleBinding did not grant the access.
Which approach grants the required permission?
a) Add the node read permission to the default ServiceAccount, since defaults automatically have cluster scope
b) Use a ClusterRole but bind it with a namespaced RoleBinding rather than a ClusterRoleBinding, which still grants cluster-wide read on nodes
c) Create the same namespaced Role and RoleBinding in every namespace, since repeating them everywhere collectively adds up to cluster-wide coverage of nodes
d) Bind a ClusterRole that permits reading nodes using a ClusterRoleBinding, because nodes are cluster-scoped rather than namespaced
10. Which activity is a core responsibility of a platform team that manages its platform as a product?
a) Writing, testing, and shipping the complete business logic of every product team's application on their behalf
b) The cloud provider's sales and account-management staff
c) Application developers building the organization's services
d) Data scientists and other information workers