I B M C E R T I F I C A T I O N
F1003700 IBM Certified Professional Developer v6 PLUS IBM Professional Cloud SRE v2 Practice Exam
Exam Number: 4343 | Last updated April 17, 2026 | 401+ questions across 5 vendor-aligned objectives
Full-stack engineers who write code and then run it in production are the audience for the F1003700 bundle. This credential combines Professional Developer v6 with Professional Cloud SRE v2, producing engineers who own services from git commit through on-call pager. Candidates should be fluent with container-native development, SLO engineering, GitOps, and the incident-response practices that shape production-quality code.
Gripping 26% of the exam, Production-Ready Code covers testing, observability hooks, error handling, graceful degradation, and idempotency built into the application itself. At 22%, Reliability Engineering covers SLI/SLO design, error budgets, error-budget policy, and incident command. A further 20% targets Platform Operations, covering OpenShift, Kubernetes, GitOps, and Helm lifecycle.
Stitching together the outline, Observability and Incident Response accounts for 18% and spans metrics, traces, logs, and structured on-call practice. Security and Access represents 14% and spans IAM, secrets, and posture management. Many scenarios reward answers that demonstrate you would both write and operate the solution — pick the path a reasonable engineer would want to be paged about at 3 AM.
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 →
747
practice exam users
94%
satisfied users
91%
passed the exam
4.7/5
quality rating
Test your F1003700 dev v6 cloud sre v2 knowledge
10 of 401+ questions
Question #1 - Production-Ready Code
A payments microservice at Swanworth Bank must tolerate duplicate client retries without double-charging.
Which production-ready coding practice makes the payment API retry-safe against duplicate client retries?
A) Design the payment API as idempotent, using an idempotency key per request so a duplicate retry returns the original result rather than creating a second charge
B) Rely on clients to not retry and hope for the best
C) Accept duplicate charges as an operational cost
D) Block all retries at the gateway to avoid the issue
Show solution
Correct answers: A – Explanation:
Idempotency keys are the canonical production-ready pattern for retry-safe APIs. Client trust, accepting duplicates, and retry blocking all fail the requirement. Source: Check Source
Question #2 - Production-Ready Code
A service at Larchford Retail occasionally gets flooded by a downstream and degrades the whole platform.
Which production-ready coding pattern fits?
A) Add infinite retries without backoff
B) Let the service crash whenever the downstream is slow
C) Remove all error handling to simplify the code
D) Implement graceful degradation with a circuit breaker and backoff so the service sheds load when the downstream is unhealthy, protecting itself and the rest of the platform
Show solution
Correct answers: D – Explanation:
Circuit breakers, backoff, and graceful degradation are production-ready patterns for downstream protection. Crashing, no-error-handling, and infinite retries all fail resilience. Source: Check Source
Question #3 - Production-Ready Code
A service at Highpoint Logistics must emit a correlation ID through every call for SRE-grade observability.
Which production-ready coding practice propagates correlation IDs across calls for SRE-grade observability?
A) Generate a new correlation ID for every log line so none of them link
B) Skip correlation IDs because they feel like extra work
C) Propagate a trace/correlation ID through incoming and outgoing requests, log it on every message, and include it in distributed traces so the SRE team can follow a request across services
D) Hide the correlation ID from logs to reduce noise
Show solution
Correct answers: C – Explanation:
Correlation-ID propagation through logs and traces is the production-ready observability-hook reference. Skipping, re-generating per line, and hiding all defeat correlation. Source: Check Source
Question #4 - Reliability Engineering
A developer-on-call team at Gorseford Insurance defines a 99.95% SLO on a shopping-cart API.
Which error-budget practice fits?
A) Ignore the SLO after publication
B) Translate the SLO into an explicit monthly error budget, alert on burn rate, and slow the release cadence when the budget is being consumed too quickly
C) Lower the SLO whenever the budget runs out
D) Fire the engineer who last deployed
Show solution
Correct answers: B – Explanation:
Error-budget plus burn-rate alerts plus release slowdown is the reliability reference. Ignored SLOs, lowered targets, and scapegoating all fail reliability engineering. Source: Check Source
Question #5 - Reliability Engineering
A sev-1 at Greenbrae Utilities is running long because two engineers are trying to drive the response independently.
Which incident-command practice fits?
A) Escalate to every VP to make the call
B) Continue without a commander and hope for consensus
C) Explicitly name one Incident Commander and announce it in the channel, so response actions flow through a single coordinator
D) Dissolve the call and reconvene in an hour
Show solution
Correct answers: C – Explanation:
Named Incident Commander with a single coordination point is the SRE doctrine. Consensus, blanket VP escalation, and call dissolution all fail incident command. Source: Check Source
Question #6 - Platform Operations
A deploy pipeline at Wrenfield Bank should deliver the same application definition consistently to dev, stage, and prod clusters.
Which platform-operations pattern fits?
A) Use hand-typed oc apply in each cluster
B) Adopt GitOps with Argo CD and environment-specific overlays, so the same application definition is deployed to each cluster with only the declarative differences that define the environment
C) Maintain one central cluster and export YAML to others manually
D) Deploy from a senior engineer’s laptop
Show solution
Correct answers: B – Explanation:
GitOps with Argo CD and overlays is IBM Cloud’s platform-operations reference. Hand-typed commands, manual exports, and laptop deploys all fail consistency. Source: Check Source
Question #7 - Platform Operations
A Helm chart at Hartsfield Insurance has grown unmaintainable with environment-specific conditionals scattered across values keys.
Which platform-operations practice fits?
A) Delete Helm and deploy manifests manually
B) Add more conditionals whenever a new environment appears
C) Fork the chart per environment and maintain each fork separately
D) Refactor into a clean base chart with per-environment values files (or Kustomize overlays), removing conditional sprawl and restoring readability
Show solution
Correct answers: D – Explanation:
Base chart plus overlays is the platform-operations hygiene reference. Conditional sprawl, forks, and manual deploys all fail Helm hygiene. Source: Check Source
Question #8 - Observability and Incident Response
A cascading incident at Westcrest Health crosses five services and the team cannot pinpoint the origin.
Which observability capability fits?
A) Use distributed tracing in IBM Instana to identify the first failing span and follow the cascade across services, rather than inspecting per-service dashboards in isolation
B) Look at host CPU only and guess
C) Restart every service and hope the pattern reveals itself
D) Scale the platform down to see which service misbehaves alone
Show solution
Correct answers: A – Explanation:
Distributed tracing is IBM’s reference for cascade investigation. Host-CPU-only, reboot loops, and scaling experiments all fail observability practice. Source: Check Source
Question #9 - Observability and Incident Response
After resolving a sev-1 at Glenhollow Retail, the team wants to avoid repeating the failure mode.
Which incident-response practice fits?
A) Run a blameless postmortem focused on contributing systemic factors, publish it internally, and track action items to closure in subsequent reviews
B) Assign disciplinary action to the engineer who deployed
C) Skip the postmortem to protect morale
D) Draft a new incident policy without changing the code or practices
Show solution
Correct answers: A – Explanation:
Blameless postmortems with tracked actions is the IBM SRE incident-response reference. Discipline, skipping, and policy-only responses all fail recurrence prevention. Source: Check Source
Question #10 - Security and Access
A service at Trentvale Credit stores database credentials in an environment variable set at deploy time.
Which security-and-access improvement fits?
A) Keep the credentials in environment variables and rotate manually once a year
B) Move credentials to IBM Cloud Secrets Manager, retrieve them at runtime via an IAM trusted profile, and rotate automatically — removing long-lived credentials from the deployment manifest
C) Check the credentials into the Git repository
D) Share a single admin credential across services
Show solution
Correct answers: B – Explanation:
Secrets Manager plus trusted profiles plus rotation is the IBM Cloud security reference. Env vars, Git checkin, and shared admin all fail secret handling. Source: Check Source
Get 401+ 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 F1003700 dev v6 cloud sre v2 exam measures
- Write and test production-ready code with testing, observability hooks, and graceful degradation to ship services that degrade cleanly and tell you when something is wrong
- Define and defend SLI/SLO targets, error budgets, and incident command practice to align engineering pace with business expectations for reliability
- Operate and scale OpenShift, Kubernetes, GitOps, and Helm lifecycle to run multi-tenant platforms that carry diverse workloads at scale
- Trace and respond metrics, traces, logs, and structured on-call practice to cut mean-time-to-recovery while keeping the on-call rotation sustainable
- Harden and delegate IAM, secrets, and posture management to enforce least-privilege access across code, CI, and runtime
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 professional developer v6 plus ibm professional cloud sre v2 F1003700 — 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
Engineers who write production code and run it on call are rare enough to see competitive offers everywhere:
- Senior Software Engineer (SRE-oriented) — $140,000–$190,000 per year, building and operating production services end-to-end (Glassdoor salary data)
- Staff Engineer — $155,000–$210,000 per year, leading technical design while carrying the pager (Indeed salary data)
- Principal SRE — $160,000–$220,000 per year, setting reliability strategy across product lines (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.