Search the practice set
126 questions, 454 terms and 400 topics in 20 areas.
60 results for “Multi-Region Architecture”
Active-Active vs Active-Passive
Whether all regions serve traffic simultaneously, or one serves while another waits to take over — a choice about which failure mode you would rather have.
Availability Zone
One or more physically separate data centres inside a cloud region, with independent power, cooling and network, connected by low-latency links.
Data Residency
A requirement that specific data be stored and sometimes processed only within a defined geography.
Global Traffic Management
The layer that decides which region a given user reaches, using DNS, anycast or an edge network, and that performs regional failover.
Regional Evacuation
The deliberate, rehearsed act of shifting all traffic out of a region — treated as a routine operation rather than an emergency procedure.
Multi-Cloud
Deliberately running across more than one cloud provider — a decision with a much higher cost than the lock-in it is usually adopted to avoid.
Salesforce's Metadata-Driven Multi-Tenancy
Salesforce serves every customer from shared infrastructure with a single physical schema, storing customer-specific data structures as metadata rather than as separate tables.
Cross-Zone Data Transfer
Charges incurred when data moves between availability zones within a region — invisible on architecture diagrams and a recurring surprise on cloud bills.
Architecture Cost Model
A calculation, made during design, of what an architecture will cost to run at expected and at peak volume.
Architecture Decision Log
The ordered, immutable collection of a system's decision records, read as a history rather than as a specification.
Architecture Decision Record
A short, immutable document capturing one architectural decision, its context, the alternatives, and its consequences.
Architecture Principle
A durable, agreed rule that constrains design decisions in advance, stated with its rationale and its implications.
Architecture Review Board
A forum that reviews significant designs against standards, risks and strategy before commitment.
Architecture Style
A named, coarse-grained way of organising a whole system, as distinct from a pattern that solves one recurring problem inside it.
Architecture Trade-off Analysis Method
A structured evaluation that scores an architecture against prioritised quality-attribute scenarios and identifies the points where those attributes conflict.
Cell-Based Architecture
Partitioning a service into complete, independent copies of itself, each serving a subset of customers, so a failure is bounded to one cell.
Clean Architecture
Concentric layers with a strict dependency rule — source code dependencies point only inwards, towards higher-level policy.
Leadership asks for multi-region "for resilience". What do you establish before designing anything?
First: is multi region the right answer to the actual problem? Multi region defends against a region wide failure . Most outages are not that — they are bad dep
The business asks for "multi-region" after a regional outage. Before agreeing, what do you need to establish, and what are you actually signing up for?
What the interviewer is testing Whether you convert a vague requirement into numbers before designing, and whether you know that multi region is primarily a dat
A multi-tenant SaaS product has outgrown one database. You must shard. How do you choose the partition key, and what makes this decision so expensive to get wrong?
What the interviewer is testing Whether you exhaust cheaper options first, and whether you understand that a shard key is close to irreversible. First: do not s
You run active-active across two regions. The link between them fails. What should each region do, and what would you have designed differently?
The immediate answer Neither region can safely keep accepting writes to shared state, because neither can know it is the surviving side. Each sees one of two no
A DR test fails: the secondary region cannot launch enough instances. What happened, and what standing checks prevent it?
What happened Service quotas in the secondary region are far lower than in the primary , because nothing has ever run there at scale. Quotas are per account and
Design the network layout for a three-tier application in one cloud region. What are the decisions you cannot easily change later?
What the interviewer is testing Whether you know which network decisions are cheap and which are effectively permanent. This is a knowledge question with a clea
Multi-Region Architecture
Surviving a region, and the data consistency price of doing so.
Single vs Multi-Region
Driven by RTO, RPO and residency rather than by ambition.
Multi-Agent Systems
Coordination, hand-off and whether more agents actually help.
Multi-Cloud
Best-of-breed, portfolio and portable — three very different costs.
Network & Egress Costs
Cross-zone and cross-region transfer that appears on no diagram.
AI-Era Architecture
General material on architecting systems that include models.
Application Architecture
The application estate as a designed portfolio rather than an accumulation.
Architecture Communication
General material on communicating architecture.
Architecture Cost Modelling
Pricing a design before building it, at expected and at ten times volume.
Architecture Decision Records
One decision, its context, alternatives and consequences, kept immutable.
Architecture Decision-Making
General material on making and recording architectural decisions.
Architecture Diagrams
Choosing an audience and refusing to mix levels of abstraction.
Architecture Documentation
What to write down, at what altitude, and what nobody will ever read.
Architecture Fundamentals
General material on what solution architecture is and what an architect is accountable for.
Architecture Governance
Preventive, automated controls rather than review meetings.
Architecture Patterns
General material on architectural patterns and their trade-offs.
Architecture Principles
Durable agreed rules that rule options out, stated with rationale and implications.
Architecture Review Boards
Thresholds, early engagement and a real route to accept deviation.
Architecture Reviews
Reviewing early enough to influence rather than to veto.
Architecture Roadmaps
Sequencing change across an estate with dependencies and funding.
Architecture Roles
Solution, enterprise, domain and platform architecture, and where each is accountable.
Architecture Styles
System-level organising shapes, and how they differ from problem-level patterns.
Business Architecture
General material on the business side of architecture.
Cell-Based Architecture
Complete isolated copies each serving a subset of customers.
Clean Architecture
Concentric layers with dependencies pointing only inwards.
Cloud Architecture
General material on designing for cloud platforms.
Data Architecture
General material on structuring, storing and governing data.
AI-Era Architecture
AI workloads meeting security, data, networking, reliability and cost.
API & Integration Architecture
Contracts between systems, and the compatibility discipline that keeps them working.
Architecture Communication
Explain the same architecture to a CEO, an engineering manager and an engineer.
Architecture Decision-Making
Where senior engineer becomes architect: evaluate, choose, write it down.
Architecture Fundamentals
What architecture actually is: drivers, constraints, trade-offs and the principles behind them.
Architecture Patterns
Patterns as tools for recurring problems, with forces and consequences.
Business Architecture
Connecting technology decisions to the outcomes that fund them.
Cloud Architecture
Cloud as a set of architectural capabilities, not a catalogue of service names.
Cost Architecture & FinOps
Architecture is also economics; exceptional architects can price their designs.
Data Architecture
Where state lives, how it is modelled, replicated, partitioned and governed.