The answer is to schedule a Cloud Function via Cloud Scheduler to run REFRESH MATERIALIZED VIEW periodically. This is correct because Cloud SQL for PostgreSQL does not support automatic or incremental materialized view refresh; the REFRESH MATERIALIZED VIEW command must be explicitly executed to update the snapshot of aggregated data. Since the underlying transaction table is updated continuously, a scheduled refresh balances data freshness with resource cost—refreshing on every transaction would be prohibitively expensive and is not supported natively. On the Google Professional Cloud Database Engineer exam, this scenario tests your understanding of PostgreSQL limitations in a managed Cloud SQL environment and your ability to architect serverless automation. A common trap is assuming Cloud SQL offers built-in triggers for materialized views, but it does not; instead, you must pair Cloud Scheduler with a Cloud Function to execute the SQL command. Memory tip: think “Scheduler + Function = Refresh Solution” to remember that automation, not auto-refresh, is the key.
PCDE Practice Question: Define data structures and implement SQL for Business Intelligence
This PCDE practice question tests your understanding of define data structures and implement sql for business intelligence. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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 company uses Cloud SQL for PostgreSQL to store transaction data. They need to create a materialized view that aggregates daily sales for a BI dashboard. The underlying transaction table is updated continuously. Which approach ensures the materialized view remains up to date without manual intervention?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Schedule a Cloud Function via Cloud Scheduler to run REFRESH MATERIALIZED VIEW periodically
Option C is correct because Cloud SQL for PostgreSQL does not support automatic materialized view refresh. The only way to keep a materialized view up to date without manual intervention is to schedule a periodic refresh using Cloud Scheduler to invoke a Cloud Function that executes the REFRESH MATERIALIZED VIEW command. This approach balances freshness with resource cost, as refreshing on every transaction would be too expensive.
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.
✗
Use BigQuery federated query to directly query the Cloud SQL table
Why it's wrong here
BigQuery federated query does not create a materialized view; it queries live data, which may not be suitable for pre-aggregated views.
✗
Use a Cloud SQL read replica and create the materialized view on the replica
Why it's wrong here
A read replica still requires manual refresh of the materialized view on the replica.
✓
Schedule a Cloud Function via Cloud Scheduler to run REFRESH MATERIALIZED VIEW periodically
Why this is correct
This provides automated periodic refreshes without manual effort.
Related concept
Read the scenario before looking for a memorised answer.
✗
Add a trigger on the base table to refresh the materialized view on each update
Why it's wrong here
PostgreSQL does not allow triggers to refresh materialized views directly; they must be refreshed explicitly.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that materialized views in PostgreSQL can be automatically refreshed via triggers or that read replicas support materialized view creation, leading candidates to pick options that ignore the fundamental write-lock and replication limitations of Cloud SQL for PostgreSQL.
Detailed technical explanation
How to think about this question
PostgreSQL materialized views are physical snapshots that must be explicitly refreshed using REFRESH MATERIALIZED VIEW, which locks the view during refresh (CONCURRENTLY option reduces locking but requires a unique index). In Cloud SQL, the refresh operation counts against database connections and IOPS, so scheduling it during off-peak hours (e.g., every 15 minutes) is a common pattern. The Cloud Function must use a Cloud SQL Auth Proxy or private IP with proper IAM permissions to execute the SQL command securely.
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 startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.
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.
Define data structures and implement SQL for Business Intelligence — This question tests Define data structures and implement SQL for Business Intelligence — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Schedule a Cloud Function via Cloud Scheduler to run REFRESH MATERIALIZED VIEW periodically — Option C is correct because Cloud SQL for PostgreSQL does not support automatic materialized view refresh. The only way to keep a materialized view up to date without manual intervention is to schedule a periodic refresh using Cloud Scheduler to invoke a Cloud Function that executes the REFRESH MATERIALIZED VIEW command. This approach balances freshness with resource cost, as refreshing on every transaction would be too expensive.
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.