Non-Destructive Testing Methods Flashcards
7 cards from real Architecting on AWS Certification practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Non-Destructive Testing Methods flashcards as text
When designing an AWS FIS experiment, which component defines the conditions under which the experiment automatically stops to prevent unintended damage?
Answer: Stop condition using a CloudWatch alarm
FIS stop conditions monitor a CloudWatch alarm and automatically halt the experiment if a safety threshold is breached, keeping the test non-destructive.
A resilience team wants to test how an application responds to an AZ failure without terminating instances. Which FIS action achieves this with minimal blast radius?
Answer: aws:ec2:stop-instances with a resource tag filter scoped to one AZ
Stopping (not terminating) instances scoped by tag to a single AZ simulates AZ loss while keeping instances recoverable and limiting blast radius.
Which AWS tool allows you to test Auto Scaling policies by simulating metric changes without generating actual load on your fleet?
Answer: CloudWatch put-metric-data to publish custom metric values that trigger scaling policies
Publishing custom CloudWatch metric values with put-metric-data lets you drive Auto Scaling policy evaluations without real load, enabling safe policy validation.
A chaos experiment on RDS needs to test multi-AZ failover. What is the non-destructive way to trigger a failover without data loss?
Answer: Reboot the primary DB instance with 'Failover' option checked
Rebooting with failover performs a synchronous multi-AZ switchover with no data loss and the primary automatically becomes available after the test.
Which pattern ensures that a chaos experiment's impact is limited only to resources under test and cannot cascade to unrelated services?
Answer: Scope FIS resource targets using resource tags and set concurrency limits
Resource tags combined with FIS concurrency limits (e.g., percentage-based targeting) ensure the experiment touches only the intended resources.
An architect wants to validate that an application degrades gracefully when DynamoDB throttling occurs, without exceeding read capacity in production. What is the safest approach?
Answer: Use FIS to inject DynamoDB throttle errors on a test table that mirrors production schema
FIS can simulate DynamoDB throttle exceptions on a dedicated test table, letting you observe graceful degradation without touching the production table.
During a GameDay exercise, the team discovers the application does not recover automatically after an FIS network disruption experiment. What is the immediate non-destructive remediation step?
Answer: Stop the FIS experiment to restore connectivity, then implement exponential back-off and retry logic in the application
Stopping the FIS experiment instantly removes the injected fault; then the team can fix retry/back-off logic and re-run the experiment to verify the fix.