Cloud Engineer

FREE Associate Cloud Engineer v1.0 Questions and Answers

For a latency-sensitive website, you wish to use GCP to run a single HTTP reverse proxy with caching. The CPU use for this specific reverse proxy is minimal. A 30-GB in-memory cache is desired, and an extra 2 GB of memory is required for the remaining processes. Cost savings are what you seek. How should this reverse proxy be used?

Run it on Compute Engine, and choose a custom instance type with 6 vCPUs and 32 GB of memory

Create a Cloud Memorystore for Redis instance with 32-GB capacity

Run it on Compute Engine, choose the instance type n1-standard-1, and add an SSD persistent disk of 32 GB

Package it in a container image, and run it on Kubernetes Engine, using n1-standard-32 instances as nodes

Correct! Wrong!

Explanation:
To run a single caching HTTP reverse proxy on GCP for a latency-sensitive website with a 30-GB in-memory cache and an additional 2 GB of memory for the rest of the processes while minimizing cost, you should run it on a Compute Engine instance with a custom machine type.

In your own data center, bare-metal servers are hosting an application. Cloud storage must be accessible to the application. Security regulations, however, forbid the servers hosting the application from having available IP addresses or internet access. It would help if you stuck to Google's advice to grant the application access to cloud storage. What ought you to do?

1. Use nslookup to get the IP address for storage.googleapis.com
2. Negotiate with the security team to allow the servers to have a public IP address.
3. Only permit egress traffic from those servers to storage.googleapis.com's IP addresses

1. Using Cloud VPN, create a VPN tunnel to a Virtual Private Cloud (VPC) in Google Cloud
2. In this VPC, create a Compute Engine instance and install the Squid proxy server on this instance
3. Configure your servers to use that instance as a proxy to access Cloud Storage

1. Using Cloud VPN or Interconnect, create a tunnel to a VPC in Google Cloud
2. Use Cloud Router to create a custom route advertisement for 199.36.153.4/30. Announce that network to your on-premises network through the VPN tunnel
3. In your on-premises network, configure your DNS server to resolve *.googleapis.com as a CNAME to restricted.googleapis.com

1. Use Migrate for Compute Engine (formerly known as Velostrata) to migrate those servers to Compute Engine
2. Create an internal load balancer (ILB) that uses storage.googleapis.com as a backend
3. Configure your new instances to use this ILB as a proxy

Correct! Wrong!

Explanation:
Suppose your application needs access to Cloud Storage, but your security policies prevent the servers hosting the application from having public IP addresses or access to the internet. In that case, you can follow Google-recommended practices to provide the application access to Cloud Storage by migrating your servers to Compute Engine and creating an internal load balancer (ILB) with storage.googleapis.com as a backend.

You wish to set up a Cloud Run application that handles Cloud Pub/Sub topic message processing. You want to adhere to Google's suggestions. What ought you to do?

1. Grant the Pub/Sub Subscriber role to the service account used by Cloud Run
2. Create a Cloud Pub/Sub subscription for that topic
3. Make your application pull messages from that subscription

1. Create a Cloud Function that uses a Cloud Pub/Sub trigger on that topic
2. Call your application on Cloud Run from the Cloud Function for every message

1. Deploy your application on Cloud Run on GKE with the connectivity set to Internal
2. Create a Cloud Pub/Sub subscription for that topic
3. In the same Google Kubernetes Engine cluster as your application, deploy a container that takes the messages and sends them to your application

1. Create a service account
2. Give the Cloud Run Invoker role to that service account for your Cloud Run application
3. Create a Cloud Pub/Sub subscription that uses that service account and uses your Cloud Run application as the push endpoint

Correct! Wrong!

A container image-packaged program has to be deployed in a new project. Not many requests are made daily to the application, which exposes an HTTP endpoint. You want to reduce spending. What ought you to do?

Deploy the container on Cloud Run on GKE

Deploy the container on Cloud Run

Deploy the container on GKE with cluster autoscaling and horizontal pod autoscaling enabled

Deploy the container on App Engine Flexible

Correct! Wrong!

Explanation:
To deploy an application, packaged in a container image, in a new project with an HTTP endpoint that receives very few requests per day while minimizing costs, you should deploy the container on Cloud Run on GKE.

You used Cloud Spanner to build a Google Cloud application. While monitoring the environment, your support staff shouldn't have access to table data. You want to adhere to Google's best practices, so you need an efficient way to grant the right rights to your support team. What ought you to do?

Add the support team group to the roles/spanner.databaseUser role

Add the support team group to the roles/monitoring.viewer role

Add the support team group to the roles/stackdriver.accounts.viewer role

Add the support team group to the roles/spanner.databaseReader role

Correct! Wrong!

Explanation:
To grant your support team permission to monitor your Cloud Spanner environment without giving them access to table data, you can add the support team group to the roles/spanner.database user role. This role grants users the ability to read metadata, such as schema and indexes, for a specific Cloud Spanner database but does not provide access to read or modify data.

Your business already has a GCP organization with a billing account and numerous projects. Your business acquired a company with hundreds of projects and its billing account. You want to combine the GCP expenses of the two GCP entities into one invoice. You want to connect all costs starting tomorrow. What ought you to do?

Set up your billing account and the acquired company's billing account so that billing information is exported into a single BigQuery dataset

Link the acquired company's projects to your company's billing account

Create a new GCP organization and a new billing account. Migrate the acquired company's projects and your company's projects into the new GCP organization and link the projects to the new billing account

Project migration into your firm's GCP organization from the acquired company. Connect the migrated projects to the billing account for your business

Correct! Wrong!

The audit log files for your company must be kept for three years because it is a financial institution. There are several Google Cloud projects in your company. It would help if you practiced a cost-efficient log file retention strategy. What ought you to do?

Make a Cloud Audit export to the sink that stores logs to a Coldline Storage bucket

Create a sink export that stores Cloud Audit logs to BigQuery

Write a Cloud Dataflow pipeline to store the logs in Cloud SQL and export these logs to Cloud Pub/Sub

Create a custom script that copies the logs from the Stackdriver logs to BigQuery using the logging API

Correct! Wrong!

Explanation:
To implement a cost-effective approach for log file retention in a scenario where hundreds of Google Cloud projects need to store audit log files for three years, you can create an export to the sink that saves logs from Cloud Audit to BigQuery.

FREE Associate Cloud Engineer v1.0 Questions and Answers

You wish to set up a Cloud Run application that handles Cloud Pub/Sub topic message processing. You want to adhere to Google's suggestions. What ought you to do?

A container image-packaged program has to be deployed in a new project. Not many requests are made daily to the application, which exposes an HTTP endpoint. You want to reduce spending. What ought you to do?

You used Cloud Spanner to build a Google Cloud application. While monitoring the environment, your support staff shouldn't have access to table data. You want to adhere to Google's best practices, so you need an efficient way to grant the right rights to your support team. What ought you to do?

The audit log files for your company must be kept for three years because it is a financial institution. There are several Google Cloud projects in your company. It would help if you practiced a cost-efficient log file retention strategy. What ought you to do?

Related Post