The correct choice is to enable point-in-time recovery and set the transaction log retention to 7 days. This works because Cloud SQL for PostgreSQL implements PITR through continuous archiving of write-ahead logs (WAL), which capture every transaction at the second level. By setting the transaction log retention to 7 days, you instruct Cloud SQL to keep those archived WAL segments for the full week, allowing recovery to any specific second within that window—exactly meeting the requirement for second-granularity recovery over the past 7 days. On the Google Professional Cloud Database Engineer exam, this scenario tests your understanding that enabling PITR alone is not enough; you must also configure the retention period for the transaction logs, as the default retention may be shorter or misaligned with business requirements. A common trap is confusing backup retention (which only covers full backups) with transaction log retention (which enables point-in-time granularity). Memory tip: think of PITR as a time machine—you need both the engine (WAL archiving) and the fuel (retention setting) to travel back to any second.
PCDE Plan and manage database infrastructure Practice Question
This PCDE practice question tests your understanding of plan and manage database infrastructure. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A financial services company runs a critical application on Cloud SQL for PostgreSQL. They require point-in-time recovery (PITR) with the ability to recover to any second within the past 7 days. However, their current backup configuration only allows recovery to the previous 7 days, but not within seconds. What should they do to enable PITR?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Enable point-in-time recovery and set the transaction log retention to 7 days.
Option A is correct because enabling point-in-time recovery (PITR) on Cloud SQL for PostgreSQL automatically uses write-ahead log (WAL) archiving to allow recovery to any second within a specified retention period. Setting the transaction log retention to 7 days ensures that the archived WAL segments are kept for exactly 7 days, enabling recovery to any point within that window. This directly satisfies the requirement for second-granularity recovery over the past 7 days.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Enable point-in-time recovery and set the transaction log retention to 7 days.
Why this is correct
PITR in Cloud SQL for PostgreSQL uses transaction logs (WAL) retained for the specified period.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use the Cloud SQL query insight feature to replay queries.
Why it's wrong here
Query insight provides query performance analysis, not recovery capabilities.
✗
Enable binary logging and set the binary log retention period to 7 days.
Why it's wrong here
PostgreSQL uses write-ahead logs, not binary logs. Binary logs are for MySQL.
✗
Increase the number of automated backups to 7 per day.
Why it's wrong here
Multiple backups don't provide PITR; PITR requires transaction logs being retained.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse the number of automated backups (full backups) with the retention of transaction logs required for PITR, leading them to select Option D, or they mistakenly apply MySQL binary logging concepts (Option C) to a PostgreSQL environment.
Detailed technical explanation
How to think about this question
Under the hood, Cloud SQL for PostgreSQL implements PITR by continuously archiving WAL segments to Cloud Storage. The `transaction_log_retention` flag controls how long these archived WAL files are kept before deletion; setting it to 7 days ensures that any point in time within that window can be reconstructed by replaying the WAL from the last full backup. A subtle behavior is that the retention period is measured from the time the WAL file is archived, not from the time of the transaction, so recovery to the exact second is possible as long as the WAL segment covering that second is still retained.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Plan and manage database infrastructure — This question tests Plan and manage database infrastructure — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Enable point-in-time recovery and set the transaction log retention to 7 days. — Option A is correct because enabling point-in-time recovery (PITR) on Cloud SQL for PostgreSQL automatically uses write-ahead log (WAL) archiving to allow recovery to any second within a specified retention period. Setting the transaction log retention to 7 days ensures that the archived WAL segments are kept for exactly 7 days, enabling recovery to any point within that window. This directly satisfies the requirement for second-granularity recovery over the past 7 days.
What should I do if I get this PCDE question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.