Key Vault creation in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create an Azure Key Vault resource by setting the name property.

Azure

resource "azurerm_key_vault" "example" {
  location            = "eastus"
  resource_group_name = "example-rg"
  [1] = "example-vault"
}

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

Asku_name

Bresource_type

Cname

Dtenant_id

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'resource_type' instead of 'name' to set the vault name.

Confusing 'sku_name' with the vault name.

The name property sets the name of the Key Vault resource. It is required to identify the vault.

2fill in blank

medium

Complete the code to specify the SKU name for the Key Vault.

Azure

resource "azurerm_key_vault" "example" {
  name                = "example-vault"
  location            = "eastus"
  resource_group_name = "example-rg"
  sku_name            = [1]
}

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

A"premium"

B"standard"

C"basic"

D"enterprise"

Attempts:

3 left

💡 Hint

Common Mistakes

Using unsupported SKU names like 'basic' or 'enterprise'.

Forgetting to put the SKU name in quotes.

The SKU name "standard" is the common SKU for Azure Key Vaults. It defines the pricing tier.

3fill in blank

hard

Fix the error in the access policy block to correctly assign tenant ID.

Azure

resource "azurerm_key_vault" "example" {
  name                = "example-vault"
  location            = "eastus"
  resource_group_name = "example-rg"
  sku_name            = "standard"

  access_policy {
    tenant_id = [1]
    object_id = "00000000-0000-0000-0000-000000000000"
    key_permissions = ["get", "list"]
  }
}

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

Avar.tenantId

BtenantId

C"tenantId"

Dtenant_id

Attempts:

3 left

💡 Hint

Common Mistakes

Using the tenant ID as a plain string instead of a variable.

Using an undefined variable name.

The tenant ID should be referenced as a variable with var.tenantId to correctly pass its value.

4fill in blank

hard

Fill both blanks to define the network ACLs to allow access only from a specific subnet.

Azure

resource "azurerm_key_vault" "example" {
  name                = "example-vault"
  location            = "eastus"
  resource_group_name = "example-rg"
  sku_name            = "standard"

  network_acls {
    default_action = [1]
    virtual_network_subnet_ids = [[2]]
  }
}

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

A"Deny"

B"Allow"

C"subnet-12345"

D"/subscriptions/0000/resourceGroups/rg/providers/Microsoft.Network/virtualNetworks/vnet/subnets/subnet1"

Attempts:

3 left

💡 Hint

Common Mistakes

Setting default_action to 'Allow' which opens access to all.

Using subnet names instead of full resource IDs.

The default_action should be set to "Deny" to block all except allowed subnets. The virtual_network_subnet_ids must be the full resource ID of the subnet.

5fill in blank

hard

Fill all three blanks to configure Key Vault with soft delete enabled, purge protection enabled, and a proper tenant ID.

Azure

resource "azurerm_key_vault" "example" {
  name                = "example-vault"
  location            = "eastus"
  resource_group_name = "example-rg"
  sku_name            = "standard"

  tenant_id           = [1]
  soft_delete_enabled = [2]
  purge_protection_enabled = [3]
}

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

Avar.tenantId

Btrue

Cfalse

D"tenantId"

Attempts:

3 left

💡 Hint

Common Mistakes

Using string literals instead of variable for tenant ID.

Setting soft delete or purge protection to false.

The tenant_id should be referenced as var.tenantId. Both soft_delete_enabled and purge_protection_enabled should be set to true to enable these important security features.

Practice

1. What is the primary purpose of an Azure Key Vault?

easy

A. To host virtual machines

B. To manage Azure subscriptions

C. To securely store secrets, keys, and certificates

D. To monitor network traffic

Solution

1. Step 1: Understand Azure Key Vault's role

   Azure Key Vault is designed to securely store sensitive information like secrets, keys, and certificates.

2. Step 2: Compare with other Azure services

   Hosting VMs, managing subscriptions, and monitoring traffic are done by other Azure services, not Key Vault.

3. Final Answer:

   To securely store secrets, keys, and certificates -> Option C

4. Quick Check:

   Key Vault = Secure storage for secrets [OK]

Hint: Key Vault is for secrets and keys storage only [OK]

Common Mistakes:

• Confusing Key Vault with VM hosting
• Thinking Key Vault manages subscriptions
• Assuming Key Vault monitors network

2. Which Azure CLI command correctly creates a Key Vault named myVault in the resource group myResourceGroup located in eastus?

easy

A. az keyvault create --name myVault --resource-group myResourceGroup --location eastus

B. az keyvault new --vault-name myVault --group myResourceGroup --region eastus

C. az vault create --name myVault --resource-group myResourceGroup --location eastus

D. az keyvault create --vault myVault --resource myResourceGroup --location eastus

Solution

1. Step 1: Identify correct Azure CLI syntax

   The correct command uses az keyvault create with parameters --name, --resource-group, and --location.

2. Step 2: Check each option's parameters

   az keyvault create --name myVault --resource-group myResourceGroup --location eastus matches the correct syntax exactly. Options B, C, and D use incorrect commands or parameter names.

3. Final Answer:

   az keyvault create --name myVault --resource-group myResourceGroup --location eastus -> Option A

4. Quick Check:

   Correct CLI syntax = az keyvault create --name myVault --resource-group myResourceGroup --location eastus [OK]

Hint: Use 'az keyvault create' with --name and --resource-group [OK]

Common Mistakes:

• Using 'az keyvault new' instead of 'create'
• Wrong parameter names like --vault or --group
• Omitting required parameters

3. Given this Azure CLI command:

az keyvault create --name testVault --resource-group testGroup --location westus --enable-soft-delete false

What will be the state of soft delete on the created Key Vault?

medium

A. Soft delete will be enabled by default

B. Soft delete will be disabled as specified

C. Soft delete will be enabled only if the region supports it

D. Command will fail due to invalid parameter

Solution

1. Step 1: Check parameter validity

   The parameter --enable-soft-delete is deprecated and cannot be set to false; soft delete is always enabled now.

2. Step 2: Understand command behavior

   Setting --enable-soft-delete false causes the command to fail because disabling soft delete is not allowed.

3. Final Answer:

   Command will fail due to invalid parameter -> Option D

4. Quick Check:

   Soft delete cannot be disabled now = Command will fail due to invalid parameter [OK]

Hint: Soft delete is always enabled; disabling causes error [OK]

Common Mistakes:

• Assuming soft delete can be turned off
• Ignoring deprecation of --enable-soft-delete
• Thinking soft delete depends on region

4. You run this command to create a Key Vault:

az keyvault create --name vault123 --resource-group group123 --location eastus

But you get an error: ResourceGroupNotFound. What is the most likely fix?

medium

A. Change the location to westus

B. Create the resource group group123 before creating the Key Vault

C. Use a different Key Vault name

D. Add --enable-soft-delete true to the command

Solution

1. Step 1: Understand the error

   ResourceGroupNotFound means the specified resource group does not exist.

2. Step 2: Fix by creating the resource group

   You must create the resource group group123 first using az group create before creating resources inside it.

3. Final Answer:

   Create the resource group group123 before creating the Key Vault -> Option B

4. Quick Check:

   Resource group must exist before Key Vault creation [OK]

Hint: Create resource group first to avoid ResourceGroupNotFound [OK]

Common Mistakes:

• Trying to change location instead of creating group
• Changing vault name without checking group
• Adding unrelated parameters to fix error

5. You want to create an Azure Key Vault with these requirements:
- Name: secureVault
- Resource group: prodGroup
- Location: centralus
- Enable soft delete
- Set access policy to allow user with object ID 1234abcd to get and list secrets

Which Azure CLI command sequence correctly achieves this?

hard

A. az keyvault create --name secureVault --resource-group prodGroup --location centralus && az keyvault set-policy --name secureVault --object-id 1234abcd --secret-permissions get list

B. az keyvault create --name secureVault --resource-group prodGroup --location centralus --enable-soft-delete true --access-policy object-id=1234abcd permissions=secrets:get,list

C. az keyvault create --name secureVault --resource-group prodGroup --location centralus --enable-soft-delete false && az keyvault set-policy --name secureVault --object-id 1234abcd --secret-permissions get list

D. az keyvault create --name secureVault --resource-group prodGroup --location centralus && az keyvault set-policy --name secureVault --object-id 1234abcd --secret-permissions get,list

Solution

1. Step 1: Create Key Vault with default soft delete enabled

   Soft delete is enabled by default and cannot be disabled, so no need to specify it.

2. Step 2: Set access policy with correct syntax

   Use az keyvault set-policy with --object-id and --secret-permissions get list to allow the user to get and list secrets.

3. Step 3: Verify command correctness

   az keyvault create --name secureVault --resource-group prodGroup --location centralus && az keyvault set-policy --name secureVault --object-id 1234abcd --secret-permissions get list uses correct commands and parameters. az keyvault create --name secureVault --resource-group prodGroup --location centralus && az keyvault set-policy --name secureVault --object-id 1234abcd --secret-permissions get,list incorrectly uses comma between permissions. az keyvault create --name secureVault --resource-group prodGroup --location centralus --enable-soft-delete true --access-policy object-id=1234abcd permissions=secrets:get,list uses invalid parameters. az keyvault create --name secureVault --resource-group prodGroup --location centralus --enable-soft-delete false && az keyvault set-policy --name secureVault --object-id 1234abcd --secret-permissions get list tries to disable soft delete, which is invalid.

4. Final Answer:

   az keyvault create --name secureVault --resource-group prodGroup --location centralus && az keyvault set-policy --name secureVault --object-id 1234abcd --secret-permissions get list -> Option A

5. Quick Check:

   Create then set-policy with correct permissions = az keyvault create --name secureVault --resource-group prodGroup --location centralus && az keyvault set-policy --name secureVault --object-id 1234abcd --secret-permissions get list [OK]

Hint: Create vault first, then set access policy with correct permissions [OK]

Common Mistakes:

• Trying to disable soft delete
• Using wrong parameter names for access policy
• Combining all settings in one invalid command