Google Cloud Associate Engineer Exam Part 1

Every employee of your company has a Google account. Your operational team needs to manage a large number of instances on Compute Engine. Each member of this team needs only administrative access to the servers. Your security team wants to ensure that the deployment of credentials is operationally efficient and must be able to determine who accessed a given instance. What should you do?

• Generate a new SSH key pair. Give the private key to each member of your team. Configure the public key in the metadata of each instance.

• Ask each member of the team to generate a new SSH key pair and to send you their public key. Use a configuration management tool to deploy those keys on each instance.

• Ask each member of the team to generate a new SSH key pair and to add the public key to their Google account. Grant the compute.osAdminLogin role to the Google group corresponding to this team.

• Generate a new SSH key pair. Give the private key to each member of your team. Configure the public key as a project-wide public SSH key in your Cloud Platform project and allow project-wide public SSH keys on each instance.

Answer explanation

Asking each team member to generate their own SSH key pair and adding the public key to their Google account ensures individual accountability. Granting the compute.osAdminLogin role to the group provides necessary administrative access while maintaining security.

You need to create a custom VPC with a single subnet. The subnet's range must be as large as possible. Which range should you use?

• 0.0.0.0/0

• 10.0.0.0/8

• 172.16.0.0/12

• 192.168.0.0/16

Answer explanation

The range 10.0.0.0/8 provides the largest possible subnet size, allowing for over 16 million IP addresses. In contrast, 172.16.0.0/12 and 192.168.0.0/16 offer smaller ranges, making 10.0.0.0/8 the best choice.

You want to select and configure a cost-effective solution for relational data on Google Cloud Platform. You are working with a small set of operational data in one geographic location. You need to support point-in-time recovery. What should you do?

• Select Cloud SQL (MySQL). Verify that the enable binary logging option is selected.

• Select Cloud SQL (MySQL). Select the create failover replicas option.

• Select Cloud Spanner. Set up your instance with 2 nodes.

• Select Cloud Spanner. Set up your instance as multi-regional.

Answer explanation

Selecting Cloud SQL (MySQL) with binary logging enabled allows for point-in-time recovery, making it suitable for small operational data in a single location. Other options do not meet the requirement for point-in-time recovery.

You want to configure autohealing for network load balancing for a group of Compute Engine instances that run in multiple zones, using the fewest possible steps. You need to configure re-creation of VMs if they are unresponsive after 3 attempts of 10 seconds each. What should you do?

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

• 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.

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

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

Answer explanation

Creating a managed instance group with an Autohealing health check set to healthy (HTTP) ensures that unresponsive VMs are automatically recreated after 3 failed health checks, fulfilling the requirement with minimal steps.

You are using multiple configurations for gcloud. You want to review the configured Kubernetes Engine cluster of an inactive configuration using the fewest possible steps. What should you do?

• Use gcloud config configurations describe to review the output.

• Use gcloud config configurations activate and gcloud config list to review the output.

• Use kubectl config get-contexts to review the output.

• Use kubectl config use-context and kubectl config view to review the output.

Answer explanation

To review the Kubernetes Engine cluster of an inactive configuration, use 'kubectl config use-context' to switch to the desired context, then 'kubectl config view' to see the details. This is the most efficient method.

Your company uses Cloud Storage to store application backup files for disaster recovery purposes. You want to follow Google's recommended practices. Which storage option should you use?

• Multi-Regional Storage

• Regional Storage

• Nearline Storage

• Coldline Storage

Answer explanation

Coldline Storage is ideal for long-term storage of infrequently accessed data, such as backup files for disaster recovery. It offers lower costs for storage while still ensuring data availability when needed.

Several employees at your company have been creating projects with Cloud Platform and paying for it with their personal credit cards, which the company reimburses. The company wants to centralize all these projects under a single, new billing account. What should you do?

• Contact [e-mail] with your bank account details and request a corporate billing account for your company.

• Create a ticket with Google Support and wait for their call to share your credit card details over the phone.

• In the Google Platform Console, go to the Resource Manage and move all projects to the root Organization.

• In the Google Cloud Platform Console, create a new billing account and set up a payment method.

Answer explanation

To centralize projects under a single billing account, you should create a new billing account in the Google Cloud Platform Console and set up a payment method. This allows for better management and tracking of expenses.

You have an application that looks for its licensing server on the IP 10.0.3.21. You need to deploy the licensing server on Compute Engine. You do not want to change the configuration of the application and want the application to be able to reach the licensing server. What should you do?

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

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

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

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

Answer explanation

Reserving the IP 10.0.3.21 as a static internal IP ensures the licensing server is always reachable at that address without changing the application's configuration, which requires that specific IP.

You are deploying an application to App Engine. You want the number of instances to scale based on request rate. You need at least 3 unoccupied instances at all times. Which scaling type should you use?

• Manual Scaling with 3 instances.

• Basic Scaling with min_instances set to 3.

• Basic Scaling with max_instances set to 3.

• Automatic Scaling with min_idle_instances set to 3.

Answer explanation

Automatic Scaling with min_idle_instances set to 3 ensures that there are always at least 3 unoccupied instances available, allowing the application to scale based on request rate while meeting the requirement.

You have a development project with appropriate IAM roles defined. You are creating a production project and want to have the same IAM roles on the new project, using the fewest possible steps. What should you do?

• Use gcloud iam roles copy and specify the production project as the destination project.

• Use gcloud iam roles copy and specify your organization as the destination organization.

• In the Google Cloud Platform Console, use the 'create role from role' functionality.

• In the Google Cloud Platform Console, use the 'create role' functionality and select all applicable permissions.

Answer explanation

Using 'gcloud iam roles copy' with the production project as the destination allows you to replicate IAM roles efficiently. This method minimizes steps compared to creating roles manually or copying to the organization level.