Associate-Cloud-Engineer Practice Questions

A.  

Multi-Regional Storage

B.  

Regional Storage

C.  

Nearline Storage

D.  

Coldline Storage

A.  

Save the incoming votes to Firestore. Use Cloud Scheduler to trigger a Cloud Functions instance to periodically process the votes.

B.  

Use a dedicated instance to process the incoming votes. Send the votes directly to this instance.

C.  

Save the incoming votes to a JSON file on Cloud Storage. Process the votes in a batch at the end of the day.

D.  

Save the incoming votes to Pub/Sub. Use the Pub/Sub topic to trigger a Cloud Functions instance to process the votes.

A.  

Use the Google Cloud Pricing Calculator to determine the cost of every Google Cloud resource you expect to use. Use similar size instances for the web server, and use your current on-premises machines as a comparison for Cloud SQL.

B.  

Implement a similar architecture on Google Cloud, and run a reasonable load test on a smaller scale. Check the billing information, and calculate the estimated costs based on the real load your system usually handles.

C.  

Use the Google Cloud Pricing Calculator and select the Cloud Operations template to define your web application with as much detail as possible.

D.  

Create a Google spreadsheet with multiple Google Cloud resource combinations. On a separate sheet, import the current Google Cloud prices and use these prices for the calculations within formulas.

A.  

Run gcloud auth login, enter your login credentials in the dialog window, and paste the received login token to gcloud CLI.

B.  

Create a Google Cloud service account, and download the service account key. Place the key file in a folder on your machine where gcloud CLI can find it.

C.  

Download your Cloud Identity user account key. Place the key file in a folder on your machine where gcloud CLI can find it.

D.  

Run gcloud config set compute/zone $my_zone to set the default zone for gcloud CLI.

E.  

Run gcloud config set project $my_project to set the default project for gcloud CLI.

A.  

Cloud Run for Anthos

B.  

Cloud Run

C.  

App Engine Standard

D.  

Cloud Functions.

A.  

Assign appropriate access for Google services to the service account used by the Compute Engine VM.

B.  

Create a service account with appropriate access for Google services, and configure the application to use this account.

C.  

Store credentials for service accounts with appropriate access for Google services in a config file, and deploy this config file with your application.

D.  

Store credentials for your user account with appropriate access for Google services in a config file, and deploy this config file with your application.

A.  

Create a custom role with view-only project permissions. Add the user's account to the custom role.

B.  

Create a custom role with view-only service permissions. Add the user's account to the custom role.

C.  

Select the built-in IAM project Viewer role. Add the user's account to this role.

D.  

Select the built-in IAM service Viewer role. Add the user's account to this role.

A.  

Modify the minimum number of Cloud Run instances.

B.  

Set a minimum concurrent requests environment variable for the application.

C.  

Modify the maximum number of Cloud Run instances.

D.  

Use traffic splitting.

A.  

Deploy a private autopilot cluster

B.  

Deploy a public autopilot cluster.

C.  

Deploy a standard public cluster and enable shielded nodes.

D.  

Deploy a standard private cluster and enable shielded nodes.

A.  

A cross-region internal Application Load Balancer together with Identity-Aware Proxy to allow only HTTPS traffic.

B.  

A global external Application Load Balancer with a managed SSL certificate to distribute the load and a URL map to target the requests for the static content to the Cloud Storage backend.

C.  

A global external Network Load Balancer pointing to the backend instances to distribute the load evenly. The web servers will forward the request to the Cloud Storage as needed.

D.  

A global external Application Load Balancer to distribute the load and a URL map to target the requests for the static content to the Cloud Storage backend. Install the HTTPS certificates on the instance.