Azure Cache for Redis - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create an Azure Cache for Redis instance with the correct SKU.

Azure

az redis create --name myCache --resource-group myResourceGroup --location eastus --sku [1]

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

APremium

BFree

CBasic

DStandard

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Free' which is not a valid SKU for Azure Cache for Redis.

Confusing SKU names with other Azure services.

The Basic SKU is a valid SKU for Azure Cache for Redis and is commonly used for development and testing.

2fill in blank

medium

Complete the code to enable non-SSL port access on the Redis cache.

Azure

az redis update --name myCache --resource-group myResourceGroup --enable-non-ssl-port [1]

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

Ayes

Bfalse

Cenable

Dtrue

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'enable' or 'yes' which are invalid boolean values.

Setting the flag to 'false' when intending to enable non-SSL port.

Setting --enable-non-ssl-port true allows access to the Redis cache over non-SSL port.

3fill in blank

hard

Fix the error in the command to scale the Redis cache to a higher capacity.

Azure

az redis update --name myCache --resource-group myResourceGroup --sku [1] --vm-size C2

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

APremium

BStandard

CBasic

DFree

Attempts:

3 left

💡 Hint

Common Mistakes

Using Basic or Standard SKU with VM size C2 causes errors.

Using 'Free' SKU which is invalid.

The Premium SKU supports scaling with VM sizes like C2. Basic and Standard SKUs do not support this VM size.

4fill in blank

hard

Fill both blanks to configure a Redis cache with a specific Redis version and enable clustering.

Azure

az redis create --name myCache --resource-group myResourceGroup --location eastus --sku Premium --redis-version [1] --enable-cluster [2]

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

A6

Btrue

Cfalse

D5

Attempts:

3 left

💡 Hint

Common Mistakes

Using Redis version 5 which may not support clustering.

Setting clustering flag to false when intending to enable it.

Redis version 6 is a supported version and enabling clustering requires setting --enable-cluster true.

5fill in blank

hard

Fill all three blanks to create a Redis cache with a custom subnet, static IP, and enable non-SSL port.

Azure

az redis create --name myCache --resource-group myResourceGroup --location eastus --sku Premium --subnet-id [1] --static-ip [2] --enable-non-ssl-port [3]

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

A/subscriptions/12345/resourceGroups/myResourceGroup/providers/Microsoft.Network/virtualNetworks/myVnet/subnets/mySubnet

B10.0.0.5

Ctrue

Dfalse

Attempts:

3 left

💡 Hint

Common Mistakes

Using an invalid subnet ID format.

Assigning a static IP outside the subnet range.

Setting enable-non-ssl-port to false when intending to enable it.

To configure a Redis cache in a custom subnet, provide the subnet resource ID, assign a static IP within that subnet, and enable the non-SSL port by setting it to true.

Practice

1. What is the main purpose of Azure Cache for Redis?

easy

A. To permanently store large files

B. To host virtual machines

C. To replace Azure SQL Database

D. To store data in memory to speed up applications

Solution

1. Step 1: Understand Azure Cache for Redis function

   Azure Cache for Redis stores data in memory, which is much faster than disk storage.

2. Step 2: Identify the main benefit

   This in-memory storage helps speed up applications by reducing the time to access data.

3. Final Answer:

   To store data in memory to speed up applications -> Option D

4. Quick Check:

   In-memory cache = speed up apps [OK]

Hint: Remember: Redis cache is for fast memory storage [OK]

Common Mistakes:

• Thinking Redis stores large files permanently
• Confusing Redis with database replacement
• Assuming Redis hosts virtual machines

2. Which property sets the pricing tier when creating an Azure Cache for Redis instance?

easy

A. sku_name

B. resource_group

C. location

D. capacity

Solution

1. Step 1: Identify pricing tier property

   The pricing tier is controlled by the SKU name, which defines features and cost.

2. Step 2: Differentiate from other properties

   Capacity sets size, location sets region, resource group organizes resources.

3. Final Answer:

   sku_name -> Option A

4. Quick Check:

   Pricing tier = sku_name [OK]

Hint: Pricing tier is set by sku_name, not capacity [OK]

Common Mistakes:

• Confusing capacity with pricing tier
• Using location or resource group as pricing tier
• Mixing sku_name with capacity

3. Given this snippet to create Azure Cache for Redis in ARM template:

{
  "type": "Microsoft.Cache/Redis",
  "name": "myRedisCache",
  "apiVersion": "2023-04-01",
  "location": "eastus",
  "properties": {
    "sku": { "name": "Standard", "family": "C", "capacity": 2 },
    "enableNonSslPort": false
  }
}

What does setting enableNonSslPort to false do?

medium

A. Disables the non-SSL port, forcing SSL connections

B. Enables non-SSL port for faster connections

C. Sets the cache size to 2 GB

D. Changes the cache location to westus

Solution

1. Step 1: Understand enableNonSslPort property

   This property controls if clients can connect without SSL (non-secure).

2. Step 2: Interpret false value

   Setting it to false disables non-SSL port, so only secure SSL connections are allowed.

3. Final Answer:

   Disables the non-SSL port, forcing SSL connections -> Option A

4. Quick Check:

   enableNonSslPort false = SSL only [OK]

Hint: False disables non-SSL port, secure only [OK]

Common Mistakes:

• Thinking false enables non-SSL port
• Confusing capacity with enableNonSslPort
• Assuming location changes with this property

4. You try to create an Azure Cache for Redis with this JSON snippet:

{
  "type": "Microsoft.Cache/Redis",
  "name": "cache1",
  "apiVersion": "2023-04-01",
  "location": "eastus",
  "properties": {
    "sku": { "name": "Standard", "family": "C", "capacity": 0 },
    "enableNonSslPort": true
  }
}

What is the problem with this configuration?

medium

A. enableNonSslPort cannot be true for Basic SKU

B. Capacity cannot be zero; it must be at least 1

C. Location eastus is invalid

D. Missing resource group property

Solution

1. Step 1: Check capacity value

   Capacity defines cache size and must be a positive integer starting at 1.

2. Step 2: Validate other properties

   enableNonSslPort can be true, eastus is valid location, resource group is set outside this snippet.

3. Final Answer:

   Capacity cannot be zero; it must be at least 1 -> Option B

4. Quick Check:

   Capacity ≥ 1 required [OK]

Hint: Capacity must be 1 or more, zero is invalid [OK]

Common Mistakes:

• Assuming zero capacity is allowed
• Thinking enableNonSslPort is restricted by SKU
• Confusing location validity

5. You want to reduce database load by caching user session data using Azure Cache for Redis. Which combination of settings is best to ensure fast response and cost efficiency?

hard

A. Use Basic SKU with capacity 10 and enableNonSslPort false

B. Use Premium SKU with capacity 5 and enableNonSslPort true

C. Use Standard SKU with capacity 3 and enableNonSslPort false

D. Use Standard SKU with capacity 1 and enableNonSslPort false

Solution

1. Step 1: Balance performance and cost

   Standard SKU offers good performance at moderate cost; capacity 3 provides enough memory for sessions without overspending.

2. Step 2: Ensure secure connections

   Disabling non-SSL port (false) ensures secure data transfer, important for user sessions.

3. Step 3: Evaluate other options

   Basic SKU with high capacity is less performant; Premium SKU with high capacity is costly; enabling non-SSL port reduces security.

4. Final Answer:

   Use Standard SKU with capacity 3 and enableNonSslPort false -> Option C

5. Quick Check:

   Standard SKU + moderate capacity + secure port = best balance [OK]

Hint: Pick Standard SKU, moderate size, secure port for best balance [OK]

Common Mistakes:

• Choosing too large capacity increasing cost
• Using Basic SKU for heavy session caching
• Enabling non-SSL port reducing security