Dapr integration overview in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to initialize Dapr client in an Azure application.

Azure

from dapr.clients import DaprClient
client = DaprClient()  # Create a [1] client instance

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

ACloud

BAzure

CDapr

DService

Attempts:

3 left

💡 Hint

Common Mistakes

Using Azure or Service instead of Dapr as the client class.

Not creating a client instance before use.

The Dapr client is created by calling DaprClient() which initializes the client to interact with Dapr sidecar.

2fill in blank

medium

Complete the code to publish a message to a topic using Dapr in Azure.

Azure

client.publish_event(pubsub_name='[1]', topic='orders', data=b'order data')

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

Apubsub

Bazure-pubsub

Cazure-servicebus

Deventbus

Attempts:

3 left

💡 Hint

Common Mistakes

Using Azure-specific names instead of the configured pubsub component name.

Confusing topic name with pubsub name.

The default pubsub component name is usually pubsub unless customized.

3fill in blank

hard

Fix the error in the code to retrieve a secret from Azure Key Vault using Dapr.

Azure

secret = client.get_secret(store_name='[1]', key='db-password')

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

Aazure-keyvault

Bkeyvault

Cazurekeyvault

Dkeyvaultstore

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'azurekeyvault' without hyphen.

Using generic names like 'keyvaultstore'.

The correct store name for Azure Key Vault in Dapr is azure-keyvault.

4fill in blank

hard

Fill both blanks to configure a Dapr state store and save state.

Azure

state_store = '[1]'
client.save_state(store_name=state_store, key='user1', value=[2])

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

Astatestore

B'{"name": "Alice"}'

C{"name": "Alice"}

Dblobstore

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'blobstore' instead of 'statestore' as store name.

Passing JSON string instead of dictionary for value.

The state store name is typically 'statestore'. The value must be a Python dictionary, not a string.

5fill in blank

hard

Fill all three blanks to subscribe to a topic and handle events in a Dapr-enabled Azure app.

Azure

from dapr.ext.grpc import App
app = App()

@app.subscribe(pubsub_name='[1]', topic='[2]')
def handle_event(data):
    print('Received:', [3])

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

Apubsub

Borders

Cdata

Deventbus

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong pubsub component name.

Using wrong topic name.

Printing undefined variable instead of 'data'.

The pubsub component is 'pubsub', the topic is 'orders', and the event handler prints the received data variable.

Practice

1. What is the main purpose of Dapr in cloud applications?

easy

A. To replace cloud providers completely

B. To simplify cloud app features without complex code

C. To create virtual machines automatically

D. To manage user interface design

Solution

1. Step 1: Understand Dapr's role

   Dapr helps developers by making common cloud app features easy to use without writing complex code.

2. Step 2: Compare options

   Options B, C, and D describe unrelated tasks. Only To simplify cloud app features without complex code matches Dapr's purpose.

3. Final Answer:

   To simplify cloud app features without complex code -> Option B

4. Quick Check:

   Dapr simplifies cloud features = A [OK]

Hint: Remember: Dapr eases cloud features, not replaces providers [OK]

Common Mistakes:

• Thinking Dapr replaces cloud providers
• Confusing Dapr with UI tools
• Assuming Dapr manages virtual machines

2. Which of the following is a valid Dapr configuration setting?

easy

A. samplingRate: 1

B. MaxInstances: 1000

C. AutoScale: off

D. UITheme: dark

Solution

1. Step 1: Identify common Dapr config options

   Dapr configuration often includes settings like tracing and security, e.g., samplingRate.

2. Step 2: Evaluate options

   Options A, B, and D are unrelated to Dapr's config. Only samplingRate: 1 is valid.

3. Final Answer:

   samplingRate: 1 -> Option A

4. Quick Check:

   Dapr config includes tracing = C [OK]

Hint: Look for tracing or security keywords in config [OK]

Common Mistakes:

• Choosing unrelated config keys
• Confusing Dapr config with app settings
• Selecting UI or scaling options not in Dapr

3. Given this Dapr component YAML snippet:

apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: statestore
spec:
  type: state.azure.cosmosdb
  metadata:
  - name: url
    value: https://mycosmos.documents.azure.com:443/
  - name: masterKey
    value: secretkey
  - name: databaseName
    value: mydb

What does this configuration do?

medium

A. Defines a state store component using Azure Cosmos DB

B. Creates a new Cosmos DB database named 'mydb'

C. Sets up a message queue for app communication

D. Configures tracing for Dapr components

Solution

1. Step 1: Analyze the YAML kind and spec

   The kind 'Component' with type 'state.azure.cosmosdb' means it defines a state store using Cosmos DB.

2. Step 2: Understand metadata fields

   Metadata includes connection info (url, masterKey, databaseName) for Cosmos DB access, not creating DB or queues.

3. Final Answer:

   Defines a state store component using Azure Cosmos DB -> Option A

4. Quick Check:

   Component type state.azure.cosmosdb = D [OK]

Hint: Look for 'state.azure.cosmosdb' type to identify state store [OK]

Common Mistakes:

• Thinking it creates the database itself
• Confusing state store with message queue
• Assuming it configures tracing

4. You have this Dapr configuration snippet:

apiVersion: dapr.io/v1alpha1
kind: Configuration
metadata:
  name: myconfig
spec:
  tracing:
    samplingRate: "0.5"
  mtls:
    enabled: true

What is the error in this configuration?

medium

A. mtls cannot be enabled in Dapr configuration

B. metadata name must be 'default'

C. Missing component type field

D. samplingRate should be a number, not a string

Solution

1. Step 1: Check tracing samplingRate format

   samplingRate expects a numeric value, but "0.5" is a string (in quotes), which is invalid.

2. Step 2: Validate other fields

   mtls enabled is valid, component type is not required in Configuration kind, and metadata name can be custom.

3. Final Answer:

   samplingRate should be a number, not a string -> Option D

4. Quick Check:

   samplingRate type error = B [OK]

Hint: Check data types carefully in YAML values [OK]

Common Mistakes:

• Assuming mtls can't be enabled
• Expecting component type in Configuration
• Thinking metadata name must be 'default'

5. You want to secure communication between your microservices using Dapr. Which combination of settings should you configure?

hard

A. Only configure tracing to monitor traffic

B. Disable mTLS and increase component replicas

C. Enable mTLS in Dapr configuration and set tracing samplingRate

D. Use Dapr without any configuration changes

Solution

1. Step 1: Identify security features in Dapr

   Dapr supports mTLS (mutual TLS) to secure service-to-service communication.

2. Step 2: Combine security with observability

   Enabling mTLS secures communication; setting tracing samplingRate helps monitor traffic, both important.

3. Final Answer:

   Enable mTLS in Dapr configuration and set tracing samplingRate -> Option C

4. Quick Check:

   mTLS + tracing for secure, observable communication = A [OK]

Hint: Secure with mTLS and monitor with tracing [OK]

Common Mistakes:

• Disabling mTLS weakens security
• Ignoring tracing for observability
• Assuming no config needed for security