Private endpoints concept in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a private endpoint resource in Azure.

Azure

resource "azurerm_private_endpoint" "example" {
  name                = "example-private-endpoint"
  location            = azurerm_resource_group.example.location
  resource_group_name = azurerm_resource_group.example.name
  subnet_id           = [1]
}

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

Aazurerm_subnet.example.id

Bazurerm_resource_group.example.id

Cazurerm_virtual_network.example.id

Dazurerm_network_interface.example.id

Attempts:

3 left

💡 Hint

Common Mistakes

Using virtual network ID instead of subnet ID

Using resource group ID instead of subnet ID

The subnet_id property must reference the subnet resource ID where the private endpoint will be placed.

2fill in blank

medium

Complete the code to specify the private service connection for the private endpoint.

Azure

private_service_connection {
  name                           = "example-psc"
  private_connection_resource_id = [1]
  is_manual_connection           = false
  subresource_names              = ["blob"]
}

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

Aazurerm_subnet.example.id

Bazurerm_virtual_network.example.id

Cazurerm_storage_account.example.id

Dazurerm_resource_group.example.id

Attempts:

3 left

💡 Hint

Common Mistakes

Using subnet or virtual network ID instead of the target resource ID

Using resource group ID instead of the target resource ID

The private_connection_resource_id must point to the resource you want to connect privately, such as a storage account.

3fill in blank

hard

Fix the error in the private endpoint configuration by completing the missing property.

Azure

resource "azurerm_private_endpoint" "example" {
  name                = "example-private-endpoint"
  location            = azurerm_resource_group.example.location
  resource_group_name = azurerm_resource_group.example.name
  subnet_id           = azurerm_subnet.example.id
  [1] {
    name                           = "example-psc"
    private_connection_resource_id = azurerm_storage_account.example.id
    is_manual_connection           = false
    subresource_names              = ["blob"]
  }
}

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

Aprivate_link_service_connection

Bprivate_service_connection

Cservice_endpoint

Dnetwork_interface

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect block names like service_endpoint

Confusing private link service with private service connection

The block defining the connection to the private resource must be named private_service_connection.

4fill in blank

hard

Fill both blanks to create a private DNS zone link for the private endpoint.

Azure

resource "azurerm_private_dns_zone_virtual_network_link" "example" {
  name                  = "example-link"
  resource_group_name   = azurerm_resource_group.example.name
  private_dns_zone_name = [1]
  virtual_network_id    = [2]
  registration_enabled  = false
}

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

A"privatelink.blob.core.windows.net"

Bazurerm_virtual_network.example.id

Cazurerm_subnet.example.id

D"privatelink.database.windows.net"

Attempts:

3 left

💡 Hint

Common Mistakes

Using subnet ID instead of virtual network ID

Using wrong DNS zone name for the service

The private_dns_zone_name must be the correct private DNS zone for the service, and virtual_network_id must be the virtual network's ID.

5fill in blank

hard

Fill all three blanks to define a private endpoint with tags and manual approval.

Azure

resource "azurerm_private_endpoint" "example" {
  name                = "example-private-endpoint"
  location            = azurerm_resource_group.example.location
  resource_group_name = azurerm_resource_group.example.name
  subnet_id           = [1]
  tags = {
    environment = [2]
  }
  private_service_connection {
    name                           = "example-psc"
    private_connection_resource_id = [3]
    is_manual_connection           = true
    subresource_names              = ["sqlServer"]
  }
}

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

Aazurerm_subnet.example.id

B"production"

Cazurerm_sql_server.example.id

Dazurerm_virtual_network.example.id

Attempts:

3 left

💡 Hint

Common Mistakes

Using virtual network ID instead of subnet ID

Not quoting the tag value

Using wrong resource ID for private connection

The subnet_id must be the subnet's ID, the tag value is a string for environment, and the private_connection_resource_id is the SQL server's ID.

Practice

1. What is the main purpose of an Azure Private Endpoint?

easy

A. To make Azure services publicly accessible over the internet

B. To increase the speed of internet browsing

C. To connect to Azure services privately within your network

D. To create virtual machines automatically

Solution

1. Step 1: Understand what a Private Endpoint does

   A Private Endpoint connects your network privately to Azure services, avoiding public internet.

2. Step 2: Compare options with this definition

   Only To connect to Azure services privately within your network describes private network connection to Azure services.

3. Final Answer:

   To connect to Azure services privately within your network -> Option C

4. Quick Check:

   Private Endpoint = Private connection [OK]

Hint: Private endpoints = private network access to Azure [OK]

Common Mistakes:

• Confusing private endpoint with public access
• Thinking it speeds up internet browsing
• Assuming it creates virtual machines

2. Which of the following is the correct way to create a Private Endpoint in Azure Portal?

easy

A. Go to Private Link Center > Private Endpoints > Create

B. Go to Virtual Machines > Create > Private Endpoint

C. Go to Storage Accounts > Networking > Public Access

D. Go to Azure Active Directory > Users > Private Endpoint

Solution

1. Step 1: Identify where Private Endpoints are managed

   Private Endpoints are created under Private Link Center in Azure Portal.

2. Step 2: Match the correct navigation path

   Go to Private Link Center > Private Endpoints > Create correctly shows Private Link Center > Private Endpoints > Create.

3. Final Answer:

   Go to Private Link Center > Private Endpoints > Create -> Option A

4. Quick Check:

   Private Endpoint creation is in Private Link Center [OK]

Hint: Private Endpoints are under Private Link Center in Azure Portal [OK]

Common Mistakes:

• Looking under Virtual Machines or Storage Accounts
• Confusing Private Endpoint with user management
• Selecting Public Access settings instead

3. Consider this scenario: You create a Private Endpoint for an Azure Storage Account. What happens to the network traffic when you access the storage account from your virtual network?

medium

A. Traffic goes over the public internet but is encrypted

B. Traffic is routed through a public IP address of the storage account

C. Traffic is blocked unless you use a VPN

D. Traffic is routed privately inside Azure network, avoiding public internet

Solution

1. Step 1: Understand Private Endpoint traffic routing

   Private Endpoints route traffic privately inside Azure, avoiding the public internet.

2. Step 2: Analyze each option

   Traffic is routed privately inside Azure network, avoiding public internet correctly states traffic is routed privately inside Azure network.

3. Final Answer:

   Traffic is routed privately inside Azure network, avoiding public internet -> Option D

4. Quick Check:

   Private Endpoint = private routing inside Azure [OK]

Hint: Private Endpoint routes traffic inside Azure, not public internet [OK]

Common Mistakes:

• Assuming traffic still uses public internet
• Thinking VPN is always required
• Confusing public IP routing with private endpoint

4. You created a Private Endpoint but your virtual machine cannot access the Azure SQL Database privately. What is the most likely cause?

medium

A. The virtual machine is not in the same subscription

B. The Private Endpoint DNS configuration is missing or incorrect

C. Azure SQL Database does not support Private Endpoints

D. The virtual machine needs a public IP address

Solution

1. Step 1: Identify common Private Endpoint issues

   DNS configuration is critical for Private Endpoint to resolve the private IP address.

2. Step 2: Evaluate options

   The Private Endpoint DNS configuration is missing or incorrect points to DNS misconfiguration, a common cause of access failure.

3. Final Answer:

   The Private Endpoint DNS configuration is missing or incorrect -> Option B

4. Quick Check:

   DNS setup is key for Private Endpoint access [OK]

Hint: Check DNS settings if Private Endpoint access fails [OK]

Common Mistakes:

• Assuming subscription difference blocks access
• Believing Azure SQL doesn't support Private Endpoints
• Thinking public IP is needed for private access

5. You want to secure access to an Azure Key Vault so only your virtual network can reach it privately. Which combination of Azure features should you use?

hard

A. Enable Private Endpoint for the Key Vault and configure DNS to resolve the private IP

B. Use a Public IP with firewall rules allowing your network IP range

C. Create a Private Endpoint for the Key Vault and configure virtual network service endpoints

D. Deploy a VPN gateway and connect to the Key Vault over public internet

Solution

1. Step 1: Understand securing Key Vault with private access

   Private Endpoint provides private IP access; DNS must resolve Key Vault name to this private IP.

2. Step 2: Analyze options for best practice

   Enable Private Endpoint for the Key Vault and configure DNS to resolve the private IP correctly combines Private Endpoint creation with DNS configuration for private access.

3. Final Answer:

   Enable Private Endpoint for the Key Vault and configure DNS to resolve the private IP -> Option A

4. Quick Check:

   Private Endpoint + DNS config = secure private access [OK]

Hint: Private Endpoint plus DNS setup secures private access [OK]

Common Mistakes:

• Confusing service endpoints with Private Endpoints
• Relying on public IP and firewall only
• Using VPN unnecessarily for private Azure service access