Answer-first summary for fast verification
Answer: Connect to the Google Cloud console and open Cloud Shell on your personal computer. Clone the Git repository and execute the workaround script. Ensure that the issue has been fixed.
Option C is the most efficient and cost-effective solution. Cloud Shell provides a pre-configured, browser-based environment with the gcloud CLI and other tools already installed. It requires no setup on the personal computer, allowing immediate access to clone the Git repository, execute the script, and verify the fix. This avoids delays from installing software (as in D or B) or provisioning resources (as in A), while keeping costs minimal since Cloud Shell usage is free within limits. Options A, B, and D involve additional setup time or potential costs, making C the optimal choice.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
You're developing a web application using Cloud Run and Cloud Storage. A production issue arises that requires immediate troubleshooting. The workaround involves executing a script from a Git repository. Your corporate laptop is unavailable, but you can access the Git repository and Google Cloud resources using your corporate credentials from your personal computer. How can you resolve the issue quickly and efficiently while minimizing additional costs?
A
Create and launch a workstation with Cloud Workstations on your personal computer. Authenticate and set up API access in the workstation. Clone the Git repository and execute the workaround script. Ensure that the issue has been fixed.
B
Install VS Code and the extension Cloud Code for VS Code on your personal computer. Check the Cloud Run logs in Cloud Code to confirm the error. Execute the workaround script. Ensure that the issue has been fixed.
C
Connect to the Google Cloud console and open Cloud Shell on your personal computer. Clone the Git repository and execute the workaround script. Ensure that the issue has been fixed.
D
Download and install the gcloud CLI on your personal computer. Authenticate and set up API access. Clone the Git repository and execute the workaround script. Ensure that the issue has been fixed.