Manage a solution that can span multiple database technologies →mediumMultiple ChoiceObjective-mapped
PCDE Practice Question: Manage a solution that can span multiple database technologies
A company uses Memorystore for Redis and wants to ensure data is preserved in case of a node failure. They cannot afford any data loss. What should they do?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Enable AOF persistence on the Redis instance
To guarantee no data loss during a node failure, Memorystore for Redis should have persistence enabled. Standard Tier instances support both RDB and AOF persistence. AOF persistence, especially with an fsync policy of 'always' or 'everysec', ensures that writes are durably stored, minimizing data loss to at most one second. Periodic exports to Cloud Storage are backups that occur at scheduled intervals, so any data written between the last export and the failure would be lost, violating the zero-data-loss requirement. Increasing maxmemory only controls eviction, not durability. Cross-region replication provides high availability but does not persist data to disk on its own and can lose recently written data due to replication lag.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Increase the maxmemory setting to avoid eviction
Why it's wrong here
Increasing maxmemory affects eviction behavior, not durability. Data can still be lost on node failure.
- ✓
Enable AOF persistence on the Redis instance
Why this is correct
Enabling AOF persistence (or RDB) ensures that writes are written to disk and can survive a node failure. With appropriate fsync settings, data loss is minimal or zero.
- ✗
Use active cross-region replication to a replica instance
Why it's wrong here
Active cross-region replication provides high availability but relies on asynchronous replication, so data written but not yet replicated could be lost on primary failure. It does not replace persistence.
- ✗
Schedule periodic backups to Cloud Storage using export
Why it's wrong here
Scheduled exports to Cloud Storage create periodic backups. Data written between backups is lost on failure, so this approach cannot guarantee zero data loss.
Visual reference
Go deeper
Related to this question
About these practice questions
One of 1,446 original PCDE practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PCDE practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PCDE exam.