Explanation:
Google Cloud advises maintaining storage utilization below 60% for applications sensitive to latency to ensure optimal performance. While using a service account for read operations is a good practice, it does not directly impact latency. HDD storage, being less performant than SSD, is not recommended for latency-sensitive applications. A global load balancer is unnecessary for Bigtable as it inherently distributes operations based on row keys. For more details, refer to Google Cloud's blog on optimizing Bigtable.
Ultimate access to all questions.
For a latency-sensitive application utilizing Bigtable, which of the following actions aligns with Google Cloud's recommended best practices?
A
Opt for HDD storage over SSD storage to save costs
B
Ensure storage utilization per node does not exceed 60%
C
Implement a global load balancer to manage Bigtable traffic
D
Utilize a service account exclusively for read operations
No comments yet.