The answer is to enable Cloud SQL slow query logging and analyze App Engine request logs. These two actions work together to isolate the bottleneck: App Engine request logs reveal which endpoints or operations are experiencing high latency, helping you determine if the slowness is in the application code or the network, while Cloud SQL slow query logging directly surfaces long-running SQL statements that cause database contention. On the Google Professional Cloud DevOps Engineer exam, this scenario tests your ability to systematically differentiate between application-layer and database-layer performance issues, a common trap being to jump straight to scaling Cloud SQL without first verifying whether inefficient queries are the root cause. A useful memory tip is “Logs first, queries second” — always check App Engine latency patterns before diving into database tuning, as the slow response could stem from code inefficiency rather than a Cloud SQL bottleneck.
PCDOE Optimizing service performance Practice Question
This PCDOE practice question tests your understanding of optimizing service performance. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 team is troubleshooting a slow response time on an App Engine standard environment application. The application uses Cloud SQL as its database. Which TWO actions should the team take to identify the bottleneck?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Examine App Engine request logs for latency patterns.
Option A is correct because examining App Engine request logs reveals latency patterns, such as which endpoints or operations are slow, helping to pinpoint whether the bottleneck is in the application code, network, or database. Option C is correct because enabling Cloud SQL slow query logging identifies long-running SQL queries that could be causing database contention or inefficient data retrieval, directly addressing a common performance bottleneck in App Engine applications using Cloud SQL.
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.
✓
Examine App Engine request logs for latency patterns.
Why this is correct
Correlates with slow queries.
Related concept
Read the scenario before looking for a memorised answer.
✗
Increase the number of App Engine instances.
Why it's wrong here
This may not address the root cause.
✓
Enable Cloud SQL slow query logging and analyze long-running queries.
Why this is correct
Identifies database-level latency.
Related concept
Read the scenario before looking for a memorised answer.
✗
Enable Cloud CDN to cache responses.
Why it's wrong here
Not suitable for dynamic content.
✗
Disable caching to ensure fresh data.
Why it's wrong here
Disabling caching worsens performance.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that scaling the application tier (more instances) always improves performance, but the trap here is that the bottleneck may be at the database layer, where scaling the app tier without addressing database issues can actually degrade performance due to increased connection contention.
Detailed technical explanation
How to think about this question
Under the hood, App Engine request logs include latency breakdowns (e.g., wall time, CPU time, and API call latency) that can reveal whether delays occur in the application handler or in external calls like Cloud SQL. Cloud SQL slow query logging uses the `log_slow_queries` flag with a configurable `long_query_time` threshold (default 10 seconds in MySQL), logging queries that exceed this duration to `sys.slow_query_log` or Cloud Logging, enabling analysis of missing indexes or inefficient joins. In a real-world scenario, a missing index on a frequently filtered column can cause full table scans, which slow query logging would flag, while request logs would show high latency on specific endpoints.
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 healthcare organisation deploys an application with a public-facing web tier and a private database tier. The database subnet has no public IP and only accepts connections from the web tier's security group. Questions like this test whether you can design cloud network isolation using VNets/VPCs, subnets, and security group rules.
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.
Optimizing service performance — This question tests Optimizing service performance — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Examine App Engine request logs for latency patterns. — Option A is correct because examining App Engine request logs reveals latency patterns, such as which endpoints or operations are slow, helping to pinpoint whether the bottleneck is in the application code, network, or database. Option C is correct because enabling Cloud SQL slow query logging identifies long-running SQL queries that could be causing database contention or inefficient data retrieval, directly addressing a common performance bottleneck in App Engine applications using Cloud SQL.
What should I do if I get this PCDOE 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 PCDOE 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 PCDOE 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.