Professional Cloud Developer
265
Professional Cloud Developer
A: Enforce signed URLs for the desired bucket. Grant the Storage Object Viewer IAM role on the bucket to the Compute Engine default service account.
B: Enforce public access prevention for the desired bucket. Grant the Storage Object Viewer IAM role on the bucket to the Compute Engine default service account.
C: Enforce signed URLs for the desired bucket Create and update the Cloud Run service to use a user -managed service account. Grant the Storage Object Viewer IAM role on the bucket to the service account
D: Enforce public access prevention for the desired bucket. Create and update the Cloud Run service to use a user-managed service account. Grant the Storage Object Viewer IAM role on the bucket to the service account.
A: Update your microservices lo log HTTP request methods and URL paths to STDOUT Use the logs router to send container logs to Cloud Logging. Create fillers in Cloud Logging to evaluate the latency of user requests across different methods and URL paths.
B: Install tcpdiimp on your GKE nodes. Run tcpdunm-- to capture network traffic over an extended period of time to collect data. Analyze the data files using Wireshark to determine the cause of high latency
C: Instrument your microservices by installing the Open Telemetry tracing package. Update your application code to send traces to Trace for inspection and analysis. Create an analysis report on Trace to analyze user requests
D: Configure GKE workload metrics using kubect1. Select all Pods to send their metrics to Cloud Monitoring. Create a custom dashboard of application metrics in Cloud Monitoring to determine performance bottlenecks of your GKE cluster.
A: Each group of developers creates a feature branch from the main branch for their work, commits their changes to their branch, and merges their code into the main branch before each major release.
B: Each developer commits their code to the main branch before each product release, conducts testing, and rolls back if integration issues are detected.
C: Each group of developers copies the repository, commits their changes to their repository, and merges their code into the main repository before each product release.
D: Each developer creates a branch for their own work, commits their changes to their branch, and merges their code into the main branch after peer review.
A: Create an image that has cURL installed and configure cURLto run a test plan Deploy the image in a managed instance group, and run one instance of the image for each VM.
B: Create an image that has cURL installed and configure cURL to run a test plan Deploy the image in an unmanaged instance group, and run one instance of the image for each VM.
C: Deploy a distributed load testing framework on a private Google Kubernetes Engine Cluster Deploy additional Pods as needed to initiate more traffic and support the number of concurrent users.
D: Download the container image of a distributed load testing framework on Cloud Shell Sequentially start several instances of the container on Cloud Shell to increase the load on the API.
