You have a set of applications running on a Google Kubernetes Engine (GKE) cluster, and you are using Stackdriver Kubernetes Engine Monitoring. You are bringing a new containerized application required by your company into production. This application is written by a third party and cannot be modified or reconfigured. The application writes its log information to /var/log/app_messages.log, and you want to send these log entries to Stackdriver Logging. What should you do?

• A.Use the default Stackdriver Kubernetes Engine Monitoring agent configuration.
• B.Deploy a Fluentd daemonset to GKE. Then create a customized input and output configuration to tail the log file in the application's pods and write to Slackdriver Logging.
• C.Install Kubernetes on Google Compute Engine (GCE> and redeploy your applications. Then customize the built-in Stackdriver Logging configuration to tail the log file in the application's pods and write to Stackdriver Logging.
• D.Write a script to tail the log file within the pod and write entries to standard output. Run the script as a sidecar container with the application's pod. Configure a shared volume between the containers to allow the script to have read access to /var/log in the application container.

Comment: *

Name: *

Email: *

Verification: *

You are creating Cloud Logging sinks to export log entries from Cloud Logging to BigQuery for future analysis Your organization has a Google Cloud folder named Dev that contains development projects and a folder named Prod that contains production projects Log entries for development projects must be exported to dev_dataset. and log entries for production projects must be exported to prod_dataset You need to minimize the number of log sinks created and you want to ensure that the log sinks apply to future projects What should you do?

• A.Create a single aggregated log sink at the organization level.
• B.Create a log sink in each project
• C.Create two aggregated log sinks at the organization level, and filter by project ID
• D.Create an aggregated Iog sink in the Dev and Prod folders

Comment: *

Name: *

Email: *

Verification: *

You are the on-call Site Reliability Engineer for a microservice that is deployed to a Google Kubernetes Engine (GKE) Autopilot cluster. Your company runs an online store that publishes order messages to Pub/Sub and a microservice receives these messages and updates stock information in the warehousing system. A sales event caused an increase in orders, and the stock information is not being updated quickly enough. This is causing a large number of orders to be accepted for products that are out of stock You check the metrics for the microservice and compare them to typical levels.

You need to ensure that the warehouse system accurately reflects product inventory at the time orders are placed and minimize the impact on customers What should you do?

• A.Decrease the acknowledgment deadline on the subscription
• B.Add a virtual queue to the online store that allows typical traffic levels
• C.Increase the number of Pod replicas
• D.Increase the Pod CPU and memory limits

Comment: *

Name: *

Email: *

Verification: *

You are developing a strategy for monitoring your Google Cloud Platform (GCP) projects in production using Stackdriver Workspaces. One of the requirements is to be able to quickly identify and react to production environment issues without false alerts from development and staging projects. You want to ensure that you adhere to the principle of least privilege when providing relevant team members with access to Stackdriver Workspaces. What should you do?

• A.Grant relevant team members read access to all GCP production projects. Create Stackdriver workspaces inside each project.
• B.Grant relevant team members the Project Viewer IAM role on all GCP production projects. Create Slackdriver workspaces inside each project.
• C.Choose an existing GCP production project to host the monitoring workspace. Attach the production projects to this workspace. Grant relevant team members read access to the Stackdriver Workspace.
• D.Create a new GCP monitoring project, and create a Stackdriver Workspace inside it. Attach the production projects to this workspace. Grant relevant team members read access to the Stackdriver Workspace.

Comment: *

Name: *

Email: *

Verification: *

Your application services run in Google Kubernetes Engine (GKE). You want to make sure that only images from your centrally-managed Google Container Registry (GCR) image registry in the altostrat-images project can be deployed to the cluster while minimizing development time. What should you do?

• A.Create a custom builder for Cloud Build that will only push images to gcr.io/altostrat-images.
• B.Use a Binary Authorization policy that includes the whitelist name pattern gcr.io/attostrat-images/.
• C.Add a tag to each image in gcr.io/altostrat-images and check that this tag is present when the image is deployed.
• D.Add logic to the deployment pipeline to check that all manifests contain only images from gcr.io/altostrat-images.

Comment: *

Name: *

Email: *

Verification: *