Kostenlos · ohne Anmeldung · ohne Zeitlimit
Fertige Multiple-Choice-Übungsquizze, von Hand geprüft. Löse jedes Gratis-Quiz online — jede Antwort kommt mit Erklärung, und jede Quiz-Seite hat einen vollständigen Lösungsschlüssel zum Wiederholen.
Kostenlos · ohne Anmeldung · ohne Zeitlimit
Fertige Multiple-Choice-Übungsquizze, von Hand geprüft. Löse jedes Gratis-Quiz online — jede Antwort kommt mit Erklärung, und jede Quiz-Seite hat einen vollständigen Lösungsschlüssel zum Wiederholen.
IT
Test your mastery of microservices patterns, including Saga, CQRS, Outbox, API Gateways, and domain decomposition. Beantworte jede Frage und sieh sofort, ob du richtig liegst — jedes Mal mit Erklärung.
Ein kostenloser Multiple-Choice-Übungstest mit 16 Fragen zu IT. Jede Frage hat eine richtige Antwort und eine kurze Erklärung, und der vollständige Lösungsschlüssel unter dem Quiz dient zugleich als Lernzettel. Kein Konto, kein Zeitlimit — löse ihn so oft du willst.
Dies ist ein kostenloses Multiple-Choice-Quiz mit 16 Fragen. Nach jeder Antwort siehst du, ob sie richtig war — immer mit Erklärung. Keine Anmeldung, kein Zeitlimit: Mach es so oft du willst und nutze den Lösungsschlüssel oben zum Wiederholen, vorher oder nachher.
Richtige Antwort: BAtomically updating the database and publishing a corresponding event to a message broker without dual-write failures
The Transactional Outbox pattern writes domain updates and outgoing events into the same local database transaction; a separate poller or CDC tool then reliably publishes events to the broker.
Richtige Antwort: BAn orchestrated saga uses a central coordinator to invoke participants; choreographed sagas rely on services reacting to events autonomously
In an orchestrated saga, a central orchestrator tells services which local transactions to execute, whereas choreography relies on services publishing and subscribing to events without a central coordinator.
Richtige Antwort: BTo semantically undo the effects of a previously committed local transaction when a downstream step fails
Because sagas commit changes locally at each step, failures in later steps require executing compensating transactions that reverse earlier committed operations.
Richtige Antwort: BSeparating operations that mutate state (Commands) from operations that read state (Queries), often using different models
CQRS separates write operations (Commands) from read operations (Queries), allowing developers to scale, optimize, and model read and write data pathways independently.
Richtige Antwort: BIt provides tailored API gateways optimized for the unique requirements of specific client interfaces (e.g., mobile, web, IoT)
The BFF pattern creates dedicated gateway services that aggregate and tailor backend data specifically to the requirements, network profiles, and display needs of distinct frontend platforms.
Richtige Antwort: BA clear boundary within which a specific domain model applies and terms in the ubiquitous language have a singular meaning
A Bounded Context defines the conceptual and linguistic boundary within which a particular domain model is consistent and terms have unambiguous, contextual meanings.
Richtige Antwort: BReading committed transaction log changes from a database engine and streaming them as events to message brokers
CDC tools (such as Debezium) monitor database transaction logs (e.g., Postgres WAL or MySQL binlog) to emit reliable, low-latency change events without impacting application code.
Richtige Antwort: BServices are deployed separately but remain tightly coupled via synchronous dependencies, sharing the downsides of both paradigms
A distributed monolith occurs when tightly coupled components are split into microservices, compounding operational, networking, and latency complexities while hindering independent deployment.
Richtige Antwort: BBulkhead Pattern
Inspired by compartmentalized ship hulls, the Bulkhead pattern isolates resources (such as thread pools or memory) so that an outage in one downstream service does not consume all system resources.
Richtige Antwort: BGradually replacing specific legacy system capabilities with microservices until the legacy system can be safely decommissioned
The Strangler Fig pattern involves intercepting calls to a legacy system and routing them to new microservices piece-by-piece, gradually deprecating the monolith without risky big-bang rewrites.
Richtige Antwort: BIt breaks service autonomy, couples schema changes across teams, and bypasses domain access boundaries
A shared database creates tight schema coupling, bypasses service business logic, risks cross-domain data corruption, and makes independent deployment and scaling impossible.
Richtige Antwort: BQuerying multiple backend microservices on behalf of a single client request and returning a consolidated payload
Request aggregation allows an API gateway to fan out calls to multiple underlying microservices, aggregate the responses, and return a single, unified payload to minimize client round-trips.
Richtige Antwort: BCascading latency, increased failure rates, and tight operational coupling across the chain
Synchronous call chains compound network latency, multiply failure probabilities, and lead to thread starvation across upstream services if a single downstream service slows down.
Richtige Antwort: BIt verifies that API providers do not break the specific schema expectations of their consumers without running full end-to-end environments
Consumer-driven contract testing codifies consumer expectations into contracts, allowing providers to validate their implementations in fast isolation builds without maintaining fragile end-to-end test environments.
Richtige Antwort: BTo translate and isolate domain models between a new microservice and an old legacy system so neither pollutes the other
An Anti-Corruption Layer translates semantics between two distinct domain models (such as a clean new service and a messy legacy monolith), keeping the new design unpolluted.
Richtige Antwort: BIt tracks and visualizes the end-to-end path and timing of a single request across multiple interconnected services
Distributed tracing propagates trace and span IDs across network hops, allowing operators to visualize the lifecycle of a request and quickly pinpoint latency bottlenecks across services.