Quiz
2908 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 areas2908
Architecture Fundamentals91
Distributed Systems101
Data Architecture90
Cloud Architecture87
Networking86
API & Integration Architecture87
Reliability & Resilience99
Observability92
Performance & Capacity Engineering100
Security Architecture95
Cost Architecture & FinOps102
Business Architecture103
Architecture Communication102
Enterprise Architecture100
Legacy Modernization92
AI-Era Architecture96
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
103 questions in Streaming & Real-Time Data.
-
Backfill & Reprocessing advanced
A bug in a streaming job produced wrong results for three weeks. How should the backfill be designed so it does not cause a second incident?
3 min answer backfillreprocessingreplayversioning -
Backfill & Reprocessing advanced
A bug is found in a stream processor that has been running for a month. How should the correction be handled?
2 min answer confluentreprocessingreplayidempotency -
Backfill & Reprocessing advanced
A logic bug means six months of a derived table are wrong. You must reprocess without disrupting live consumers. How?
2 min answer data-platformbackfillreprocessingcorrectness -
Backfill & Reprocessing beginner Multiple choice
A logic bug means the last 10 days of a derived table are wrong. An engineer proposes resetting the running consumer group's offsets back 10 days and letting the job reprocess. What does that actually do?
2 min answer offsetsconsumer-groupsreplaybackfill -
Backfill & Reprocessing advanced
A transformation bug means months of derived data are wrong. What makes reprocessing feasible, and what breaks it?
2 min answer backfillreprocessingretentionisolation -
Backfill & Reprocessing advanced
Enabling tiered storage let a platform raise log retention from 7 days to 90 days while shrinking broker disks and cutting the cluster bill roughly in half. Four months later the first 30-day reprocessing run takes 14 hours against the 3 hours the team projected from local-disk throughput. What did the saving actually buy and when does the bill arrive?
2 min answer tiered-storageobject-storagereplayretention -
Backfill & Reprocessing advanced
You reprocess six months of events through an updated job to fix a calculation error. Support is flooded with customer complaints. What went wrong?
2 min answer replayside-effectsdesign -
CDC to Stream intermediate
A CDC connector on a 4 TB Postgres table is restarted with a changed configuration during business hours, and the operator does not realise this triggers a new initial snapshot. What happens over the next three hours, upstream and downstream?
3 min answer cdcsnapshotreplication slotbackpressure -
CDC to Stream advanced
A catalogue search index is rebuilt every night by a full extract of a 60-million-row product table. You must move it onto a change-data-capture stream with no search downtime and no window where the index is silently wrong. Sequence it so each step is reversible, and say where the point of no return is.
3 min answer cdcsearch-indexingdivergencereversibility -
CDC to Stream advanced
A platform publishes database changes as a stream for many consumers. What must the published stream provide that the raw change log does not?
2 min answer cdccontractscouplingtransformation -
CDC to Stream advanced
A product search index is fed from a Postgres change-data-capture stream. Price and title edits appear within two seconds. For about 3% of products the indexed description is a placeholder string nobody recognises, and every affected product has a description over roughly 2 KB. Replication lag is zero and the connector reports no errors. Where is the data going?
3 min answer postgresdebeziumtoastreplica-identity -
CDC to Stream advanced
A service rebuilds its cache from a compacted topic after being offline for two weeks. It now holds records that were deleted. Why?
2 min answer compactiontombstonescorrectness