Performance efficiency pillar in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create an Azure Virtual Machine with the Standard_DS1_v2 size for better performance.

Azure

az vm create --resource-group myResourceGroup --name myVM --image UbuntuLTS --size [1]

Drag options to blanks, or click blank then click option'

ABasic_A0

BStandard_B1s

CStandard_DS1_v2

DStandard_F1

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing a basic or burstable VM size that limits performance.

Using a VM size not supported in the region.

The Standard_DS1_v2 size provides a balanced CPU-to-memory ratio suitable for performance efficiency.

2fill in blank

medium

Complete the code to enable Azure Monitor autoscale for a VM scale set to improve performance efficiency.

Azure

az monitor autoscale create --resource-group myResourceGroup --resource myScaleSet --resource-type Microsoft.Compute/virtualMachineScaleSets --name autoscaleSetting --min-count 1 --max-count [1] --count 2

Drag options to blanks, or click blank then click option'

A10

B5

C0

D1

Attempts:

3 left

💡 Hint

Common Mistakes

Setting max-count less than or equal to min-count disables scaling out.

Setting max-count to zero disables scaling.

Setting max-count to 5 allows the scale set to increase instances to handle load spikes, improving performance.

3fill in blank

hard

Fix the error in the Azure CLI command to create a performance-optimized storage account with Premium SSD.

Azure

az storage account create --name mystorageacct --resource-group myResourceGroup --sku [1] --kind StorageV2

Drag options to blanks, or click blank then click option'

ABasic_LRS

BStandard_LRS

CStandard_GRS

DPremium_LRS

Attempts:

3 left

💡 Hint

Common Mistakes

Using Standard SKUs which do not provide premium performance.

Using Basic SKU which is not valid for StorageV2.

The Premium_LRS SKU provides high-performance SSD storage suitable for performance efficiency.

4fill in blank

hard

Fill both blanks to configure an Azure SQL Database with the correct performance tier and compute size.

Azure

az sql db create --resource-group myResourceGroup --server myServer --name myDatabase --service-objective [1] --compute-model [2]

Drag options to blanks, or click blank then click option'

AGP_Gen5_2

BBasic

CProvisioned

DServerless

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing Basic tier which has limited performance.

Using Serverless compute which may have variable performance.

GP_Gen5_2 is a General Purpose tier with 2 vCores for performance. Provisioned compute model allocates fixed resources for consistent performance.

5fill in blank

hard

Fill all three blanks to create an Azure App Service plan optimized for performance with the correct SKU, tier, and number of instances.

Azure

az appservice plan create --name myAppServicePlan --resource-group myResourceGroup --sku [1] --is-linux true --number-of-workers [2] --tier [3]

Drag options to blanks, or click blank then click option'

AP1v3

B3

CPremiumV3

DB1

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing Basic SKU or tier which limits performance.

Setting number of workers to 1 which limits scaling.

P1v3 SKU in the PremiumV3 tier provides high performance. Setting number-of-workers to 3 allows scaling out to handle more load.

Practice

1. What is the main goal of the Performance efficiency pillar in Azure cloud architecture?

easy

A. To secure data and prevent unauthorized access

B. To ensure applications run fast and scale smoothly

C. To reduce the cost of cloud resources only

D. To create backups and disaster recovery plans

Solution

1. Step 1: Understand the purpose of the performance efficiency pillar

   This pillar focuses on making sure cloud applications perform well and can handle changes in demand.

2. Step 2: Compare with other pillars

   Security and cost management are different pillars, so they are not the main goal here.

3. Final Answer:

   To ensure applications run fast and scale smoothly -> Option B

4. Quick Check:

   Performance efficiency = fast, scalable apps [OK]

Hint: Performance efficiency means fast and scalable apps [OK]

Common Mistakes:

• Confusing performance with security
• Thinking cost saving is the only goal
• Mixing backup with performance

2. Which Azure service helps automatically adjust resources to meet demand under the Performance efficiency pillar?

easy

A. Azure Autoscale

B. Azure Security Center

C. Azure Monitor

D. Azure Backup

Solution

1. Step 1: Identify autoscaling service in Azure

   Azure Autoscale automatically adds or removes resources based on demand.

2. Step 2: Differentiate from monitoring and security

   Azure Monitor tracks performance but does not adjust resources; Security Center protects security; Backup handles data copies.

3. Final Answer:

   Azure Autoscale -> Option A

4. Quick Check:

   Autoscale adjusts resources automatically [OK]

Hint: Autoscale means automatic resource adjustment [OK]

Common Mistakes:

• Confusing monitoring with autoscaling
• Choosing security or backup services
• Not knowing autoscale exists

3. Consider this Azure setup: An app uses Azure Cache for Redis to store frequent data. What is the expected effect on performance?

medium

A. Faster response times by reducing database load

B. Increased cost with no performance benefit

C. No change in performance

D. Slower response times due to extra caching layer

Solution

1. Step 1: Understand caching role

   Caching stores frequent data closer to the app, reducing database queries.

2. Step 2: Effect on performance

   Less database load means faster responses and better scalability.

3. Final Answer:

   Faster response times by reducing database load -> Option A

4. Quick Check:

   Caching improves speed by reducing database hits [OK]

Hint: Cache reduces database load, speeding responses [OK]

Common Mistakes:

• Thinking cache slows down app
• Assuming no performance change
• Ignoring cost vs benefit

4. You configured Azure Autoscale but notice your app still slows down during peak hours. What is a likely cause?

medium

A. Azure Backup is running during peak hours

B. Azure Monitor is disabled

C. Autoscale rules are not set correctly for CPU or memory thresholds

D. The app is using Azure Security Center

Solution

1. Step 1: Check autoscale configuration

   If autoscale rules do not trigger at correct CPU or memory levels, scaling won't happen on time.

2. Step 2: Rule out unrelated services

   Monitor tracks metrics but does not scale; Backup and Security Center do not affect autoscale directly.

3. Final Answer:

   Autoscale rules are not set correctly for CPU or memory thresholds -> Option C

4. Quick Check:

   Incorrect autoscale rules cause slow app under load [OK]

Hint: Check autoscale thresholds if app slows at peak [OK]

Common Mistakes:

• Blaming monitoring or backup services
• Ignoring autoscale rule settings
• Assuming security affects performance scaling

5. You want to design an Azure app that handles unpredictable traffic spikes efficiently. Which combination best follows the Performance efficiency pillar?

hard

A. Deploy multiple apps without scaling or caching

B. Use fixed VM sizes and manual scaling

C. Use Azure Backup and Security Center only

D. Use Azure Autoscale with Azure Cache for Redis and monitor with Azure Monitor

Solution

1. Step 1: Identify autoscaling for unpredictable traffic

   Azure Autoscale adjusts resources automatically to meet demand spikes.

2. Step 2: Add caching and monitoring

   Azure Cache for Redis speeds data access; Azure Monitor tracks performance to optimize scaling.

3. Step 3: Eliminate unsuitable options

   Fixed VMs and manual scaling can't handle spikes well; Backup and Security Center don't improve performance; no scaling or caching causes slowdowns.

4. Final Answer:

   Use Azure Autoscale with Azure Cache for Redis and monitor with Azure Monitor -> Option D

5. Quick Check:

   Autoscale + cache + monitor = efficient scaling [OK]

Hint: Combine autoscale, cache, and monitor for best performance [OK]

Common Mistakes:

• Choosing manual scaling for spikes
• Ignoring caching benefits
• Confusing backup/security with performance