PagerDuty Foundational Practitioner case studies
PagerDuty Foundational Practitioner · Put your knowledge to work in context.
The PagerDuty Foundational Practitioner credential is a vendor-aligned certification that verifies a candidate's working knowledge of the PagerDuty operations platform. It suits SREs, on-call engineers, incident commanders, platform and DevOps engineers, support and operations-center staff, and technical managers who need to configure and operate PagerDuty day to day rather than simply acknowledge pages. The exam is organized into five equally weighted domains: Incident Management, Signal Intelligence, Automation, the PD Reliability Platform and Paige (PagerDuty's SRE Agent), and Integrations and Developer Platform. Each domain carries 20 percent of the score, so no single area can be skipped. Topics on this exam: Incident Management, Signal Intelligence, Automation, PD Reliability Platform and Paige, PagerDuty's SRE Agent, and Integrations and Developer Platform. The PagerDuty Foundational Practitioner case studies are 5 cases and about 2,998 words.
1Payment Outage Buried by Noisy Alerts
Northstar Payments runs 14 services and 22 engineers on two on-call rotations. Last month the platform produced 1,860 alerts.
626 words, about 3 min2Black Friday Alert Storm and Grouping Risk
Meridian Retail has 40 services and 3,200 alerts per day across six monitoring tools. A six-person NOC triages everything.
604 words, about 3 min3Automating Toil Without Automating a Bad Runbook
Helio SaaS runs 9,000 incidents a year across 60 services. Thirty percent are disk-pressure alerts on Kubernetes nodes, 25% are service-restart requests, and 15% are certificate-expiry warnings.
571 words, about 3 min4Paige Pilot with PII and Skeptical SREs
Corvus Financial has 140 services, 300 engineers, and 6 SREs. Only 20% of services have SLOs.
588 words, about 3 min5Deployment Failure Integration with Duplicate Events
TransFleet Logistics has 20 teams, 400 services, and a custom deployment tool that ships 150 times a day. When a deployment fails, the tool writes a message to Kafka; a cron script reads the topic and sends an email to the on-call address.
609 words, about 3 min