Test 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

We recommend collecting users with the same responsibilities into groups and assigning IAM roles to the groups rather than to individual users. For example, you can create a "data scientist" group and assign appropriate roles to enable interaction with BigQuery and Cloud Storage. When a new data scientist joins your team, you can simply add them to the group and they will inherit the defined permissions. You can create and manage groups through the Admin Console. https://cloud.google.com/compute/docs/instances/managing-instance-access

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

Use 10.0.0.0/8 CIDR range. is the right answer. The private network range is defined by IETF (Ref: https://tools.ietf.org/html/rfc1918) and adhered to by all cloud providers. The supported internal IP Address ranges are 1. 24-bit block 10.0.0.0/8 (16777216 IP Addresses) 2. 20-bit block 172.16.0.0/12 (1048576 IP Addresses) 3. 16-bit block 192.168.0.0/16 (65536 IP Addresses) 10.0.0.0/8 gives you the most extensive range - 16777216 IP Addresses.

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

You must enable binary logging to use point-in-time recovery. Enabling binary logging causes a slight reduction in write performance. https://cloud.google.com/sql/docs/mysql/backup-recovery/backups

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

Use separate health checks for load balancing and for autohealing. Health checks for load balancing detect unresponsive instances and direct traffic away from them. Health checks for autohealing detect and recreate failed instances, so they should be less aggressive than load balancing health checks. Using the same health check for these services would remove the distinction between unresponsive instances and failed instances, causing unnecessary latency and unavailability for your users. https://cloud.google.com/compute/docs/tutorials/high-availability-autohealing

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

Use kubectl config get-contexts to review the output : shows the clusters and the configurations and based on the output we can identify the inactive configurations https://medium.com/google-cloud/kubernetes-engine-kubectl-config-b6270d2b656c

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 is a new Cloud Storage class designed for long-term archival and disaster recovery. Coldline is perfect for the archival needs of big data or multimedia content, allowing businesses to archive years of data. Coldline provides fast and instant (millisecond) access to data and changes the way that companies think about storing and accessing their cold data. https://cloud.google.com/blog/products/gcp/introducing-coldline-and-a-unified-platform-for-data-storage

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

The link between projects and billing accounts is preserved, irrespective of the hierarchy. When you move your existing projects into the organization they will continue to work and be billed as they used to before the migration, even if the corresponding billing account has not been migrated yet. Moving projects under an organisation doesn't change their linked billing project. https://cloud.google.com/resource-manager/docs/migrating-projects-billing

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

IP 10.0.3.21 is internal by default, and to ensure that it will be static non-changing it should be selected as static internal IP address. https://cloud.google.com/vpc/docs/subnets#valid-ranges

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

App Engine calculates the number of instances necessary to serve your current application traffic based on scaling settings such as target_cpu_utilization and target_throughput_utilization. Setting min_idle_instances specifies the number of instances to run in addition to this calculated number. For example, if App Engine calculates that 5 instances are necessary to serve traffic, and min_idle_instances is set to 2, App Engine will run 7 instances (5, calculated based on traffic, plus 2 additional per min_idle_instances)

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

This command creates a role from an existing role https://cloud.google.com/sdk/gcloud/reference/iam/roles/copy