Architecture as Code

According to the chapter, what is the tipping point for most organisations adopting Architecture as Code?

1. The licence cost of commercial diagramming and modelling tools
2. The complexity created by large-scale microservice estates
3. A regulatory requirement to keep architecture in version control
4. The retirement of experienced enterprise architects

How does the chapter describe the specifications that Architecture as Code produces?

1. Aspirational design artefacts that guide delivery teams through each quarterly planning cycle
2. Annual reference models approved by an architecture board
3. Generated source code that replaces manual implementation
4. Live, executable specifications synchronised with the running estate

Which three design criteria shape how the book evaluates Architecture as Code practices and tooling?

1. Adoptability, extensibility and productivity
2. Scalability, availability and security
3. Traceability, immutability and testability
4. Simplicity, portability and affordability

An organisation totals 52 points on the readiness scorecard. What does the chapter's scoring guidance say?

1. Ready to proceed: begin with a focused pilot
2. Foundation work needed: follow the Remediation Roadmap first
3. Partial readiness: address critical gaps before scaling
4. The score is invalid and the assessment must be repeated

In the case study of the multinational financial services group, which of these was one of the three gaps the readiness assessment uncovered?

1. Funding remained tied to annual projects
2. CI/CD pipelines were missing altogether
3. No team had been trained in an Infrastructure as Code tool
4. The regulator had rejected the cloud strategy

Which readiness anti-pattern does the chapter describe as buying modelling platforms without addressing the cultural foundations?

1. Budget whiplash from one-off project funding
2. Metrics myopia
3. Heroic ownership
4. Tool-first enthusiasm

By default, administrators are exempt from protected branch rules. What does the chapter say is needed for the review gates to bind them as well?

1. Removing administrators from the CODEOWNERS file
2. Enabling the option that disallows bypassing the settings
3. Requiring a second administrator to countersign each merge
4. Moving the architecture definitions to a private repository

How does the chapter characterise the predominant way non-functional requirements are checked as code?

1. Stakeholder review cycles at major releases
2. User acceptance testing that confirms the business intent was met
3. Automated testing with objective, quantitative thresholds
4. Expert inspection of the architecture diagrams

Which of the following is listed in the chapter as a cause of architectural drift?

1. Excessive automated validation in the pipeline
2. Too frequent releases of new immutable versions
3. Overuse of declarative definitions in version control
4. Emergency patches applied without the standard process

In the chapter's comparison, what is the primary artefact of Architecture as Code as opposed to Infrastructure as Code?

1. Codified guardrails, architectural policies and structural models
2. Environment templates, resource modules and orchestration logic for deployment
3. Plan, apply and monitoring reports on the runtime state
4. Container images, build pipelines and deployment manifests

Why does the chapter say Architecture as Code workflows generally benefit from trunk-based development?

1. Because it removes the need for pull-request reviews
2. Because organisations with formal change-control requirements always demand a single branch
3. Because definitions are long-lived and should reflect reality continuously
4. Because long-lived release branches cannot be protected

What is the principal drawback of a mono-repo that the chapter names?

1. Cross-cutting changes cannot be made in one pull request
2. Scale: clone times, CI durations and merge conflicts increase
3. Shared tooling has to be configured separately per team
4. Access control can only be granted to one owning team

What happens to the number of an ADR when the decision it records is replaced?

1. The number is released and reused for the next new decision
2. The successor takes over the number with a version suffix
3. The record is deleted and its number is retired from the log
4. The original keeps its number and a new ADR supersedes it

Where does the chapter, following the Lightweight Architecture Decision Records technique, recommend storing decision records?

1. In the organisation's wiki, where they are easiest to edit
2. In source control, so that they stay in sync with the code
3. In the minutes of the architecture review board
4. In a dedicated document management system for auditors

In the worked example ADR-0003, which negative consequence of choosing Terraform is recorded?

1. Complexity in state file management
2. No support for multiple clouds
3. An imperative syntax that conflicts with policy requirements
4. A small community with few available providers

Which GDPR article does the chapter cite for data protection by design and by default as a requirement on pipeline design?

1. Article 5
2. Article 17
3. Article 25
4. Article 32

According to the chapter's promotion table, what must be present before the traffic switch executes in production?

1. Explicit architect approval plus an uploaded policy-as-code attestation
2. A successful run of the validate-modules unit checks on the feature branch alone
3. A cost estimate that is lower than the previous release
4. A signed statement from the supplier of the cloud platform

How is policy breach density calculated in the chapter?

1. Count of manual overrides found by drift-detection jobs
2. Average time between a failed deployment and a successful rollback
3. Rolling proportion of successful runs in each environment
4. Failing policy checks divided by total runs in each environment

Which C4 level illustrates how the software system in scope fits into its environment of users and neighbouring systems?

1. Component
2. System Context
3. Container
4. Code

Why does the chapter say both the DSL file and the workspace JSON belong in version control?

1. The JSON is an encrypted backup of the DSL
2. The JSON contains the licence needed to run the prebuilt server binaries
3. The DSL is generated from the JSON on every build
4. The DSL holds model and views, the JSON holds the manual layout

In the chapter's recommendation matrix, which tool is recommended for quick diagrams in a README?

1. Mermaid
2. Structurizr
3. PlantUML
4. Lucidchart

What does the example OPA Gatekeeper constraint in the chapter prohibit?

1. Unsigned images
2. Privileged containers
3. Deployments without resource requests
4. Services exposed outside the cluster

In the GitOps model the chapter describes, how is a rollback performed?

1. By restoring the cluster from the latest volume snapshot
2. By editing the live resources directly and recording the change afterwards in Git
3. By reverting the commit, after which the tool reconciles the cluster
4. By disabling the reconciliation controller until the fix is ready

Which tools does the chapter name as exposing cloud resources as custom resource definitions, so that they are provisioned through the same API as workloads?

1. Crossplane and the Operator Framework
2. Helm and Docker Compose
3. Podman and kubeconform
4. Istio and Linkerd

In the saga pattern as the chapter describes it, what happens if one step fails?

1. The whole transaction is retried from the first step
2. A distributed lock holds all services until an operator intervenes
3. The failed step is skipped and reported at the end
4. Compensating transactions reverse the steps already completed

What should a pipeline verify about golden paths, according to the chapter?

1. That each team has written and versioned its own modules for security, observability and networking
2. That each service consumes the authorised modules and deviations go through decision records
3. That golden paths are optional for services with fewer than three consumers
4. That every service uses the same programming language and framework

Which hotspot does the chapter say the executable catalogue should flag?

1. A service with many synchronous consumers or a repeatedly changing schema
2. A service whose repository has more than one maintainer
3. A service that publishes events instead of exposing an API
4. A service that is deployed to production more often than the average for the estate

Which guiding principle does the chapter give for Zero Trust Architecture?

1. Trust the internal network, verify the external one
2. Never trust, always verify
3. Verify once at the perimeter, then trust the session
4. Trust owned devices

In the chapter's STRIDE table, which concern is listed under Repudiation?

1. Secrets stored in code repositories
2. Stolen credentials for a service account
3. Resource exhaustion through misconfiguration
4. Missing version control history and untracked deployments

Why does the chapter say infrastructure state files must be treated as sensitive artefacts?

1. They capture live inventories, secrets and enforced policy decisions
2. They are the only copy of the application source code
3. They are required by auditors in their original, unmodified binary form
4. They cannot be regenerated once a deployment has completed

Which GDPR article does the chapter's Open Policy Agent example translate into automated checks?

1. Article 6
2. Article 15
3. Article 32
4. Article 44

Which of these does the chapter list as a signal that should raise an alert on a state backend?

1. Manual state downloads outside approved pipeline identities
2. A pipeline run that completes faster than the weekly average
3. A state file that grows after new resources are added
4. A key rotation that follows the documented cadence

What does integrating orchestrated incident response with Architecture as Code make possible, according to the chapter?

1. Removing the need for threat intelligence feeds
2. Replacing tamper-evident audit logging with automated summaries of each incident
3. Skipping post-incident evidence collection
4. Isolating or redeploying compromised components from known-good definitions

Under the governance logic the chapter gives as an example, when may a deployment proceed?

1. When the risk steward is on call during the deployment window
2. When all risks have been reviewed in the past twelve months
3. When every high or critical risk is mitigated automatically or has a time-bound exception
4. When the total number of open risks in the catalogue is lower than it was at the previous release

Which four duties should a response playbook fulfil, in the chapter's order?

1. Subscribe, assess, act, document
2. Detect, escalate, restore, close
3. Plan, do, check, adjust
4. Identify, protect, respond, recover

In what structured formats does the chapter say threat intelligence feeds should be ingested?

1. OSCAL and SPDX
2. STIX and TAXII
3. OpenAPI and AsyncAPI
4. CycloneDX and SLSA

Which OSCAL model tailors catalogues to an organisation's specific needs by selecting, modifying or adding control language?

1. Component definitions
2. System Security Plans
3. Assessment results
4. Profiles

What limitation does the chapter assign to Phase 2, scripted automation?

1. Findings were logged manually weeks after release
2. Duplication, drift and brittle scripts that were hard to share
3. Policy languages were too declarative for engineers
4. Audit evidence was produced continuously but never used

What is the first step of the chapter's implementation roadmap?

1. Policy inventory of existing manual controls
2. Operational integration with security operations
3. Evidence harmonisation with OSCAL catalogues
4. Pilot automation in a production pipeline

What target does the chapter set for time to policy adoption, from proposal to production merge?

1. At most 48 hours
2. At most 30 calendar days
3. At most 5 business days
4. At most one quarter

Which mechanism does the chapter assign to the review and approval stage of the governance workflow?

1. Feature branches
2. Pull requests with templates
3. A merge to the protected main branch
4. A quarterly meeting of the governance board

How does the chapter recommend staging the transition to Governance as Code?

1. Move all critical controls first to prove the value quickly
2. Migrate one regulatory framework at a time in order of audit date
3. Wait until every governance professional has completed training
4. Start with low-risk governance components and scale after feedback

Which control does the worked matrix row SEC-ID-001 record?

1. Enforce MFA for human identities
2. Encrypt all storage at rest
3. Restrict workloads to EU regions
4. Rotate customer-managed keys annually

What closes the compliance loop in the chapter's model?

1. The regulator signs off the complete evidence package at the end of every quarter
2. Automated controls delete non-compliant resources
3. Governance reinforcement informs the next regulatory intelligence cycle
4. The policy templates are archived after each audit

How does the chapter characterise its section on quantum computing readiness and green computing?

1. As mandatory controls for all regulated organisations today
2. As forward-looking, exploratory guidance and not current-state requirements
3. As topics outside the scope of Architecture as Code
4. As requirements that apply only to public authorities

Which of these is one of the four key characteristics of Evidence as Code in the chapter?

1. Annual attestation signed by the control owner
2. Screenshots taken by compliance staff
3. Deterministic capture from automated checks
4. Evidence stored separately from the controls it verifies

What does a SLSA provenance attestation record?

1. The retention period, storage location and expiry date of each evidence file in the catalogue
2. The list of auditors who have accessed the evidence store
3. The licence terms of every dependency in the artefact
4. Build platform, external parameters, resolved dependencies and output digests

In the evidence lifecycle table, what happens at the indexing stage?

1. The artefact is signed with a key held in a hardware module
2. The manifest is registered in an evidence catalogue for audit queries
3. The pipeline step produces the artefact from an automated check
4. Artefacts past their retention period are archived or deleted

According to the chapter, at what point does Open Policy Agent evaluate policies, in contrast to AWS Config Rules?

1. Only during the annual compliance audit
2. Preventively in the pipeline, before deployment
3. Detectively, after resources have been deployed
4. Only when a resource is deleted from the estate

What should unit tests for codified infrastructure validate, according to the chapter?

1. Auto-scaling behaviour under realistic production load
2. Failover between regions during a simulated outage
3. End-to-end deployment from a source change through the pipeline to a running system
4. Resource configurations, variable validations, outputs and interface contracts

Which order of investment does the chapter's summary suggest, based on the testing strategy quadrant?

1. Start with security scanning and policy testing, then add end-to-end tests where risk justifies it
2. Start with end-to-end tests of whole environments, then add unit tests once the pipeline has become stable
3. Start with performance testing, then add compliance tests before each audit
4. Start with chaos experiments in production, then add static analysis

Which activities belong to the Pilot stage of the adoption journey in the chapter's table?

1. Define the adoption vision; assess platform readiness
2. Automate guardrails; onboard product teams
3. Establish the landing zone; deliver the first reusable module
4. Measure outcomes; run the continuous improvement loop

Under which area of the resilience checklist does the chapter ask whether a tested rollback script or inverse plan exists?

1. Rollback readiness
2. State resilience
3. Pre-change validation
4. Recovery drills

What mitigation does the chapter give for the version compatibility challenge, where provider and module upgrades break workflows?

1. Remote state backends with mandatory locking, frequent backups and reconciliation
2. Modular designs with explicit dependency declarations
3. A freeze on all upgrades until the next annual review
4. Staged rollouts, compatibility matrices and automated integration tests

How much usage data does the chapter say should be analysed before committing to reserved capacity?

1. At least 7 days
2. At least 30 to 90 days
3. At least 12 months
4. At least one full budget cycle of 3 years

Why does the chapter say rightsizing should be acted upon before making multi-year commitments?

1. Because providers refuse commitments on oversized instances
2. Because rightsizing recommendations expire after one year
3. Because committing to the wrong instance size locks in waste
4. Because commitments cannot be tagged with a cost centre

Which Kubernetes component sets hard limits on CPU, memory and pod count per namespace?

1. ResourceQuotas
2. LimitRanges
3. Horizontal Pod Autoscaler
4. Vertical Pod Autoscaler

Which migration strategy does the chapter's table describe as suited to the majority of enterprise migrations?

1. Lift-and-shift
2. Re-architecting
3. Application retirement
4. Lift-and-improve (hybrid)

Why does the chapter follow an import of existing resources with drift detection?

1. To prove the template describes reality before any further update
2. To delete resources that were not part of the import
3. To calculate the cost saving achieved by the migration
4. To transfer ownership of the resources to the platform team

What does the chapter recommend doing before critical systems are migrated?

1. Re-architecting all strategic applications in one programme
2. Running pilot projects with non-critical systems
3. Retiring every legacy application of limited value
4. Moving the whole estate by lift-and-shift first

How does the chapter's table characterise decision making in product-aligned teams?

1. Handoffs through tickets and change requests
2. Autonomous within guardrails
3. Meetings and shared backlogs
4. Approval by a central architecture board

What dual purpose do pilot projects serve, according to the chapter?

1. They reduce headcount and shorten procurement cycles
2. They replace formal training and remove the need for sponsorship
3. They test business-critical systems first and expose the teams with the weakest skills
4. They prove feasibility and create reference stories for sceptical stakeholders

Which kind of indicator does the chapter's measurement guidance emphasise?

1. Leading indicators that teams can influence directly
2. Lagging indicators confirmed at programme end
3. Activity counts such as the number of training sessions held
4. Infrastructure metrics alone, without cultural measures

Which focus area does the skills matrix assign to the Practitioner level (Level 2)?

1. Basic operations
2. Platform leadership
3. Infrastructure automation
4. Architecture design

What do platform teams own, according to the chapter?

1. The common toolchains, guardrails and reusable modules
2. The backlog and release dates of every product team
3. The budget approval for all cloud spending
4. The performance reviews of application developers

What do the balanced scorecards in the chapter combine?

1. Cloud cost per team with the number of certifications held
2. Lines of infrastructure code with hours of training completed
3. Audit findings with the number of incidents per quarter
4. DORA-based operational indicators with knowledge-sharing contributions

Which of these is one of the three ways Management as Code differs from traditional management documentation?

1. The artefacts are approved once a year by the board
2. The artefacts are written only by engineers
3. The artefacts are executable and integrate with operational systems
4. The artefacts are kept confidential from delivery teams

In the chapter's implementation steps, after how long without activity does automation flag a Discussion for closure or renewal?

1. 14 days
2. 90 days
3. 30 days
4. One year

How does Management as Code keep leadership in the change management loop without reintroducing bottlenecks?

1. Codified criteria approve low-risk changes and route higher-risk items to leaders
2. Every change waits for a weekly leadership review meeting
3. Leaders approve all changes in advance for the coming quarter
4. Changes are approved afterwards by leaders on the basis of continuous delivery dashboards

Which three elements make up the shared DNA of the soft as-code disciplines?

1. Policy engines, static site generators and dashboards
2. Lawyers, architects and documentation specialists
3. Regulations, standards and internal policies
4. Structured representation, version control and automatability

Which role does the chapter assign to Documentation as Code in the interplay?

1. The quality engine
2. The communication layer
3. The central hub
4. The automated quality gate

In Scenario 1, the compliance team updates a data retention rule in code. What happens next in the chapter's account?

1. The rule waits for the next quarterly architecture board
2. The documentation team rewrites the affected manuals by hand over the following weeks, one system at a time
3. The architectural models flag components lacking encryption and a documentation section is generated
4. The change is applied to production without notifying the teams

What does the chapter say about external communication such as progress reports to sponsors or responses to regulatory enquiries?

1. Agents publish it directly to save time
2. Agents draft it and humans approve it before publication
3. It is excluded from the repository altogether
4. It is approved by the Project Manager agent alone, in the sprint packet

What coverage do automated tests aim for on critical components in the agent team's quality measures?

1. At least fifty per cent
2. At least seventy per cent
3. At least one hundred per cent
4. At least eighty-five per cent

When two agents produce conflicting recommendations, what happens in the chapter's model?

1. The Project Manager agent presents both perspectives to the project owner, who resolves it
2. The Architect agent's recommendation always takes precedence, since it curates the system blueprint
3. The recommendation with the higher test coverage is merged
4. Both recommendations are discarded and the case is closed

What does the chapter say about searching infrastructure code for encryption keywords in a compliance pipeline?

1. It is sufficient evidence for a supervisory authority
2. It is the recommended first step before any policy tooling
3. It is not a meaningful GDPR compliance check
4. It is required by the NIS2 Directive

How should policy catalogues treat cloud providers, according to the chapter?

1. Differentiate inherently sovereign providers from those acceptable only with EU-only controls
2. Treat all providers with an EU region as equivalent
3. Exclude every provider headquartered outside the EU, whatever sovereign controls it has in force
4. Leave provider choice to each product team's preference

Which four dimensions of digital transformation does the chapter say must be addressed holistically?

1. Strategy, budget, procurement and operations
2. Technical, organisational, cultural and competence
3. Cloud, data, security and artificial intelligence
4. Discovery, pilot, scale and optimisation

What is the first limitation of diagram tools for Architecture as Code that the chapter lists?

1. They cannot be stored in version control
2. The diagram is the source of truth, with no underlying model to query or validate
3. They cannot be reviewed through pull requests
4. They require a commercial licence for every contributor who edits or reviews a diagram

According to the comparative framework, what is the validation focus of Architecture as Code?

1. Link checking, spelling, grammar and consistency
2. Readability scores and reader satisfaction surveys
3. Page load time and search ranking of the documentation site
4. Compliance verification, policy enforcement and drift detection

Which three of CALM's core components does the chapter use to illustrate the approach?

1. Nodes, relationships and metadata
2. Context, containers and components
3. Actors, use cases and sequences
4. Catalogues, profiles and plans

What does the chapter call the first visible signal of a mature Architecture as Code programme?

1. A dedicated architecture review board
2. A contract with more than one cloud provider
3. An orderly codebase
4. A FinOps dashboard

How often does the chapter say organisations rehearse disaster simulations to validate recovery time and recovery point objectives?

1. At least annually
2. After incidents
3. Once, when the platform is first built
4. Every working day in production

Which maturity indicator does the cluster table give for the governance cluster?

1. Strategic vendor partnerships and reduced lock-in
2. Empowered delivery teams, automated policy enforcement and fiscal control
3. Latency budgets met and performance balanced with sustainability
4. Multidisciplinary teams and career development

Which NIST standard does the chapter name as the primary algorithm for key encapsulation and key establishment?

1. ML-KEM, standardised as FIPS 203
2. ML-DSA, standardised as FIPS 204
3. SLH-DSA, standardised as FIPS 205
4. FN-DSA (Falcon), still being standardised

What does the chapter recommend investing in to prepare for the future?

1. The single most promising emerging technology
2. A complete rebuild of the platform every three years
3. Adaptive capabilities: flexible architectures, modular codebases and automated testing
4. Long-term exclusive contracts with one technology supplier to secure its product roadmap

What does carbon-aware scheduling do, as the chapter describes it?

1. It switches off all non-production workloads at night
2. It buys carbon credits for each deployment automatically
3. It moves every workload to the cheapest available region
4. It shifts compute-intensive workloads to times and regions with cleaner energy mixes

What recovery does the chapter give for policy drift through manual exceptions?

1. Move the exception list from spreadsheets to a shared wiki page
2. Store time-boxed exceptions as code and evaluate them with the same policy engine
3. Forbid all exceptions and escalate every request to the board
4. Reconcile the exception spreadsheets and email threads by hand before each regulatory audit

A small minority of contributors performs the majority of merges. Which leading indicator is this, and what does it suggest?

1. Pipeline failure clustering, suggesting automation fatigue
2. Exception backlog growth, suggesting governance drift
3. Shadow tooling proliferation, suggesting trust gaps
4. Repository contribution imbalance, suggesting gatekeeping or insufficient coaching

According to the severity table, what is the recommended response to a Critical anti-pattern?

1. Escalate to leadership, pause scaling and address it within the sprint
2. Add it to the backlog and address it within the quarter
3. Monitor it and document it in the risk register
4. Prioritise it in the next planning cycle and assign an owner

Which challenge does the chapter describe as remaining genuinely unsolved?

1. The choice between mono-repo and multi-repo topologies
2. The measurement of cloud costs across several providers
3. The governance of AI-generated architecture decisions
4. The rendering of diagrams from textual models

What is the first step of the chapter's step-by-step adoption strategy?

1. Scaling towards container orchestration and platform capabilities
2. Foundational education in principles and version control
3. Security integration into every delivery workflow
4. Tracking emerging trends and sustainability expectations

What does the fifth step of the adoption strategy ask organisations to do before expanding to new domains?

1. Validate readiness with the prerequisites framework and consult the anti-patterns
2. Replace the pilot team with an external centre of excellence that curates reusable modules
3. Complete the migration of every legacy system
4. Obtain a conformity assessment for all automation tooling