Quiz

2827 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 areas2827 Architecture Fundamentals91 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-Making101 The Architect's Meta-Skills92 Delivery & Release Engineering103 Platform Engineering & Developer Experience92 Testing & Quality Architecture102 Data Platform Architecture98 Streaming & Real-Time Data93 Data Governance & Semantics91 Frontend & Experience Architecture101 Edge, Mobile & IoT98 Regulatory & Data Protection Architecture99 Assurance, Audit & Model Risk98

Difficulty Any beginner intermediate advanced

98 questions in Edge, Mobile & IoT.

Quiz

A mobile team ships every two weeks, cannot roll back a released build, and regularly finds severe bugs in production. What would you change?

Mobile applications ship through app stores with review delays and users who do not update. How should this change backend and release architecture?

A courier application must work where connectivity is intermittent. What must be designed rather than assumed?

A field application must work fully offline for hours and sync when connectivity returns. How should conflicts, permission changes and schema migrations on the device be handled?

A field service app must work offline. Engineers book parts from a shared inventory. What is the design problem?

Delivery couriers work in areas with intermittent connectivity and must complete jobs regardless. What does offline-first require beyond local caching?

You are designing a field-service application for engineers who work in basements and rural sites with no reliable connectivity. What is the architecture, and what are the decisions that will bite later?

A connected-vehicle fleet needs over-the-air firmware updates. What must the architecture guarantee, and why is this unlike a server deployment?

A firmware update bricked 4% of a deployed fleet. Each recovery requires a site visit. What went wrong and what prevents recurrence?

A staged over-the-air rollout reaches 100% over two weeks. What happens to the 12% of devices that were offline for the whole window and come back three weeks later on the old firmware?

An OTA firmware update has bricked 3% of a 50,000-device fleet. What do you do, and what should have prevented it?

Design over-the-air updates for devices where a failed update means a physical service visit.