Professional-Cloud-Developer Practice Test

You are developing a new application. You want the application to be triggered only when a given file is updated in your Cloud Storage bucket. Your trigger might change, so your process must support different types of triggers. You want the configuration to be simple so that multiple team members can update the triggers in the future. What should you do?

A. Create an Eventarc trigger that monitors your Cloud Storage bucket for a specific filename, and set the target as Cloud Run.

B. Configure Cloud Storage events to be sent to Pub/Sub, and use Pub/Sub events to trigger a Cloud Build job that executes your application.

C. Configure a Firebase function that executes your application and is triggered when an object is updated in Cloud Storage.

D. Configure a Cloud Function that executes your application and is triggered when an object is updated in Cloud Storage.

Your App Engine standard configuration is as follows:
service: production
instance_class: B1
You want to limit the application to 5 instances. Which code snippet should you include in your configuration?

A. manual_scaling:instances: 5min_pending_latency: 30ms

B. manual_scaling:max_instances: 5idle_timeout: 10m

C. basic_scaling:instances: 5min_pending_latency: 30ms

D. basic_scaling:max_instances: 5idle_timeout: 10m

You have an on-premises application that authenticates to the Cloud Storage API using a user-managed service account with a user-managed key. The application connects to Cloud Storage using Private Google Access over a Dedicated Interconnect link. You discover that requests from the application to access objects in the Cloud Storage bucket are failing with a 403 Permission Denied error code. What is the likely cause of this issue?

A. The folder structure inside the bucket and object paths have changed.

B. The permissions of the service account’s predefined role have changed.

C. The service account key has been rotated but not updated on the application server.

D. The Interconnect link from the on-premises data center to Google Cloud is experiencing a temporary outage.

You have containerized a legacy application that stores its configuration on an NFS share. You need to deploy this application to Google Kubernetes Engine (GKE) and do not want the application serving traffic until after the configuration has been retrieved. What should you do?

A. Use the gsutil utility to copy files from within the Docker container at startup, and start the service using an ENTRYPOINT script.

B. Create a PersistentVolumeClaim on the GKE cluster. Access the configuration files from the volume, and start the service using an ENTRYPOINT script.

C. Use the COPY statement in the Dockerfile to load the configuration into the container image. Verify that the configuration is available, and start the service using an ENTRYPOINT script.

D. Add a startup script to the GKE instance group to mount the NFS share at node startup. Copy the configuration files into the container, and start the service using an ENTRYPOINT script.

Your application performs well when tested locally, but it runs significantly slower when you deploy it to App Engine standard environment. You want to diagnose the problem. What should you do?

A. File a ticket with Cloud Support indicating that the application performs faster locally.

B. Use Stackdriver Debugger Snapshots to look at a point-in-time execution of the application.

C. Use Stackdriver Trace to determine which functions within the application have higher latency.

D. Add logging commands to the application and use Stackdriver Logging to check where the latency problem occurs.