Azure Cache for Redis - Mini Project: Build & Apply

Create and Configure Azure Cache for Redis

📖 Scenario: You are setting up a fast, in-memory data store to improve the performance of a web application. Azure Cache for Redis will help by storing frequently accessed data close to your app.

🎯 Goal: Build an Azure Cache for Redis instance with basic configuration and enable non-SSL port for local testing.

📋 What You'll Learn

Create an Azure Cache for Redis resource with the name myRedisCache

Set the resource location to East US

Use the Basic pricing tier with C0 size

Enable the non-SSL port for local testing

💡 Why This Matters

🌍 Real World

Azure Cache for Redis is used to speed up applications by caching data close to the app, reducing delays and load on databases.

💼 Career

Cloud engineers and developers often create and configure Redis caches to improve app performance and scalability.

1

Create the Azure Cache for Redis resource

Write an Azure Resource Manager (ARM) template snippet to create an Azure Cache for Redis resource named myRedisCache in the East US location.

Azure

{
  "type": "Microsoft.Cache/Redis",
  "apiVersion": "2023-04-01",
  "name": "myRedisCache",
  "location": "East US",
  "properties": {
  }
}
# Your code here

Hint

Use the type property as Microsoft.Cache/Redis and set name and location exactly as specified.

2

Add pricing tier configuration

Add the sku property to the Azure Cache for Redis resource with name set to Basic and family set to C and capacity set to 0.

Azure

{
  "type": "Microsoft.Cache/Redis",
  "apiVersion": "2023-04-01",
  "name": "myRedisCache",
  "location": "East US",
  "sku": {
  },
  "properties": {
  }
}
# Your code here

Hint

The sku property defines the pricing tier. Use Basic for name, C for family, and 0 for capacity.

3

Enable non-SSL port

Inside the properties object, add the property enableNonSslPort and set it to true to allow non-SSL connections for local testing.

Azure

{
  "type": "Microsoft.Cache/Redis",
  "apiVersion": "2023-04-01",
  "name": "myRedisCache",
  "location": "East US",
  "sku": {
    "name": "Basic",
    "family": "C",
    "capacity": 0
  },
  "properties": {
    
  }
}
# Your code here

Hint

Set enableNonSslPort inside properties to true to allow non-SSL connections.

4

Complete the ARM template with resource declaration

Wrap the Redis resource definition inside a resources array and add the type and apiVersion at the root level to form a valid ARM template snippet.

Azure

{
  "resources": [
    {
      "type": "Microsoft.Cache/Redis",
      "apiVersion": "2023-04-01",
      "name": "myRedisCache",
      "location": "East US",
      "sku": {
        "name": "Basic",
        "family": "C",
        "capacity": 0
      },
      "properties": {
        "enableNonSslPort": true
      }
    }
  ]
}
# Your code here

Hint

Wrap the Redis resource inside a resources array to complete the ARM template.

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