Beginner Google Cloud test (Beginner)

Sample questions

5 sample questions from the Beginner Google Cloud test, with the answers. Samples are taken out of the live test, so you will not meet these when you sit it.

1. What is the primary purpose of Google Cloud projects?

   1. Google Cloud projects are only used for storing data and have no relation to billing or access control.
   2. Google Cloud projects are temporary and automatically deleted after a certain period.
   3. Google Cloud projects are used to organize and manage resources, billing, and access control within Google Cloud.
   4. Google Cloud projects are only used for compute resources and cannot be used for storage or networking.

   Answer: C. Google Cloud projects are used to organize and manage resources, billing, and access control within Google Cloud.

   Google Cloud projects serve as containers for organizing resources, managing billing, and controlling access. Other options may describe features of projects but do not accurately define their primary purpose.

2. Which statement accurately describes the requirements for creating a Compute Engine instance in a realistic project scenario?

   1. Compute Engine instance creation requires specifying a machine type, boot disk, and network configuration.
   2. Only the network configuration is necessary for creating a Compute Engine instance.
   3. Compute Engine instances automatically assign machine types and boot disks.
   4. Compute Engine instances can be created without defining a machine type or boot disk.

   Answer: A. Compute Engine instance creation requires specifying a machine type, boot disk, and network configuration.

   When creating a Compute Engine instance, specifying a machine type, boot disk, and network configuration is mandatory as these are fundamental components required to launch an instance. Other options may be optional or incorrect based on the context of the question.

3. What is a common mistake or tricky edge case when setting up a persistent disk in Compute Engine?

   1. The persistent disk is not automatically deleted when the instance is terminated.
   2. The persistent disk is not associated with any specific region.
   3. The persistent disk is automatically deleted when the project is deleted.
   4. The persistent disk is automatically deleted when the instance is terminated.

   Answer: A. The persistent disk is not automatically deleted when the instance is terminated.

   A common mistake when working with persistent disks in Compute Engine is assuming that the disk is automatically deleted when the instance is terminated. In reality, the persistent disk remains attached to the project and must be manually deleted to avoid ongoing charges. The other options describe behaviors that are either incorrect or unrelated to the persistent disk setup edge case.

4. Which of the following statements best describes a project in Google Cloud?

   1. A project is the top-level resource in Google Cloud and serves as a container for all other resources.
   2. A project is a security group that manages access to all resources in Google Cloud.
   3. A project is a collection of regions and zones used for resource deployment.
   4. A project is a billing account linked to multiple organizations.

   Answer: A. A project is the top-level resource in Google Cloud and serves as a container for all other resources.

   A project is indeed the top-level resource in Google Cloud and serves as a container for all other resources. This is a fundamental concept in the structure of Google Cloud resources. The other options refer to incorrect definitions or are not directly related to the concept of a project in Google Cloud.

5. Which of the following is a common mistake or edge case when configuring Compute Engine auto-scaling?

   1. Auto-scaling cannot be applied to instance groups that use custom machine types.
   2. Auto-scaling cannot be applied to instance groups that use predefined machine types.
   3. Auto-scaling is not supported for instance groups with a minimum size of 1.
   4. Auto-scaling is not supported for instance groups with a maximum size of 100.

   Answer: A. Auto-scaling cannot be applied to instance groups that use custom machine types.

   Compute Engine auto-scaling can be applied to managed instance groups, but it has limitations. One common mistake is assuming that auto-scaling works with all instance types. Auto-scaling is not supported for instance groups that use custom machine types, as they are not compatible with the autoscaling policies and metrics used by Compute Engine.