Google Associate Cloud Engineer - Practice Test 3
Your web application, hosted on Cloud Run, experiences slow initial page loads for some users, while subsequent pages load quickly. You want to optimize performance and reduce these 'cold start' delays, following Google's recommended best practices. What configuration change should you implement?
The described issue is a classic 'cold start' problem, where serverless instances take time to initialize when no active instances are available. Setting a minimum number of instances ensures that a specified number of instances are always running and ready to serve requests, thereby eliminating or significantly reducing cold start delays for initial page loads. This is a direct recommendation from Google for optimizing Cloud Run performance.
You have just installed the Google Cloud CLI on your workstation. Before you can effectively use commands like `gcloud compute instances list` to manage resources, which two essential steps must you take?
To interact with Google Cloud resources using the gcloud CLI, you first need to authenticate your identity (Option 1) to ensure you have the necessary permissions. Additionally, you must specify which Google Cloud project your commands should operate within (Option 5), as resources like compute instances are scoped to specific projects. Both steps are fundamental for successful gcloud CLI operations.
Your organization utilizes a single sign-on (SSO) identity provider that supports Security Assertion Markup Language (SAML) integration. Your users are managed within Cloud Identity. You need to configure Cloud Identity so that users authenticate using your company's existing SSO provider. What is the correct approach?
The scenario describes integrating an existing SAML-based SSO identity provider with Cloud Identity. In this setup, the company's SSO provider is the Identity Provider (IdP), and Google Cloud (via Cloud Identity) acts as the Service Provider (SP). Therefore, you need to configure Cloud Identity to use a third-party IdP, with Google as the SP.
You have been using Google Cloud for personal experimentation, with costs charged to your personal credit card. Your company now wants to consolidate billing for your projects under their corporate monthly invoice. What is the most appropriate action to take?
To streamline billing and have project costs charged to the company's invoice, the projects must be linked to the company's billing account. Changing the billing account directly associates the project's expenses with the desired corporate billing entity. Other options either don't achieve the goal or are indirect methods that don't solve the core billing association problem.
A managed instance group (MIG) in Google Cloud has failed to create new instances, leading to a reduced number of running instances below the desired target. This is impacting the application's ability to handle expected traffic. You suspect an issue with persistent disks preventing new instance creation. What is the most appropriate action to resolve this issue and ensure future instance creation succeeds?
The primary issue is likely that persistent disks were not deleted when instances were terminated, preventing new instances from being created with the same name. The solution involves first clearing the existing conflicting persistent disks. Then, to prevent recurrence, the instance template needs to be updated to set `disks.autoDelete` to `true`, ensuring boot disks are automatically deleted with their instances.