Associate-Cloud-Engineer Practice Questions

A.  

Enable the Identity Aware Proxy API on the project.

B.  

Scan the bucker using the Data Loss Prevention API.

C.  

Allow only a single Service Account access to read the data.

D.  

Enable Data Access audit logs for the Cloud Storage API.

A.  

Configure Cloud Identity-Aware Proxy (or HTTPS resources

B.  

Configure Cloud Identity-Aware Proxy for SSH and TCP resources.

C.  

Create an SSH keypair and store the public key as a project-wide SSH Key

D.  

Create an SSH keypair and store the private key as a project-wide SSH Key

A.  

Select the MIG from the Compute Engine console and, in the menu, select Replace VMs.

B.  

Use the gcloud compute instance-groups managed recreate-instances command to recreate theVM.

C.  

Use the gcloud compute instances update command with a REFRESH action for the VM.

D.  

Update and apply the instance template of the MI

G.  

A.  

Deploy an ingress resource on the GKE cluster to expose the API to the internet. Use Cloud Armor to filter for IP addresses that can connect to the API. On the Cloud Run service, configure the application to fetch its public IP address and update the Cloud Armor policy on startup to allow this IP address to call the API on ports 80 and 443.

B.  

Create an egress firewall rule on the VPC to allow connections to 0.0.0.0/0 on ports 80 and 443.

C.  

Create an ingress firewall rule on the VPC to allow connections from 0.0.0.0/0 on ports 80 and 443.

D.  

Deploy an internal Application Load Balancer to expose the API on GKE to the VP

C.  

Configure Cloud DNS with the IP address of the internal Application Load Balancer. Deploy a Serverless VPC Access connector to allow the Cloud Run service to call the API through the FQDN on Cloud DNS.

A.  

Use the cost breakdown report with the available filters from Cloud Billing to visualize the data

B.  

Enable the Cloud Billing export to BigQuery. and use Looker Studio to visualize the data

C.  

Run Queries in Cloud Monitoring Create dashboards to visualize the billing metrics

D.  

Enable Cloud Monitoring metrics export to BigQuery and use Looker to visualize the data

A.  

Reserve the IP 10.0.3.21 as a static internal IP address using gcloud and assign it to the licensing server.

B.  

Reserve the IP 10.0.3.21 as a static public IP address using gcloud and assign it to the licensing server.

C.  

Use the IP 10.0.3.21 as a custom ephemeral IP address and assign it to the licensing server.

D.  

Start the licensing server with an automatic ephemeral IP address, and then promote it to a static internal IP address.

A.  

Use a Cloud Scheduler cron job to trigger a Cloud Function that queries Cloud Logging and sends the logs to the SaaS tool.

B.  

Create a Cloud Logging sink and configure Pub/Sub as the destination. Configure the SaaS tool to subscribe to the Pub/Sub topic to retrieve the logs.

C.  

Create a Cloud Logging sink and configure Cloud Storage as the destination. Configure the SaaS tool to read the Cloud Storage bucket to retrieve the logs.

D.  

Create a Cloud Logging sink and configure BigQuery as the destination. Configure the SaaS tool to query BigQuery to retrieve the logs.

A.  

Verify that both projects are in a GCP Organization. Create a new VPC and add all instances.

B.  

Verify that both projects are in a GCP Organization. Share the VPC from one project and request that the Compute Engine instances in the other project use this shared VP

C.  

C.  

Verify that you are the Project Administrator of both projects. Create two new VPCs and add all instances.

D.  

Verify that you are the Project Administrator of both projects. Create a new VPC and add all instances.

A.  

Add users to roles/bigquery user role only, instead of roles/bigquery dataOwner.

B.  

Add users to roles/bigquery dataEditor role only, instead of roles/bigquery dataOwner.

C.  

Create a custom role by removing delete permissions, and add users to that role only.

D.  

Create a custom role by removing delete permissions. Add users to the group, and then add the group to the custom role.

A.  

Use the command gcloud config set container/cluster dev.

B.  

Use the command gcloud container clusters update dev.

C.  

Create a file called gke.default in the ~/.gcloud aname.

D.  

Create a file called defaults.json in the ~/.gcloud folder that contains the cluster name.