Question 57 of 1,446
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 Cloud SQL for PostgreSQL and needs to enable point-in-time recovery (PITR) with a retention period of 14 days. Currently, automated backups are configured with a 7-day retention. What should the engineer do to meet this requirement?
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
✓
Note that Cloud SQL for PostgreSQL only supports up to 7 days of PITR retention; consider exporting logs to Cloud Storage for longer recovery.
Cloud SQL PITR is based on write-ahead log (WAL) archiving. The transaction log retention is set via the 'transaction log retention' setting, not the backup retention. PITR for PostgreSQL in Cloud SQL supports up to 7 days of log retention; 14 days is not supported. The engineer must accept the limitation or use a different approach.
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 backup retention period to 14 days; PITR is automatically extended.
Why it's wrong here
Backup retention does not control PITR retention; PITR uses transaction logs with a separate maximum of 7 days.
- ✗
Set the 'transaction log retention' to 14 days in the Cloud SQL instance settings.
Why it's wrong here
Cloud SQL for PostgreSQL supports a maximum transaction log retention of 7 days. 14 days is not allowed.
- ✓
Note that Cloud SQL for PostgreSQL only supports up to 7 days of PITR retention; consider exporting logs to Cloud Storage for longer recovery.
Why this is correct
Correct. The maximum PITR retention is 7 days. For longer retention, export logs to Cloud Storage and use custom scripts for recovery.
- ✗
Enable binary logging and set the binary log retention to 14 days.
Why it's wrong here
Binary logging is for MySQL, not PostgreSQL. PostgreSQL uses WAL archiving.
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 →
Last reviewed: Jul 4, 2026
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.