Connection from applications in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the connection string for an Azure Storage account.

Azure

connection_string = "DefaultEndpointsProtocol=https;AccountName=[1];AccountKey=your_key;EndpointSuffix=core.windows.net"

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

AmyStorageAccount

BmyResourceGroup

CmyContainer

DmySubscription

Attempts:

3 left

💡 Hint

Common Mistakes

Using the resource group name instead of the storage account name.

Using the container name in the connection string.

The AccountName in the connection string must be the name of your Azure Storage account.

2fill in blank

medium

Complete the code to create a BlobServiceClient using the connection string.

Azure

from azure.storage.blob import BlobServiceClient
client = BlobServiceClient.from_connection_string([1])

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

Acontainer_name

Baccount_key

Cconnection_string

Dendpoint_suffix

Attempts:

3 left

💡 Hint

Common Mistakes

Passing only the account key instead of the full connection string.

Passing the container name instead of the connection string.

The from_connection_string method requires the full connection string to create the client.

3fill in blank

hard

Fix the error in the code to upload a blob to Azure Blob Storage.

Azure

blob_client = client.get_blob_client(container=[1], blob='example.txt')
with open('example.txt', 'rb') as data:
    blob_client.upload_blob(data)

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

A'mycontainer'

BmyContainer

Ccontainer_name

D'myContainer'

Attempts:

3 left

💡 Hint

Common Mistakes

Using the container name without quotes causing a NameError.

Using incorrect casing for container names.

The container name must be a string literal with quotes in Python.

4fill in blank

hard

Fill both blanks to list blobs in a container and print their names.

Azure

container_client = client.get_container_client([1])
for blob in container_client.[2]():
    print(blob.name)

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

A'mycontainer'

Blist_blobs

Cget_blobs

D'container1'

Attempts:

3 left

💡 Hint

Common Mistakes

Using a variable without quotes for container name.

Using a non-existent method get_blobs().

The container name must be a string, and the method to list blobs is list_blobs().

5fill in blank

hard

Fill all three blanks to download a blob and save it locally.

Azure

blob_client = client.get_blob_client(container=[1], blob=[2])
with open([3], 'wb') as file:
    data = blob_client.download_blob()
    file.write(data.readall())

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

A'mycontainer'

B'example.txt'

C'downloaded_example.txt'

D'localfile.txt'

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting quotes around container or blob names.

Using the same name for local file and blob without quotes.

The container and blob names must be strings with quotes, and the local file name is also a string.

Practice

1. What is the main purpose of a connection string when an application connects to an Azure service?

easy

A. It stores the application's source code.

B. It provides the necessary information to authenticate and access the service.

C. It defines the user interface of the application.

D. It manages the billing details for the Azure subscription.

Solution

1. Step 1: Understand connection string role

   A connection string contains credentials and endpoint details needed to connect securely to an Azure service.

2. Step 2: Eliminate unrelated options

   Options about source code, UI, or billing are unrelated to connection strings.

3. Final Answer:

   It provides the necessary information to authenticate and access the service. -> Option B

4. Quick Check:

   Connection string = authentication info [OK]

Hint: Connection strings hold access info, not code or UI [OK]

Common Mistakes:

• Confusing connection strings with application code
• Thinking connection strings manage billing
• Assuming connection strings define UI

2. Which of the following is the correct format for an Azure Storage Account connection string?

easy

A. AccountName=youraccount;Password=yourpassword;Region=us-east

B. https://youraccount.blob.core.windows.net/yourcontainer

C. DefaultEndpointsProtocol=https;AccountName=youraccount;AccountKey=yourkey;EndpointSuffix=core.windows.net

D. Server=yourserver;Database=yourdb;User Id=youruser;Password=yourpassword;

Solution

1. Step 1: Identify Azure Storage connection string format

   Azure Storage connection strings include protocol, account name, account key, and endpoint suffix as in DefaultEndpointsProtocol=https;AccountName=youraccount;AccountKey=yourkey;EndpointSuffix=core.windows.net.

2. Step 2: Compare other options

   https://youraccount.blob.core.windows.net/yourcontainer is a URL, not a connection string. AccountName=youraccount;Password=yourpassword;Region=us-east uses wrong keys and lacks protocol. Server=yourserver;Database=yourdb;User Id=youruser;Password=yourpassword; is a SQL Server connection string format.

3. Final Answer:

   DefaultEndpointsProtocol=https;AccountName=youraccount;AccountKey=yourkey;EndpointSuffix=core.windows.net -> Option C

4. Quick Check:

   Storage connection string = protocol + account info [OK]

Hint: Look for protocol, account name, and key in connection string [OK]

Common Mistakes:

• Confusing URLs with connection strings
• Using SQL connection string format for Azure Storage
• Missing protocol or key in connection string

3. Given this Python code snippet connecting to Azure Blob Storage, what will be the output if the connection string is invalid?

from azure.storage.blob import BlobServiceClient
try:
    conn_str = "InvalidConnectionString"
    blob_service_client = BlobServiceClient.from_connection_string(conn_str)
    print("Connection successful")
except Exception as e:
    print(f"Connection failed: {e}")

medium

A. Connection failed: Invalid connection string format

B. Connection successful

C. SyntaxError

D. No output

Solution

1. Step 1: Analyze code behavior on invalid connection string

   The BlobServiceClient.from_connection_string method raises an exception if the string is invalid.

2. Step 2: Check exception handling output

   The except block catches the exception and prints "Connection failed:" with the error message.

3. Final Answer:

   Connection failed: Invalid connection string format -> Option A

4. Quick Check:

   Invalid string triggers exception message [OK]

Hint: Invalid connection strings cause exceptions caught and printed [OK]

Common Mistakes:

• Assuming connection always succeeds
• Expecting syntax errors instead of runtime exceptions
• Ignoring exception handling output

4. You wrote this code to connect to Azure Key Vault but get an authentication error:

from azure.identity import DefaultAzureCredential
from azure.keyvault.secrets import SecretClient

credential = DefaultAzureCredential()
client = SecretClient(vault_url="https://myvault.vault.azure.net/", credential=credential)
secret = client.get_secret("MySecret")
print(secret.value)

What is the most likely cause of the error?

medium

A. The SecretClient class is deprecated and cannot be used.

B. The vault URL is incorrect and missing the .com suffix.

C. The secret name "MySecret" is invalid because it contains uppercase letters.

D. The application lacks proper Azure AD permissions or managed identity is not enabled.

Solution

1. Step 1: Understand authentication with DefaultAzureCredential

   This credential requires the app to have Azure AD permissions or a managed identity enabled to access Key Vault.

2. Step 2: Evaluate other options

   The vault URL format is correct without .com. SecretClient is current and uppercase secret names are allowed.

3. Final Answer:

   The application lacks proper Azure AD permissions or managed identity is not enabled. -> Option D

4. Quick Check:

   Authentication error = missing permissions or identity [OK]

Hint: Check Azure AD permissions and managed identity setup first [OK]

Common Mistakes:

• Assuming URL must end with .com
• Thinking SecretClient is deprecated
• Believing secret names cannot have uppercase letters

5. You want your Azure web app to securely connect to Azure SQL Database without storing credentials in code. Which approach is best practice?

hard

A. Use Managed Identity for the web app and configure Azure SQL to allow Azure AD authentication.

B. Store the SQL username and password in the web app's environment variables.

C. Embed the SQL connection string with username and password directly in the application code.

D. Use a public IP whitelist to restrict SQL access and use SQL authentication.

Solution

1. Step 1: Identify secure connection methods without hardcoding credentials

   Managed Identity allows the app to authenticate to Azure SQL using Azure AD without secrets in code.

2. Step 2: Compare other options for security risks

   Storing credentials in environment variables or code risks exposure. IP whitelisting alone does not remove credential storage.

3. Final Answer:

   Use Managed Identity for the web app and configure Azure SQL to allow Azure AD authentication. -> Option A

4. Quick Check:

   Managed Identity + Azure AD = secure no-secret connection [OK]

Hint: Managed Identity avoids storing secrets in code [OK]

Common Mistakes:

• Hardcoding credentials in code
• Relying only on IP whitelisting
• Storing secrets in environment variables without encryption