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
Challenge your understanding of Chaos Engineering, hypothesis testing, GameDays, blast radius containment, and tools like Chaos Mesh. 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: BThe discipline of experimenting on a system in order to build confidence in its capability to withstand turbulent conditions in production
Chaos Engineering is the discipline of experimenting on a system to build confidence in its ability to withstand turbulent, unexpected conditions in production environments.
Richtige Antwort: BDefining 'steady state' as a measurable output of a system that indicates normal behavior
Before injecting failure, practitioners must define and measure the 'steady state' (normal business metrics like successful checkouts/min) to detect deviations during the experiment.
Richtige Antwort: BRandomly terminating virtual machine instances in production during business hours to ensure systems survive instance loss
Chaos Monkey randomly terminated production EC2 instances during business hours, proving that stateless architectures and automated recovery could survive server loss without human intervention.
Richtige Antwort: BThe scope and potential negative impact of a chaos experiment on real users and critical business operations
Blast radius refers to the extent of disruption a chaos experiment can cause; best practices mandate starting experiments with a tightly contained blast radius (e.g., 1% of traffic, one canary container).
Richtige Antwort: BAn automated safeguard that instantly halts the failure injection and rolls back the system if steady-state metrics breach safety bounds
A stop mechanism monitors real-time business metrics; if an experiment causes severe collateral damage or exceeds defined thresholds, it instantly halts failure injection to protect users.
Richtige Antwort: BBy utilizing Linux kernel utilities like Traffic Control (tc) and NetEm inside the target Pod's network namespace
Kubernetes chaos tools use eBPF, iptables, or the Linux Traffic Control (tc) NetEm subsystem inside the target pod's network namespace to inject artificial latency, packet loss, or corruption.
Richtige Antwort: BStaging environments rarely capture the authentic scale, traffic spikes, configuration drift, and third-party dependencies of real systems
Only production captures real-world conditions: realistic traffic patterns, third-party integrations, background churn, and actual scale. Staging environments rarely replicate these nuances accurately.
Richtige Antwort: BA failure in one component that triggers a domino effect of sequential outages across dependent components, collapsing the system
Cascading failure occurs when a localized fault (e.g., a slow cache) causes upstream services to exhaust threads or resources, propagating failures through the entire architecture.
Richtige Antwort: BPreventing services from resolving hostnames to IP addresses, verifying fallback logic and connection pooling resilience
DNS chaos breaks domain name resolution, testing whether microservices cache IP mappings safely, use working fallbacks, or crash completely when upstream name resolution falters.
Richtige Antwort: BDocumenting timelines, observed behaviors, metric anomalies, and action items during the drill without executing injections
The Scribe focuses entirely on capturing notes, tracking telemetry observations, recording timeline milestones, and noting follow-up engineering action items as the experiment plays out.
Richtige Antwort: BA tool that simulates the complete outage of an entire AWS Availability Zone or Region to verify cross-region evacuation
Chaos Kong tests large-scale infrastructure resilience by simulating the loss of an entire cloud region, verifying that traffic can be evacuated and served from alternative regions without incident.
Richtige Antwort: BIt uses FUSE or kernel hooks to return read/write I/O errors to applications, testing corrupt sector and disk failure handling
I/O injection uses FUSE file systems or kernel tracing to return synthetic EIO or delay codes on system calls (read/write), validating how databases handle disk stalls and corruption.
Richtige Antwort: BEngineers cannot distinguish normal system behavior from failure-induced degradation, invalidating the experiment
Without comprehensive observability (metrics, logs, traces), it is impossible to verify whether steady state was preserved or understand how failure propagated through the system.
Richtige Antwort: BA precise, testable prediction that the system will maintain its defined steady state despite the injected failure
A chaos hypothesis explicitly predicts how the system should behave: 'Even if we terminate the primary database instance, the checkout service will continue to succeed for >99.9% of requests using replicas.'
Richtige Antwort: BHow the application handles desynchronized system clocks, testing token expirations, cache leases, and distributed lock validity
Clock skew experiments manipulate physical time inside target containers, revealing bugs in time-sensitive operations like JWT validation, cache leases, and consensus timeouts.
Richtige Antwort: ADR testing verifies procedural recovery after catastrophic events; Chaos Engineering continuously tests systemic hypotheses to prevent outages proactively
Disaster recovery testing is typically an infrequent, scheduled validation of backup and restore procedures; Chaos Engineering is an ongoing experimental practice to discover unknown architectural weaknesses proactively.