Google Updated Associate-Cloud-Engineer Exam Questions and Answers by selina

The requirements specify a relational database that provides global scale and is a managed service.

Cloud Spanner is Google Cloud ' s globally distributed, strong-consistency database service. It provides limitless horizontal scaling while maintaining the structure of a relational database, making it the best fit for an application with a rapidly growing, global user base. As a fully managed service, it inherently minimizes management and administration efforts.

Cloud SQL (Option A) is a regional managed relational database and does not offer the same unlimited, global horizontal scaling capability as Spanner.

The correct answer is B because the task is not asking you to invoke the Cloud Run service yourself; it asks for permission to manage IAM policy related to service accounts so the new service account can be granted the required access. The roles/run.invoker role would allow a principal to invoke a Cloud Run service, but it would not give your user permission to modify service account IAM policies. Editor and Owner are excessive and violate least privilege because they grant broad project-level permissions. The roles/iam.serviceAccountAdmin role is the most appropriate option listed because it provides administrative control over service accounts, including managing their configuration and IAM-related access without granting full project ownership.

https://cloud.google.com/deployment-manager/docs/configuration/create-basic-configuration

The reason is that when you do health check, you want the VM to be working. Do the first check after initial setup time of 3 mins = 180 s < 200 s is reasonable.

The reason why our autoscaling is adding more instances than needed is that it checks 30 seconds after launching the instance and at this point, the instance isnt up and isnt ready to serve traffic. So our autoscaling policy starts another instance  again checks this after 30 seconds and the cycle repeats until it gets to the maximum instances or the instances launched earlier are healthy and start processing traffic  which happens after 180 seconds (3 minutes). This can be easily rectified by adjusting the initial delay to be higher than the time it takes for the instance to become available for processing traffic.So setting this to 200 ensures that it waits until the instance is up (around 180-second mark) and then starts forwarding traffic to this instance. Even after a cool out period, if the CPU utilization is still high, the autoscaler can again scale up but this scale-up is genuine and is based on the actual load.

Initial Delay Seconds  This setting delays autohealing from potentially prematurely recreating the instance if the instance is in the process of starting up. The initial delay timer starts when the currentAction of the instance is VERIFYING.

Ref: https://cloud.google.com/compute/docs/instance-groups/autohealing-instances-in-migs