Google Associate Cloud Engineer - Associate-Cloud-Engineer Free Exam Questions

A. Manage service accounts as resources.

B. Create as few service accounts as possible.

C. Delete any unused service accounts immediately.

D. Create single-purpose service accounts.

E. Use random names for the service accounts.

A. Use a standard naming convention for projects that includes the department name. Configure both organization policies and log sinks on the projects.

B. Organize projects under folders for each department. Configure both organization policies and log sinks on the folders.

C. Use a standard naming convention for projects that includes the department name. Configure organization policies on the organization and log sinks on the projects.

D. Organize projects under folders for each department. Configure organization policies on the organization and log sinks on the folders.

A. Create a custom Compute Engine image from a snapshot.
Create your images from that image.

B. Create a Compute Engine snapshot of your base VM.
Create your instances from that snapshot.

C. Create a custom Compute Engine image from a snapshot.
Create your instances from that image.

D. Create a Compute Engine snapshot of your base VM.
Create your images from that snapshot.

A. Change the region property setting in the existing App Engine application from us-central to asia- northeast1.

B. Change the default region property setting in the existing GCP project to asia-northeast1.

C. Create a second App Engine application in the existing GCP project and specify asia-northeast1 as the region to serve your application.

D. Create a new GCP project and create an App Engine application inside this new project.
Specify asia-northeast1 as the region to serve your application.

A. Create an organization to contain all the dev projects. Create an Identity and Access Management (IAM) policy to limit the resources in US regions.

B. Create an Identity and Access Management (IAM) policy to restrict the resources locations in all dev projects. Apply the policy to all dev roles.

C. Create an Identity and Access Management (IAM) policy to restrict the resources locations in the US. Apply the policy to all dev projects.

D. Create a folder to contain all the dev projects. Create an organization policy to limit resources in US locations.

A. Use the command gcloud config set container/cluster dev

B. Create a file called gke. default in the -/ .gcloud folder that contains the cluster name

C. Use the command gcloud container clusters update dev

D. Create a file called defaults. j son in the -/.gcioud folder that contains the cluster name

A. Use the kubectl rollout undocommand.

B. Use the kubectl rollout restartcommand to revert the deployment.

C. Delete the deployment.

D. Manually scale down the new Pods and scale up the old Pods.

A. Grant the basic role roles/viewer and the predefined role roles/compute.admin to the DevOps group.

B. Create an IAM policy and grant all compute.instanceAdmin.* permissions to the policy. Attach the policy to the DevOps group.

C. Grant the basic role roles/editor to the DevOps group.

D. Create a custom role at the folder level and grant all compute.instanceAdmin.* permissions to the role. Grant the custom role to the DevOps group.

A. Create a managed instance group. Verify that the autoscaling setting is on.

B. Create an HTTP load balancer with a backend configuration that references an existing instance group.
Set the health check to healthy (HTTP)

C. Create a managed instance group. Set the Autohealing health check to healthy (HTTP)

D. Create an HTTP load balancer with a backend configuration that references an existing instance group.
Define a balancing mode and set the maximum RPS to 10.

A. Use a proxy Network Load Balancer for the MIG and an A record in your DNS private zone with the load balancer's IP address.

B. Use an Application Load Balancer for the MIG and an A record in your DNS public zone with the load balancer's IP address.

C. Use a proxy Network Load Balancer for the MIG and a CNAME record in your DNS public zone with the load balancer's IP address.

D. Use an Application Load Balancer for the MIG and a CNAME record in your DNS private zone with the load balancer's IP address.

A. Create a temporary account for the auditor in Cloud Identity, and give that account the Viewer role on the project.

B. Create a temporary account for the auditor in Cloud Identity, and give that account the Security Reviewer role on the project.

C. Ask the auditor for their Google account, and give them the Security Reviewer role on the project.

D. Ask the auditor for their Google account, and give them the Viewer role on the project.

A. Go to the IAM & admin console, grant a user account permissions similar to the service account permissions, and use this user account for authentication from your data center.

B. Use service account credentials in your on-premises application.

C. Use gcloud to create a key file for the service account that has appropriate permissions.

D. Set up direct interconnect between your data center and Google Cloud Platform to enable authentication for your on-premises applications.

A. Write a custom script that uses logging API to copy the logs from Stackdriver logs to BigQuery.

B. Create an export to the sink that saves logs from Cloud Audit to a Coldline Storage bucket.

C. Create an export to the sink that saves logs from Cloud Audit to BigQuery.

D. Export these logs to Cloud Pub/Sub and write a Cloud Dataflow pipeline to store logs to Cloud SQL.

A. Automatic Scaling with min_idle_instances set to 3.

B. Basic Scaling with max_instances set to 3.

C. Basic Scaling with min_instances set to 3.

D. Manual Scaling with 3 instances.

A. Add a network tag of your choice to the instance running the LDAP server. Create a firewall rule to allow egress on UDP port 636 for that network tag.

B. Add the network tag allow-udp-636 to the VM instance running the LDAP server.

C. Create a route called allow-udp-636 and set the next hop to be the VM instance running the LDAP server.

D. Add a network tag of your choice to the instance. Create a firewall rule to allow ingress on UDP port 636 for that network tag.