You are designing an augmented reality game for iOS and Android devices. You plan to use Cloud Spanner as the primary backend database for game state storage and player authentication. You want to track in-game rewards that players unlock at every stage of the game. During the testing phase, you discovered that costs are much higher than anticipated, but the query response times are within the SLA. You want to follow Google-recommended practices. You need the database to be performant and highly available while you keep costs low.
What should you do?
A. Manually scale down the number of nodes after the peak period has passed.
B. Use interleaving to co-locate parent and child rows.
C. Use the Cloud Spanner query optimizer to determine the most efficient way to execute the SQL query.
D. Use granular instance sizing in Cloud Spanner and Autoscaler.
Answer: D
Explanation:
Granular instance is available in Public Preview. With this feature, you can run workloads on Spanner at as low as 1/10th the cost of regular instances, https://cloud.google.com/blog/products/databases/get-more-out-of-spanner-with-granular-instance-sizing
Latest Professional Cloud Database Engineer Dumps Valid Version with 120 Q&As
Latest And Valid Q&A | Instant Download | Once Fail, Full Refund