PCD practice questions 141–150

1. Question 141 · 357 in bank

   Before promoting your new application code to production, you want to conduct testing across a variety of different users. Although this plan is risky, you want to test the new version of the application with production users and you want to control which users are forwarded to the new version of the application based on their operating system. If bugs are discovered in the new version, you want to roll back the newly deployed version of the application as quickly as possible. What should you do?

   • ADeploy your application on Cloud Run. Use traffic splitting to direct a subset of user traffic to the new version based on the revision tag.
   • BDeploy your application on Google Kubernetes Engine with Anthos Service Mesh. Use traffic splitting to direct a subset of user traffic to the new version based on the user-agent header.
   • CDeploy your application on App Engine. Use traffic splitting to direct a subset of user traffic to the new version based on the IP address.
   • DDeploy your application on Compute Engine. Use Traffic Director to direct a subset of user traffic to the new version based on predefined weights.

   Show answer

   Answer: B

   Explanation

   The key point for this question is the last two word of this statement "you want to control which users are forwarded to the new version of the application based on their operating system". Operating system. Where could the developers find the OS for a certain user? That's the User-Agent header. Example of a header: Mozilla/5.0 (Macintosh; Intel Mac OS X x.y; rv:42.0) Gecko/20100101 Firefox/42.0. - More info about the User-Agent header: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/User-Agent

   Source: Adapted from community discussion — x_cath

   References

   • Google Cloud documentation

   Next question

2. Question 142 · 357 in bank

   Your team is writing a backend application to implement the business logic for an interactive voice response (IVR) system that will support a payroll application. The IVR system has the following technical characteristics: • Each customer phone call is associated with a unique IVR session. • The IVR system creates a separate persistent gRPC connection to the backend for each session. • If the connection is interrupted, the IVR system establishes a new connection, causing a slight latency for that call. You need to determine which compute environment should be used to deploy the backend application. Using current call data, you determine that: • Call duration ranges from 1 to 30 minutes. • Calls are typically made during business hours. • There are significant spikes of calls around certain known dates (e.g., pay days), or when large payroll changes occur. You want to minimize cost, effort, and operational overhead. Where should you deploy the backend application?

   • ACompute Engine
   • BGoogle Kubernetes Engine cluster in Standard mode
   • CCloud Functions
   • DCloud Run

   Show answer

   Answer: D

   Explanation

   Answer D This page shows Cloud Run-specific details for developers who want to use gRPC to connect a Cloud Run service with other services, for example, to provide simple, high performance communication between internal microservices. You can use all gRPC types, streaming or unary, with Cloud Run. Possible use cases include: Communication between internal microservices. High loads of data (gRPC uses protocol buffers, which are up to seven times faster than REST calls). Only a simple service definition is needed, you don't want to write a full client library. Use streaming gRPCs in your gRPC server to build more responsive applications and APIs. https://cloud.google.com/run/docs/tutorials/secure-services#:~:text=The%20backend%20service%20is%20private,Google%20Cloud%20except%20where%20necessary.

   Source: Adapted from community discussion — TNT87

   References

   • Google Cloud documentation

   Next question

3. Question 143 · 357 in bank

   You are developing an application hosted on Google Cloud that uses a MySQL relational database schema. The application will have a large volume of reads and writes to the database and will require backups and ongoing capacity planning. Your team does not have time to fully manage the database but can take on small administrative tasks. How should you host the database?

   • AConfigure Cloud SQL to host the database, and import the schema into Cloud SQL.
   • BDeploy MySQL from the Google Cloud Marketplace to the database using a client, and import the schema.
   • CConfigure Bigtable to host the database, and import the data into Bigtable.
   • DConfigure Cloud Spanner to host the database, and import the schema into Cloud Spanner.
   • EConfigure Firestore to host the database, and import the data into Firestore.

   Show answer

   Answer: A

   Explanation

   The answer A is more likely to be the correct one. Although Cloud Spanner is also a relational DB service (and has certain advantages over Cloud SQL), migrating from MySQL to Cloud Spanner is not as trivial as "import the schema" (stating by the answer D). If D has been excluded, the only relational DB option in the answers is A: Cloud SQL. https://cloud.google.com/spanner/docs/migrating-mysql-to-spanner#migration-process

   Source: Adapted from community discussion — x_cath

   References

   • Google Cloud documentation
   • Google Cloud documentation

   Next question

4. Question 144 · 357 in bank

   You are developing a new web application using Cloud Run and committing code to Cloud Source Repositories. You want to deploy new code in the most efficient way possible. You have already created a Cloud Build YAML file that builds a container and runs the following command: gcloud run deploy. What should you do next?

   • ACreate a Pub/Sub topic to be notified when code is pushed to the repository. Create a Pub/Sub trigger that runs the build file when an event is published to the topic.
   • BCreate a build trigger that runs the build file in response to a repository code being pushed to the development branch.
   • CCreate a webhook build trigger that runs the build file in response to HTTP POST calls to the webhook URL.
   • DCreate a Cron job that runs the following command every 24 hours: gcloud builds submit.

   Show answer

   Answer: B

   References

   • Google Cloud documentation
   • Google Cloud documentation

   Next question

5. Question 145 · 357 in bank

   You are a developer at a large organization. You are deploying a web application to Google Kubernetes Engine (GKE). The DevOps team has built a CI/CD pipeline that uses Cloud Deploy to deploy the application to Dev, Test, and Prod clusters in GKE. After Cloud Deploy successfully deploys the application to the Dev cluster, you want to automatically promote it to the Test cluster. How should you configure this process following Google-recommended best practices?

   • A1. Create a Cloud Build trigger that listens for SUCCEEDED Pub/Sub messages from the clouddeploy-operations topic. 2. Configure Cloud Build to include a step that promotes the application to the Test cluster.
   • B1. Create a Cloud Function that calls the Google Cloud Deploy API to promote the application to the Test cluster. 2. Configure this function to be triggered by SUCCEEDED Pub/Sub messages from the cloud-builds topic.
   • C1. Create a Cloud Function that calls the Google Cloud Deploy API to promote the application to the Test cluster. 2. Configure this function to be triggered by SUCCEEDED Pub/Sub messages from the clouddeploy-operations topic.
   • D1. Create a Cloud Build pipeline that uses the gke-deploy builder. 2. Create a Cloud Build trigger that listens for SUCCEEDED Pub/Sub messages from the cloud-builds topic. 3. Configure this pipeline to run a deployment step to the Test cluster.

   Show answer

   Answer: C

   Explanation

   Option A is not better than Option C because it involves using Cloud Build instead of Cloud Functions for the deployment promotion process. While Cloud Build is a powerful tool for building and testing applications, it is generally not recommended for triggering automated tasks in response to events like the successful deployment of an application to a cluster. In Option A, the Cloud Build trigger listens for SUCCEEDED Pub/Sub messages from the clouddeploy-operations topic, and then promotes the application to the Test cluster as part of the Cloud Build pipeline. This approach involves using a more complex and less scalable infrastructure than using a serverless function like Cloud Functions. On the other hand, Option C uses a Cloud Function to promote the application, which is a more streamlined, scalable, and event-driven solution. Cloud Functions are designed specifically for triggering automated tasks in response to events, making them a better choice for this type of use case.

   Source: Adapted from community discussion — mrvergara

   References

   • Google Cloud documentation

   Next question

6. Question 146 · 357 in bank

   You want to use the Stackdriver Logging Agent to send an application's log file to Stackdriver from a Compute Engine virtual machine instance. After installing the Stackdriver Logging Agent, what should you do first?

   • AEnable the Error Reporting API on the project.
   • BGrant the instance full access to all Cloud APIs.
   • CConfigure the application log file as a custom source.
   • DCreate a Stackdriver Logs Export Sink with a filter that matches the application's log entries.

   Show answer

   Answer: C

   Explanation

   Answer B tells us to authorize the instance to ALL Cloud APIs. I don't see a world where this answer can be right as it breaks the least privilege principle quite heavily.

   Source: Adapted from community discussion — GofX

   References

   • Google Cloud documentation

   Next question

7. Question 147 · 357 in bank

   Your application is running as a container in a Google Kubernetes Engine cluster. You need to add a secret to your application using a secure approach. What should you do?

   • ACreate a Kubernetes Secret, and pass the Secret as an environment variable to the container.
   • BEnable Application-layer Secret Encryption on the cluster using a Cloud Key Management Service (KMS) key.
   • CStore the credential in Cloud KMS. Create a Google service account (GSA) to read the credential from Cloud KMS. Export the GSA as a .json file, and pass the .json file to the container as a volume which can read the credential from Cloud KMS.
   • DStore the credential in Secret Manager. Create a Google service account (GSA) to read the credential from Secret Manager. Create a Kubernetes service account (KSA) to run the container. Use Workload Identity to configure your KSA to act as a GSA.

   Show answer

   Answer: D

   Explanation

   A is not correct because a Kubernetes Secret only encodes the string, and anyone who can read the secret will be able to decode it.

   Source: Adapted from community discussion — mrvergara

   References

   • Kubernetes documentation
   • Google Cloud documentation
   • Google Cloud documentation

   Next question

8. Question 148 · 357 in bank

   You are a developer at a financial institution. You use Cloud Shell to interact with Google Cloud services. User data is currently stored on an ephemeral disk; however, a recently passed regulation mandates that you can no longer store sensitive information on an ephemeral disk. You need to implement a new storage solution for your user data. You want to minimize code changes. Where should you store your user data?

   • AStore user data on a Cloud Shell home disk, and log in at least every 120 days to prevent its deletion.
   • BStore user data on a persistent disk in a Compute Engine instance.
   • CStore user data in a Cloud Storage bucket.
   • DStore user data in BigQuery tables.

   Show answer

   Answer: B

   Explanation

   Store user data in a Cloud Storage bucket is a good option for storing large amounts of data, but if you need to minimize code changes, using a persistent disk in a Compute Engine instance may be a better fit as it provides a more direct replacement for an ephemeral disk with similar access patterns, which will likely require fewer changes to your existing code. Storing user data in a Cloud Storage bucket would likely require more significant changes to how your application interacts with the data.

   Source: Adapted from community discussion — mrvergara

   References

   • Google Cloud documentation

   Next question

9. Question 149 · 357 in bank

   Select 2

   You recently developed a web application to transfer log data to a Cloud Storage bucket daily. Authenticated users will regularly review logs from the prior two weeks for critical events. After that, logs will be reviewed once annually by an external auditor. Data must be stored for a period of no less than 7 years. You want to propose a storage solution that meets these requirements and minimizes costs. What should you do? (Choose two.)

   • AUse the Bucket Lock feature to set the retention policy on the data.
   • BRun a scheduled job to set the storage class to Coldline for objects older than 14 days.
   • CCreate a JSON Web Token (JWT) for users needing access to the Coldline storage buckets.
   • DCreate a lifecycle management policy to set the storage class to Coldline for objects older than 14 days.
   • ECreate a lifecycle management policy to set the storage class to Nearline for objects older than 14 days.

   Show answer

   Answer: AD

   Explanation

   The requirement of storing data for a period of no less than 7 years can be met by setting the retention policy for the data in the Cloud Storage bucket. This can be done using the Bucket Lock feature (A) or a lifecycle management policy (D), which can be set to retain the objects for the required period of 7 years.

   Source: Adapted from community discussion — mrvergara

   References

   • Google Cloud documentation
   • Google Cloud documentation

   Next question

10. Question 150 · 357 in bank

    Your team is developing a Cloud Function triggered by Cloud Storage events. You want to accelerate testing and development of your Cloud Function while following Google-recommended best practices. What should you do?

    • ACreate a new Cloud Function that is triggered when Cloud Audit Logs detects the cloudfunctions.functions.sourceCodeSet operation in the original Cloud Function. Send mock requests to the new function to evaluate the functionality.
    • BMake a copy of the Cloud Function, and rewrite the code to be HTTP-triggered. Edit and test the new version by triggering the HTTP endpoint. Send mock requests to the new function to evaluate the functionality.
    • CInstall the Functions Frameworks library, and configure the Cloud Function on localhost. Make a copy of the function, and make edits to the new version. Test the new version using curl.
    • DMake a copy of the Cloud Function in the Google Cloud console. Use the Cloud console's in-line editor to make source code changes to the new function. Modify your web application to call the new function, and test the new version in production

    Show answer

    Answer: C

    Explanation

    Making a copy of the function for edits ensures that your changes do not affect the original function in production. It provides a controlled environment for development and testing. curl Testing: Testing the new version using curl is a simple and effective way to send mock requests and evaluate the functionality of your Cloud Function locally. Using the Functions Frameworks library and local testing provides a development environment that is both efficient and aligned with Google-recommended best practices for Cloud Functions development.

    Source: Adapted from community discussion — braska

    References

    • Google Cloud documentation
    • Google Cloud documentation
    • Google Cloud documentation

    Next question

Keyboard:J Kmove between questionsA–Dselect an answerRshow or hide the answer← →change page

PCD practice, question 141. 357 questions available.