PROFESSIONAL-DATA-ENGINEER · Question #296
You have a Standard Tier Memorystore for Redis instance deployed in a production environment. You need to simulate a Redis instance failover in the most accurate disaster recovery situation, and…
The correct answer is B. Create a Standard Tier Memorystore for Redis instance in a development environment. Initiate a manual failover by using the force-data-loss data protection. Option B is correct because it satisfies both requirements simultaneously: using a development environment isolates the test from production (protecting production data), while force-data-loss mode is the most accurate DR simulation because it triggers failover regardless of…
Question
Options
- ACreate a Standard Tier Memorystore for Redis instance in the development environment. Initiate a manual failover by using the limited-data-loss data
- BCreate a Standard Tier Memorystore for Redis instance in a development environment. Initiate a manual failover by using the force-data-loss data protection
- CIncrease one replica to Redis instance in production environment. Initiate a manual failover by using the force-data-loss data protection mode.
- DInitiate a manual failover by using the limited-data-loss data protection mode to the Memorystore for Redis instance in the production environment.
How the community answered
(32 responses)- A3% (1)
- B75% (24)
- C9% (3)
- D13% (4)
Explanation
Option B is correct because it satisfies both requirements simultaneously: using a development environment isolates the test from production (protecting production data), while force-data-loss mode is the most accurate DR simulation because it triggers failover regardless of replication lag - mirroring what actually happens in a real disaster where a primary node suddenly becomes unavailable.
Option A fails on accuracy: limited-data-loss only initiates failover if the replica is within a safe replication lag threshold, which is too controlled to simulate a true disaster scenario. Real disasters don't wait for replication to catch up.
Option C fails on safety: running force-data-loss against the production instance directly risks losing production data, violating the core constraint of the question.
Option D fails on both counts: it targets the production environment (risking production data) and uses limited-data-loss mode (not the most accurate DR simulation).
Memory tip: Map the two requirements to the two parts of the answer - "no production impact" → dev environment, "most accurate DR" → force-data-loss (because real disasters are forced, not gentle). When both requirements appear, you need both conditions satisfied, which only B provides.
Topics
Community Discussion
No community discussion yet for this question.