Application Production Support
Six lessons, 24 questions, and eight APS cases: priorities, observability, incidents, batch, changes, recovery, and RUN handover.
Objectives and progression
A professional course with six modules, explained decisions, and fictional banking and operations cases. Develops reasoning about impact, cutoffs, service signals, reconciliation, recovery, and RUN autonomy. Suits a hybrid support and project context, with an internal assessment of 26 decisions in 60 minutes. It does not represent BNP Paribas policies, award external certification, or replace controlled practice.
Audience: APS L2/L3 teams and technical project managers with production responsibility.
Prerequisites: Application, infrastructure, log, and data-flow fundamentals. Cases provide necessary information.
270 estimated study minutes
- Translate a technical alert into business impact with ownership and priority.
- Assess indicators, latency distribution, and collection gaps.
- Coordinate recovery and preserve continuity between teams.
- Protect completeness and consistency when recovering processing.
- Connect release decisions to representative evidence and feasible recovery.
- Turn operational gaps into acceptance, improvements, and project work.
Modules
- The service, impact, and ownership
- Measure what the user receives
- Incidents, communication, and shift change
- Batch, files, and reconciliation
- Changes, canary, and recovery
- RUN autonomy and continuous improvement
Continue learning
References and version
DR APS professional curriculum 2026-09; vendor-neutral operational guidance reviewed 2026-09-30
- Monitoring Distributed Systems · 2026-09-30
- Effective Troubleshooting · 2026-09-30
- Incident Response · 2026-09-30
- Implementing SLOs · 2026-09-30
- Alerting on SLOs · 2026-09-30
- Release Engineering · 2026-09-30
- Data Integrity: What You Read Is What You Wrote · 2026-09-30
- Eliminating Toil · 2026-09-30
- Canarying Releases · 2026-09-30
- Reliable Product Launches at Scale · 2026-09-30
- Service Level Objectives · 2026-09-30
- Making retries safe with idempotent APIs · 2026-09-30
- OPS07-BP03: Use runbooks · 2026-09-30
- OPS07-BP04: Use playbooks · 2026-09-30
- Data Processing Pipelines · 2026-09-30
- Being On-Call · 2026-09-30
- Postmortem Culture: Learning from Failure · 2026-09-30
- COST04-BP02: Implement a decommissioning process · 2026-09-30
- Managing Incidents · 2026-09-30
What you will explore
0 / 6The service, impact, and ownership
Translate a technical alert into business impact with ownership and priority.
Measure what the user receives
Assess indicators, latency distribution, and collection gaps.
Incidents, communication, and shift change
Coordinate recovery and preserve continuity between teams.
Batch, files, and reconciliation
Protect completeness and consistency when recovering processing.
Changes, canary, and recovery
Connect release decisions to representative evidence and feasible recovery.
RUN autonomy and continuous improvement
Turn operational gaps into acceptance, improvements, and project work.