Free Google Professional Cloud Database Engineer Actual Exam Questions - Question 4 Discussion

Question No. 4
Your application uses Cloud SQL for MySQL. Your users run reports on data that relies on near-real
time; however, the additional analytics caused excessive load on the primary database. You created a
read replica for the analytics workloads, but now your users are complaining about the lag in data
changes and that their reports are still slow. You need to improve the report performance and
shorten the lag in data replication without making changes to the current reports. Which two
approaches should you implement? (Choose two.)
Select all that apply, then reveal solution.
US
SQ
Sarah Q.
2026-02-19

B imo, adding more replicas definitely helps distribute the reporting load better. A also makes sense since indexes speed up query execution without changing reports. E feels like a bigger shift than the question might want.

0
RZ
Ryan Z.
2026-02-16

B – More replicas spread the load and reduce report delays. A – Secondary indexes speed up queries without changing

0
MV
Marco V.
2026-01-29

Not C, because stopping replication defeats the purpose of having a replica for near-real time data. B is solid since more replicas mean less load per replica and better performance for users.

0
NT
Noah T.
2026-01-16

Maybe B and C; spreading load with replicas plus parallel replication should cut lag.

0
NT
Noah T.
2026-01-16

This one feels tricky but starting with B makes sense-adding more read replicas to spread out the load should help with slow reports. And E is interesting since moving analytics to BigQuery can reduce load on the primary DB and handle near-real time data better. The others seem less likely because disabling replication sounds risky or confusing, and creating indexes only on replicas might not fix lag issues. So for me, B and E look like the best bets here.

0