A Database Specialist is working with a company to launch a new website built on Amazon Aurora with several Aurora Replicas. This new website will replace an on-premises website connected to a…

Question

Options

• AStop the DB cluster and analyze how the website responds
• BUse Aurora fault injection to crash the master DB instance
• CRemove the DB cluster endpoint to simulate a master DB instance failure
• DUse Aurora Backtrack to crash the DB cluster

• A
  4% (2)
• B
  85% (45)
• C
  2% (1)
• D
  9% (5)

Explanation

Explanation

Option B is correct because Aurora Fault Injection Queries allow database specialists to simulate failures directly within a running Aurora cluster - including crashing the master DB instance, simulating replica failures, or causing disk congestion - making it the purpose-built tool for resiliency testing without requiring manual infrastructure changes.

Why the other options are wrong:

• Option A (stopping the DB cluster) shuts down the entire cluster rather than simulating a realistic failure scenario, and it doesn't test Aurora's automatic failover capabilities.
• Option C (removing the DB cluster endpoint) is not a valid resiliency test because Aurora's cluster endpoints are managed by AWS and cannot simply be "removed" to simulate a failure.
• Option D (Aurora Backtrack) is a point-in-time recovery feature that rewinds the database to a previous state - it has nothing to do with simulating crashes or testing resiliency.

Memory Tip: Think of "Fault Injection = Controlled Chaos." Just like chaos engineering in DevOps, Aurora's Fault Injection Queries let you intentionally break things in a controlled way to see how your system responds - if the word "test resiliency" appears in a question, think Fault Injection first.

No community discussion yet for this question.