Free Google Professional Data Engineer Actual Exam Questions - Question 6 Discussion
a. You are targeting funding that will allow your startup lo serve customers globally. Your current goal
is to optimize for cost, and your post-funding goat is to optimize for global presence and
performance. You must use a native JDBC driver. What should you do?
Option B seems off because Bigtable doesn’t support native JDBC drivers, so that contradicts the question requirements. Option C is similar but also includes Bigtable, which complicates things with JDBC. Between A and D, A’s Cloud Spanner offers global scaling natively, which fits the long-term goal better. But for cost optimization early on, D’s zonal Cloud SQL is cheaper and easier to manage. Since the question prioritizes cost first and global presence after funding, D matches the phased approach without adding complexity that JDBC might not handle well.
It’s A because Cloud Spanner natively supports JDBC and scales globally after funding, unlike Cloud SQL which may require more complex migration or doesn't scale as smoothly across regions.
D makes sense because starting with zonal Cloud SQL is cheaper and simpler, then moving to highly available improves reliability later. It fits the cost-first, performance-later plan well without complex setup upfront.
It’s D. Starting with a zonal Cloud SQL instance keeps things simple and cheap before funding, and then upgrading to a highly available setup aligns well with the post-funding goal of better performance. It also matches the requirement for a native JDBC driver since Cloud SQL has solid support for that. A and B involve more complex multi-region setups too early, which could be costly and unnecessary right now. C is off because Bigtable doesn’t support SQL/JDBC natively, so it wouldn’t fit the driver requirement. D feels like the safer, more practical choice for cost optimization first and scal
D imo, starting with a zonal Cloud SQL instance keeps costs low for now, and upgrading to highly available Cloud SQL after funding still fits the goal without jumping to more complex solutions early.
A/B? Cloud Spanner scales great globally but costs more initially, so starting single region fits cost goals. Cloud SQL with high availability might be cheaper at first but doesn’t handle global scaling as smoothly later.
I’m thinking option A makes the most sense here. Starting with Cloud Spanner single region keeps things simple and cost-effective, and then you can move to multi-region once you get funding for better global presence and performance. Cloud Spanner also supports native JDBC drivers, which is a must. The other options seem to mix databases or don’t scale as well globally when you need it later. So, sticking with Cloud Spanner for both phases fits the plan cleanly.
A/D? Starting with single region Cloud Spanner or Cloud SQL zonal seems okay for cost, then scaling later fits the plan.