Quiz
2777 questions of the kind that actually get asked — in interviews, in architecture review boards, and by the person who has to run the thing at 3 AM. Every answer states the trade-off rather than the slogan, and says when the obvious choice is the wrong one.
All areas2777
Architecture Fundamentals81
Distributed Systems101
Data Architecture90
Cloud Architecture87
Networking86
API & Integration Architecture87
Reliability & Resilience99
Observability92
Performance & Capacity Engineering90
Security Architecture95
Cost Architecture & FinOps92
Business Architecture93
Architecture Communication91
Enterprise Architecture100
Legacy Modernization92
AI-Era Architecture96
Software Architecture & Engineering93
Architecture Patterns84
Architecture Decision-Making91
The Architect's Meta-Skills92
Delivery & Release Engineering93
Platform Engineering & Developer Experience92
Testing & Quality Architecture102
Data Platform Architecture98
Streaming & Real-Time Data93
Data Governance & Semantics91
Frontend & Experience Architecture91
Edge, Mobile & IoT88
Regulatory & Data Protection Architecture99
Assurance, Audit & Model Risk98
93 questions in Delivery & Release Engineering.
-
Multi-Region Rollout advanced
A configuration or code change must reach many regions or edge locations. What rollout properties matter most?
2 min answer rolloutstagingrollbackhealth-gates -
Multi-Region Rollout advanced
A globally distributed platform must roll out a change across regions. What order and what controls?
2 min answer fly-iorolloutregionshalt -
Multi-Region Rollout advanced
You own the system that rolls changes out to thirty regions. During an incident the commander asks how fast you can get a fix everywhere. Walk me through your answer.
3 min answer fastlymulti-regionrolloutincident-response -
Multi-Region Rollout intermediate Multiple choice
Your deployment updates all four regions in parallel to keep versions consistent. Argue for or against.
2 min answer multi-regiondeploymentblast-radius -
Pipeline Architecture advanced
A deployment platform's build queue is forty minutes deep after a popular framework release. Before adding capacity, what should be examined in the queue itself?
2 min answer vercelrailwaybuildsqueueing -
Pipeline Architecture intermediate
A monorepo's pipeline takes 55 minutes because every commit builds and tests everything. Developers batch changes to avoid it. How do you fix it?
2 min answer cimonorepofeedback -
Pipeline Architecture beginner Multiple choice
A team's pipeline builds the artifact separately for each environment because "the config differs". What is wrong, and what do you propose?
2 min answer cdartifactsconfiguration -
Pipeline Architecture intermediate
A team's pipeline takes 80 minutes from commit to a deployable artifact and engineers have stopped watching it. How do you approach fixing it?
2 min answer cipipelinefeedbackdelivery -
Pipeline Architecture advanced
How should a delivery pipeline be structured for a large monorepo where most changes affect a small part of the system?
2 min answer pipelinemonoreposelectioncaching -
Pipeline Secrets intermediate
A build pipeline needs credentials to deploy. What is the safe design, and what is the most common leak?
2 min answer supabasesecretspipelineworkload-identity -
Pipeline Secrets beginner
A build script echoes a deployment token into the pipeline log. The log is private to the engineering team. Is the token compromised?
2 min answer secretsci-cdrotationblast-radius -
Pipeline Secrets advanced
A team stores no credentials in its repository. The cloud role is assumed through OIDC federation, the registry token lives in a managed secret store, and the build never prints it. Over one weekend an attacker publishes a malicious version of the team's package, and the audit trail shows the push came from the team's own pipeline. Trace how, and name the structural fix.
3 min answer pipeline-secretsfork-triggeroidcsupply-chain