A · Professional problem solving and implementation

Quality, security, and safety

Designing for quality validation, reliability, security, privacy, and risk controls.

Classification boundary

Include: Include test strategy, quality gates, threat modeling, security and privacy controls, and reliability engineering.

Choose a neighboring leaf when: Use system design for a security trade-off inside a broader architecture, and engineering systems when credential migration workflow is primary.

This capability may appear in standards across different stages. Explore stage expectations

13 questions

Choose a group based on the evidence you need. Groups follow existing question formats, not difficulty or mandatory prerequisites. Each batch has up to eight questions.

Judgment and options13

Compare goals, constraints, options, and trade-offs.

Questions 1–8

A long-lived credential is shared by several services. Security requires prompt rotation, but all dependents cannot be stopped at once. How would you proceed?
You take over a module that is about to ship and has very low test coverage, and time is short. How do you decide which tests to add first, and how do you explain that order to the team?
A core flow passes mouse testing, but keyboard or screen-reader users cannot complete it. How would you include accessibility in release gates?
A critical user journey across several pages and services regresses often. How would you define the scope and priority of automated tests?
A user requests deletion of personal data, but some records have reached backups, analytics warehouses, and downstream systems. How would you design a verifiable deletion process?
A widely used dependency is disclosed as critically vulnerable, but upgrading may introduce compatibility issues. How would you sequence the response?
Service failures have exceeded the target range, but the business has firm feature commitments. How would you adjust the release pace and investment in reliability?
Backups report success, but the team has never verified restored data integrity or recovery time. How would you establish demonstrable recovery capability?

Questions 9–13

A new external service will access user data and trigger internal actions. How would you perform a lightweight but effective threat model?
A critical end-to-end test fails intermittently: it passes alone but fails in a parallel suite, and the team has started rerunning it until it passes. How would you determine whether it exposes product risk, isolate shared state, resource contention, clock or ordering dependencies, and improve the test workflow?
Several teams copy de-identified data into development, staging, and performance environments with different refresh schedules. How would you design access, lifecycle, and reproducibility?
A core service remains within its monthly SLO, but its error budget is being consumed much faster and errors cluster around a recent feature release. How would you decide whether to pause rollout or roll back?
Users can upload archives for processing, and a past incident showed that malicious files could exhaust resources or access paths without authorization. How would you design isolation, extraction limits, content checks, and safe failure behavior?

Back to the whole domain