Azure CLI and Cloud Shell - Time & Space Complexity

Time Complexity: Azure CLI and Cloud Shell

O(n)

Understanding Time Complexity

We want to understand how the time to run Azure CLI commands in Cloud Shell changes as we do more work.

Specifically, how does adding more commands or resources affect the total time?

Scenario Under Consideration

Analyze the time complexity of running multiple Azure CLI commands in Cloud Shell.

az group create --name MyResourceGroup --location eastus
az vm create --resource-group MyResourceGroup --name MyVM1 --image UbuntuLTS
az vm create --resource-group MyResourceGroup --name MyVM2 --image UbuntuLTS
az vm create --resource-group MyResourceGroup --name MyVM3 --image UbuntuLTS

This sequence creates a resource group and then creates three virtual machines inside it.

Identify Repeating Operations

Look at what happens multiple times:

• Primary operation: Creating a virtual machine with az vm create.
• How many times: Once per VM, here 3 times.

How Execution Grows With Input

Each VM creation takes roughly the same time, so total time grows as we add more VMs.

Input Size (n)	Approx. API Calls/Operations
10	10 VM create commands + 1 group create
100	100 VM create commands + 1 group create
1000	1000 VM create commands + 1 group create

Pattern observation: The total operations increase directly with the number of VMs created.

Final Time Complexity

Time Complexity: O(n)

This means the time grows in a straight line as you add more virtual machines to create.

Common Mistake

[X] Wrong: "Running many VM create commands in Cloud Shell takes the same time as running one."

[OK] Correct: Each VM creation is a separate operation that takes time, so total time adds up as you create more VMs.

Interview Connect

Understanding how command sequences scale helps you plan and explain cloud automation tasks clearly and confidently.

Self-Check

"What if we ran VM creation commands in parallel instead of one after another? How would the time complexity change?"

Practice

1. What is the primary purpose of Azure Cloud Shell?

easy

A. To store files permanently in Azure storage

B. To create virtual machines automatically without commands

C. To replace the Azure Portal with a graphical interface

D. To provide a ready-to-use command line interface in the browser with Azure CLI pre-installed

Solution

1. Step 1: Understand Cloud Shell functionality

   Cloud Shell is a browser-based shell environment with Azure CLI and other tools pre-installed, ready for use without setup.

2. Step 2: Compare options

   Options B, C, and D describe other Azure features but not Cloud Shell's main purpose.

3. Final Answer:

   To provide a ready-to-use command line interface in the browser with Azure CLI pre-installed -> Option D

4. Quick Check:

   Cloud Shell = browser CLI with Azure CLI [OK]

Hint: Cloud Shell = browser command line ready to use [OK]

Common Mistakes:

• Thinking Cloud Shell is a GUI tool
• Confusing Cloud Shell with Azure Portal
• Assuming Cloud Shell stores files permanently

2. Which command correctly logs you into Azure CLI in Cloud Shell?

easy

A. az connect

B. az login

C. az start

D. az authenticate

Solution

1. Step 1: Identify the login command in Azure CLI

   The command to log in to Azure CLI is az login.

2. Step 2: Verify other options

   Commands like az connect, az start, and az authenticate do not exist or are incorrect for login.

3. Final Answer:

   az login -> Option B

4. Quick Check:

   Login command = az login [OK]

Hint: Login always uses 'az login' command [OK]

Common Mistakes:

• Using 'az connect' instead of 'az login'
• Trying 'az start' to login
• Assuming 'az authenticate' is valid

3. What will the following command do?

az group create --name MyResourceGroup --location eastus

medium

A. Create a new resource group named MyResourceGroup in the East US region

B. Delete the resource group named MyResourceGroup

C. List all resource groups in East US

D. Create a virtual machine named MyResourceGroup

Solution

1. Step 1: Understand the command structure

   az group create creates a resource group. The parameters specify the name and location.

2. Step 2: Interpret parameters

   --name sets the resource group name to 'MyResourceGroup', --location sets the region to 'eastus'.

3. Final Answer:

   Create a new resource group named MyResourceGroup in the East US region -> Option A

4. Quick Check:

   az group create = create resource group [OK]

Hint: az group create = make new resource group [OK]

Common Mistakes:

• Confusing resource group creation with VM creation
• Thinking it deletes or lists groups
• Misunderstanding --location parameter

4. You run this command in Cloud Shell:

az vm create --resource-group MyGroup --name MyVM --image UbuntuLTS

But get an error saying the resource group does not exist. What should you do?

medium

A. Create the resource group first using az group create

B. Change the VM name to match an existing resource group

C. Run az vm delete before creating the VM

D. Use az vm list to create the resource group

Solution

1. Step 1: Understand the error cause

   The error says the resource group 'MyGroup' does not exist, so the VM cannot be created there.

2. Step 2: Fix by creating the resource group

   You must create the resource group first with az group create --name MyGroup --location eastus (or another location).

3. Final Answer:

   Create the resource group first using az group create -> Option A

4. Quick Check:

   Resource group must exist before VM creation [OK]

Hint: Create resource group before VM creation [OK]

Common Mistakes:

• Trying to delete VM before creating resource group
• Changing VM name instead of resource group
• Using az vm list to create groups

5. You want to automate creating a VM and then immediately open its public IP in your browser using Azure CLI in Cloud Shell. Which sequence of commands is correct?

hard

A. az vm create --resource-group RG --name VM1 --image UbuntuLTS && az vm get-ip VM1 | open-browser

B. az vm create --resource-group RG --name VM1 --image UbuntuLTS; az vm list-ip --name VM1 | open

C. az vm create --resource-group RG --name VM1 --image UbuntuLTS && az vm show --resource-group RG --name VM1 --query publicIpAddress -o tsv | xargs xdg-open

D. az vm create --resource-group RG --name VM1 --image UbuntuLTS && az vm show --resource-group RG --name VM1 --query publicIpAddress -o tsv | xargs open

Solution

1. Step 1: Create VM with az vm create

   This command creates the VM in the specified resource group with the Ubuntu image.

2. Step 2: Retrieve public IP and open in browser

   az vm show --query publicIpAddress -o tsv extracts the IP. Piping to xdg-open opens it in the default browser on Linux-based Cloud Shell.

3. Step 3: Analyze options

   Options B and C use invalid commands or syntax. az vm create --resource-group RG --name VM1 --image UbuntuLTS && az vm show --resource-group RG --name VM1 --query publicIpAddress -o tsv | xargs open uses open which is MacOS-specific, not Cloud Shell.

4. Final Answer:

   az vm create ... && az vm show ... | xargs xdg-open -> Option C

5. Quick Check:

   Use az vm show + xdg-open in Cloud Shell [OK]

Hint: Use az vm show + xdg-open to open IP in Cloud Shell [OK]

Common Mistakes:

• Using MacOS 'open' command in Cloud Shell
• Using non-existent commands like az vm get-ip
• Not piping IP correctly to open command