Google Professional Cloud DevOps Engineer

Get started today

Ultimate access to all questions.

Explanation:

The correct approach involves installing the Stackdriver logging agent on the application servers for collecting and storing application logs in Stackdriver Logging. Granting developers the IAM Logs Viewer role enables them to access these logs efficiently, ensuring security and ease of troubleshooting. Other options either focus on monitoring metrics, limit log visibility, or introduce unnecessary complexity and delays in log access.

Explanation:

Comments (0)

No comments yet.

To ensure security and facilitate easy troubleshooting of applications running on Google Compute Engine, a minimal setup is required for a pool of application servers. Developers need quick and effective access to application logs. What is the most suitable approach to implement this solution on GCP?

Real Exam

Last updated: April 12, 2026 at 14:02

Install the gsutil command line tool on your application servers. 2) Write a script using gsutil to upload your application log to a Cloud Storage bucket, and then schedule it to run via cron every 5 minutes. 3) Give the developers the IAM Object Viewer access to view the logs in the specified bucket.

0.0%

Install the Stackdriver monitoring agent to the application servers. 2) Give the developers the IAM Monitoring Viewer role to access Stackdriver and view metrics.

33.3%

Install the Stackdriver logging agent to the application servers. 2) Give the developers the IAM Logs Private Logs Viewer role to access Stackdriver and view logs.

Install the Stackdriver logging agent to the application servers. 2) Give the developers the IAM Logs Viewer role to access Stackdriver and view logs.

66.7%