I B M C E R T I F I C A T I O N
C9005500 IBM Certified Associate SRE – Cloud v2 Practice Exam
Exam Number: 4386 | Last updated April 17, 2026 | 342+ questions across 5 vendor-aligned objectives
Reliability engineers building SRE fundamentals on IBM Cloud v2 target the C9005500 credential. This associate-level exam precedes the professional Cloud SRE v2 track and focuses on core concepts — SLO design, error budgets, incident response, and basic platform operations on IBM Cloud. Candidates should be comfortable with Kubernetes basics, observability fundamentals, the infrastructure-as-code tools that SRE teams rely on, and the incident-response practices shared across SRE organizations.
Embracing 26% of the exam, Reliability Fundamentals covers SLI/SLO design, error budgets, toil reduction, and blameless postmortem practice. At 22%, Platform Operations covers Kubernetes basics, IBM Cloud Kubernetes Service, and OpenShift on IBM Cloud. A further 20% targets Observability, covering metrics, logs, traces, and IBM Cloud Monitoring.
Refining the remaining domains, Incident Response accounts for 18% and spans on-call practice, severity definitions, communication patterns, and postmortem workflow. Automation and Tooling represents 14% and spans Terraform, Ansible, and CI/CD basics for SRE. Associate-level questions stay conceptual — pick the answer that reflects SRE best-practice as taught in the canonical literature.
Every answer links to the source. Each explanation below includes a hyperlink to the exact IBM documentation page the question was derived from. PowerKram is the only practice platform with source-verified explanations. Learn about our methodology →
754
practice exam users
94%
satisfied users
91%
passed the exam
4.6/5
quality rating
Test your C9005500 sre cloud v2 associate knowledge
10 of 342+ questions
Question #1 - Reliability Fundamentals
An associate SRE at Linkfold Retail must translate a 99.9% monthly availability SLO into actionable practice.
Which SRE fundamental translates the 99.9% SLO into actionable release practice?
A) Lower the SLO whenever the budget is tight
B) Ignore the SLO after publication
C) Compute the monthly error budget from the SLO (approx. 43 minutes for 99.9% in a 30-day month), alert on burn-rate, and slow releases when the budget is being consumed too fast
D) Fire the engineer who deployed
Show solution
Correct answers: C – Explanation:
SLO → error-budget → burn-rate → release-cadence is the associate SRE fundamental reference. Ignored SLOs, lowered targets, and blame all fail SRE practice. Source: Check Source
Question #2 - Reliability Fundamentals
An associate SRE at Hollingwood Bank notices the team spending most of its time on repetitive manual work.
Which SRE fundamental addresses repetitive manual toil on the team?
A) Ignore toil measurement
B) Accept toil as the nature of the work
C) Hire more people to do the same toil
D) Identify the repetitive work as toil, measure it, and allocate deliberate engineering time to automate it — so the team’s ratio of project work to toil meets the SRE target
Show solution
Correct answers: D – Explanation:
Toil identification automation allocation is the associate SRE fundamental reference. Acceptance, hiring-more-toil, and no-measurement all fail SRE practice. Source: Check Source
Question #3 - Reliability Fundamentals
After a sev-1 at Stonewall Insurance, the team holds a postmortem.
Which SRE fundamental shapes the sev-1 postmortem for learning?
A) Run a blameless postmortem focusing on systemic contributors and producing tracked action items, avoiding punitive framing so future incidents get honest disclosure
B) Blame the engineer at the keyboard
C) Skip the postmortem to save time
D) Hold a closed-door review attended only by executives
Show solution
Correct answers: A – Explanation:
Blameless postmortem with tracked actions is the SRE doctrine. Blame, skipping, and closed-door reviews all fail learning. Source: Check Source
Question #4 - Platform Operations
An associate SRE at Oakgate Retail must deploy a Kubernetes application on IBM Cloud for a small team.
Which IBM Cloud platform-ops choice fits?
A) Use IBM Cloud Kubernetes Service (or Red Hat OpenShift on IBM Cloud) with managed worker nodes, and define the application via Kubernetes manifests or a Helm chart stored in Git
B) Run raw docker containers on a VSI with no orchestration
C) Skip orchestration and run on developer laptops
D) Use an unrelated non-IBM platform contrary to the scenario
Show solution
Correct answers: A – Explanation:
IKS or ROKS with manifests/Helm in Git is the associate SRE platform-ops reference. Raw VSI, laptops, and off-platform choices all fail platform ops. Source: Check Source
Question #5 - Platform Operations
An associate SRE at Wintworth Financial needs the same application deployed across dev, stage, and prod consistently.
Which SRE platform-ops practice fits?
A) Hand-type kubectl apply in each cluster
B) Use GitOps (e.g., Argo CD) with per-environment overlays so the same application definition is deployed consistently across environments with declarative differences
C) Deploy from the senior engineer’s laptop
D) Let each environment drift with no alignment
Show solution
Correct answers: B – Explanation:
GitOps with overlays is the SRE platform-ops consistency reference. Hand-typing, laptop deploys, and drift all fail consistency. Source: Check Source
Question #6 - Observability
An associate SRE at Cresthaven Mutual sees a latency regression but cannot identify which service contributes most.
Which observability fundamental fits?
A) Disabling logs to ‘simplify’
B) Host-level CPU graphs alone
C) Manual service-by-service checks in random order
D) Distributed tracing (e.g., IBM Cloud Monitoring IBM Instana) attributes latency to specific spans across services, which is the observability answer for identifying the contributing hop
Show solution
Correct answers: D – Explanation:
Distributed tracing is the SRE observability reference for cascade latency. Host CPU only, random checks, and disabled logs all miss distributed tracing. Source: Check Source
Question #7 - Observability
An associate SRE at Pinerock Insurance wants to alert on a service’s error rate above a threshold.
Which observability approach fits?
A) Rely on users reporting errors via tickets
B) Emit metrics from the service, scrape via IBM Cloud Monitoring, and configure an alert on the error-rate metric crossing the threshold — with routing to the on-call channel
C) Skip alerting and check dashboards once a week
D) Alert on every single request
Show solution
Correct answers: B – Explanation:
Metrics IBM Cloud Monitoring threshold alerts on-call routing is the associate SRE reference. Ticket-based reporting, weekly checks, and alert-on-everything all fail alerting practice. Source: Check Source
Question #8 - Observability
An associate SRE at Harchester Retail must retain logs long enough to investigate incidents from two weeks ago.
Which observability practice fits?
A) Rely on pod-local log files that rotate after one day
B) Configure log retention in IBM Cloud Log Analysis to match the investigation horizon, and archive older logs to durable storage if longer retention is needed beyond the platform’s default
C) Skip log collection entirely
D) Store logs on a single engineer’s laptop
Show solution
Correct answers: B – Explanation:
Log Analysis with tuned retention optional archive is the SRE observability reference. Pod-local rotation, no-collection, and laptop storage all fail log practice. Source: Check Source
Question #9 - Incident Response
An associate SRE at Murchwood Bank is the first responder to a sev-1 with multiple teams already on the call.
Which incident-response practice fits?
A) Ensure a named Incident Commander is announced explicitly so decisions flow through a single coordinator, with clear roles for scribe, comms, and subject-matter experts
B) Let everyone shout commands simultaneously
C) Wait for a VP to decide who leads
D) Dissolve the call and hope someone reconvenes
Show solution
Correct answers: A – Explanation:
Named Incident Commander clear roles is the SRE associate incident-response reference. Parallel shouting, VP-escalation, and dissolve-and-retry all fail incident command. Source: Check Source
Question #10 - Automation and Tooling
An associate SRE at Lighthollow Financial must automate IBM Cloud infrastructure provisioning.
Which SRE tooling choice fits?
A) Run a one-off shell script from a developer’s laptop
B) Click-ops provisioning in the IBM Cloud console with no record
C) Use Terraform with the IBM Cloud provider, keeping infrastructure definitions in source control and running terraform plan/apply via CI for repeatable provisioning
D) Provision infrastructure verbally over a phone call
Show solution
Correct answers: C – Explanation:
Terraform with IBM Cloud provider Git CI is the associate SRE automation reference. Click-ops, laptop scripts, and verbal provisioning all fail automation practice. Source: Check Source
Get 342+ more questions with source-linked explanations
Every answer traces to the exact IBM documentation page — so you learn from the source, not just memorize answers.
Exam mode & learn mode · Score by objective · Updated April 17, 2026
Learn more...
What the C9005500 sre cloud v2 associate exam measures
- Define and defend SLI/SLO design, error budgets, toil reduction, and blameless postmortems to build a shared language and process for reliability across engineering teams
- Operate and scale Kubernetes basics, IKS, and OpenShift on IBM Cloud to run containerized workloads confidently on IBM Cloud managed platforms
- Observe and correlate metrics, logs, traces, and IBM Cloud Monitoring to answer production questions quickly with the right signal sources
- Respond and learn on-call practice, severity definitions, communication, and postmortem workflow to handle incidents without burning out the on-call rotation
- Automate and deploy Terraform, Ansible, and CI/CD basics to codify operational work so it can be reproduced and reviewed rather than ad-hoc clicked
How to prepare for this exam
- Review the official exam guide to understand every objective and domain weight before you begin studying
- Work through the relevant IBM Training learning path — ibm certified associate sre cloud v2 C9005500 — to cover vendor-authored material end-to-end
- Get hands-on inside IBM TechZone or a comparable sandbox so you can practice the console tasks, CLI commands, and APIs the exam expects
- Tackle a real-world project at your workplace, a volunteer role, or an open-source repository where the technology under test is actually in use
- Drill one exam objective at a time, starting with the highest-weighted domain and only moving on once you can teach it to someone else
- Study by objective in PowerKram learn mode, where every explanation links back to authoritative IBM documentation
- Switch to PowerKram exam mode to rehearse under timed conditions and confirm you consistently score above the pass mark
Career paths and salary outlook
Associate SREs start their reliability careers with a clear path toward principal and staff roles:
- Associate Site Reliability Engineer — $95,000–$135,000 per year, starting an SRE career on IBM Cloud platforms (Glassdoor salary data)
- Junior DevOps Engineer — $85,000–$120,000 per year, supporting platform operations and CI/CD delivery (Indeed salary data)
- Platform Operations Engineer — $100,000–$140,000 per year, running cloud platforms alongside senior SREs (Glassdoor salary data)
Official resources
Work through the official IBM Training learning path for this certification, which bundles videos, labs, and skill tasks aligned to every objective. The official exam page lists the full objective breakdown, prerequisite knowledge, and scheduling details.