Portfolio ↗

Quiz

2988 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 areas2988 Architecture Fundamentals91 Distributed Systems111 Data Architecture100 Cloud Architecture97 Networking96 API & Integration Architecture97 Reliability & Resilience99 Observability92 Performance & Capacity Engineering100 Security Architecture105 Cost Architecture & FinOps102 Business Architecture103 Architecture Communication102 Enterprise Architecture100 Legacy Modernization102 AI-Era Architecture106 Software Architecture & Engineering93 Architecture Patterns94 Architecture Decision-Making101 The Architect's Meta-Skills102 Delivery & Release Engineering103 Platform Engineering & Developer Experience102 Testing & Quality Architecture102 Data Platform Architecture98 Streaming & Real-Time Data103 Data Governance & Semantics91 Frontend & Experience Architecture101 Edge, Mobile & IoT98 Regulatory & Data Protection Architecture99 Assurance, Audit & Model Risk98
Difficulty Any beginner intermediate advanced

2988 questions.

  1. Physical-World Failure Modes advanced

    A logistics platform's software is correct and the operation still fails regularly. What failure modes does software architecture usually ignore?

    2 min answer physical-worldfailure-modeshuman-factorsdegradation
  2. Physical-World Failure Modes advanced

    A logistics system's software is correct and operations still fail. What class of failure is this, and how should the architecture accommodate it?

    2 min answer porterphysicalexceptionsreconciliation
  3. Physical-World Failure Modes advanced

    A regional power cut takes out 9,000 building-controller devices for six hours. Power returns and 8,700 of them reconnect within ten minutes. The other 300 never come back, and the gateway logs show TLS handshake failures with "certificate is not yet valid". The certificates do not expire for another year. What failed, and which design decision made it possible?

    3 min answer clocktlscold-startfleet
  4. 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
  5. 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
  6. Pipeline Architecture intermediate

    A release is burning 4% of checkout requests. The revert commit is merged at 14:06. At 14:08 your CI provider reports a degraded control plane and no new pipeline runs start. What happens next, and what should have been true?

    3 min answer rollbackrecovery-timeartifact-digestci-dependency
  7. 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
  8. 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
  9. 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
  10. 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
  11. 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
  12. 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