Deployment Manager as native IaC in GCP - Time & Space Complexity

Time Complexity: Deployment Manager as native IaC

O(n)

Understanding Time Complexity

When using Deployment Manager to create cloud resources, it's important to know how the time to deploy grows as you add more resources.

We want to understand how the number of resources affects the deployment time and API calls.

Scenario Under Consideration

Analyze the time complexity of deploying multiple resources using Deployment Manager.

resources:
- name: vm-instance-1
  type: compute.v1.instance
  properties:
    zone: us-central1-a
    machineType: zones/us-central1-a/machineTypes/n1-standard-1
- name: vm-instance-2
  type: compute.v1.instance
  properties:
    zone: us-central1-a
    machineType: zones/us-central1-a/machineTypes/n1-standard-1
# ... repeated for n instances

This configuration creates multiple virtual machine instances, each defined as a separate resource.

Identify Repeating Operations

Identify the API calls, resource provisioning, data transfers that repeat.

• Primary operation: Creating each VM instance via the Compute Engine API.
• How many times: Once per resource, so n times for n instances.

How Execution Grows With Input

Each additional resource adds one more API call to create it, so the total work grows directly with the number of resources.

Input Size (n)	Approx. API Calls/Operations
10	10
100	100
1000	1000

Pattern observation: The number of API calls grows linearly as you add more resources.

Final Time Complexity

Time Complexity: O(n)

This means the deployment time grows in direct proportion to the number of resources you define.

Common Mistake

[X] Wrong: "Adding more resources won't affect deployment time much because Deployment Manager handles everything at once."

[OK] Correct: Each resource requires its own API call and provisioning, so more resources mean more work and longer deployment time.

Interview Connect

Understanding how deployment time scales with resource count helps you design efficient infrastructure and explain trade-offs clearly in real projects.

Self-Check

"What if Deployment Manager supported batching multiple resource creations in a single API call? How would the time complexity change?"

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