Deployment Manager as native IaC in GCP - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Google Cloud Deployment Manager?

Google Cloud Deployment Manager is a tool that helps you create, configure, and manage Google Cloud resources using simple text files. It lets you define your infrastructure as code, so you can deploy and update resources automatically.

beginner

How does Deployment Manager treat infrastructure?

Deployment Manager treats infrastructure as code, meaning you write configuration files that describe your resources. These files are then used to create and manage your cloud resources in a repeatable and consistent way.

intermediate

What file formats can you use with Deployment Manager?

You can use YAML, JSON, or Jinja2 templates to define your resources in Deployment Manager. YAML and JSON are simple and readable, while Jinja2 lets you add logic and reuse parts of your configuration.

beginner

What is a deployment in Deployment Manager?

A deployment is a collection of resources defined by your configuration files. When you create a deployment, Deployment Manager creates all the resources you described and keeps track of them for updates or deletion.

beginner

Why use Deployment Manager instead of manual setup?

Using Deployment Manager saves time and reduces errors by automating resource creation. It also makes your infrastructure repeatable and easy to update, just like software code.

What does Deployment Manager use to define cloud resources?

A Text configuration files

B Manual clicks in the console

C Binary executables

D Email commands

Deployment Manager uses text configuration files like YAML, JSON, or Jinja2 templates to define resources.

Which file format is NOT supported by Deployment Manager?

A XML

B Jinja2

C JSON

D YAML

Deployment Manager supports YAML, JSON, and Jinja2 templates, but XML is not supported.

What is the main benefit of using Deployment Manager?

A Manual resource creation

B Automated, repeatable infrastructure setup

C Faster internet speed

D Better email management

Deployment Manager automates and makes infrastructure setup repeatable and consistent.

What does a deployment represent in Deployment Manager?

A A single virtual machine

B A user account

C A network cable

D A collection of cloud resources

A deployment is a group of resources defined and managed together.

Which statement about Deployment Manager is TRUE?

A It requires manual updates for each resource.

B It cannot manage networks.

C It uses infrastructure as code to manage resources.

D It only works with on-premises servers.

Deployment Manager uses infrastructure as code to automate resource management.

Explain how Deployment Manager helps manage Google Cloud resources.

Think about how writing text files can replace manual setup.

Describe the role of templates in Deployment Manager.

Templates are like blueprints for your cloud setup.

Practice

1. What is the main purpose of Google Cloud Deployment Manager?

easy

A. To define and manage cloud resources using code

B. To manually create resources through the console

C. To monitor cloud resource usage in real-time

D. To provide a graphical interface for cloud billing

Solution

1. Step 1: Understand Deployment Manager's role

   Deployment Manager lets you write code to define cloud resources instead of manual setup.

2. Step 2: Compare options

   Only To define and manage cloud resources using code describes defining and managing resources using code, which matches Deployment Manager's purpose.

3. Final Answer:

   To define and manage cloud resources using code -> Option A

4. Quick Check:

   Deployment Manager = Infrastructure as Code [OK]

Hint: Deployment Manager = write code for cloud setup [OK]

Common Mistakes:

• Confusing Deployment Manager with monitoring tools
• Thinking it is a manual console tool
• Mixing it with billing or cost tools

2. Which of the following is the correct way to start a Deployment Manager YAML configuration file?

easy

A. services:

B. resources:

C. instances:

D. deployments:

Solution

1. Step 1: Recall YAML structure for Deployment Manager

   The root key to list cloud resources is resources:.

2. Step 2: Check other options

   Options like deployments:, instances:, and services: are not valid root keys in Deployment Manager YAML.

3. Final Answer:

   resources: -> Option B

4. Quick Check:

   YAML starts with resources: [OK]

Hint: Deployment Manager YAML always starts with resources: [OK]

Common Mistakes:

• Using wrong root keys like deployments or instances
• Confusing resource types with YAML structure
• Starting with service names instead of resources

3. Given this Deployment Manager snippet:

resources:
- name: my-vm
  type: compute.v1.instance
  properties:
    zone: us-central1-a
    machineType: zones/us-central1-a/machineTypes/n1-standard-1

What resource is being created?

medium

A. A network firewall rule

B. A storage bucket in us-central1-a

C. A SQL database instance

D. A virtual machine instance in zone us-central1-a

Solution

1. Step 1: Identify resource type

   The type compute.v1.instance means a virtual machine (VM) instance.

2. Step 2: Check properties

   The zone and machineType confirm it's a VM in zone us-central1-a with a standard machine type.

3. Final Answer:

   A virtual machine instance in zone us-central1-a -> Option D

4. Quick Check:

   compute.v1.instance = VM instance [OK]

Hint: compute.v1.instance means VM instance [OK]

Common Mistakes:

• Confusing instance with storage or database
• Ignoring the type field
• Assuming default zone without checking properties

4. You wrote this Deployment Manager YAML:

resources:
- name: my-vm
  type: compute.v1.instance
  properties:
    zone: us-central1-a
    machineType: n1-standard-1

Why does deployment fail?

medium

A. name property cannot be my-vm

B. zone property is invalid

C. machineType property is missing zone prefix

D. type compute.v1.instance is deprecated

Solution

1. Step 1: Check machineType format

   machineType must include full path with zone prefix like zones/us-central1-a/machineTypes/n1-standard-1.

2. Step 2: Validate other fields

   zone is valid, name is allowed, and type is current. Only machineType format is wrong.

3. Final Answer:

   machineType property is missing zone prefix -> Option C

4. Quick Check:

   machineType needs full path [OK]

Hint: machineType needs full zone path like zones/zone/machineTypes/type [OK]

Common Mistakes:

• Using short machineType without zone prefix
• Changing name to fix error
• Assuming type is deprecated

5. You want to create two VM instances in Deployment Manager using one YAML file. Which approach is best?

hard

A. List two separate resource entries under resources with different names

B. Create one resource with two names separated by commas

C. Use a loop inside YAML to repeat the resource

D. Write two separate YAML files and deploy them separately

Solution

1. Step 1: Understand YAML resource listing

   Deployment Manager YAML supports multiple resources by listing each with a unique name under resources:.

2. Step 2: Evaluate options

   List two separate resource entries under resources with different names correctly lists two resources separately. Create one resource with two names separated by commas is invalid syntax. Use a loop inside YAML to repeat the resource is not supported natively in YAML. Write two separate YAML files and deploy them separately works but is less efficient and not best practice.

3. Final Answer:

   List two separate resource entries under resources with different names -> Option A

4. Quick Check:

   Multiple resources = multiple entries [OK]

Hint: Multiple resources = multiple entries under resources: [OK]

Common Mistakes:

• Trying to name one resource with multiple names
• Expecting loops inside YAML
• Splitting into multiple files unnecessarily