Dapr integration overview in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does Dapr handle service-to-service communication?

Dapr simplifies communication between microservices. Which option best describes how Dapr manages this?

A Dapr uses a centralized message broker that all services must connect to for communication.

B Dapr requires services to directly call each other's IP addresses without intermediaries.

C Dapr uses HTTP or gRPC calls through a sidecar proxy to route requests between services.

D Dapr only supports communication through database polling between services.

💡 Hint

Think about how Dapr runs alongside your service to help with communication.

Dapr runs as a sidecar next to each service and handles communication using HTTP or gRPC calls. This abstracts the complexity of direct service calls.

❓ Architecture

intermediate

Which component in Dapr manages state storage?

In a Dapr-enabled application, which component is responsible for managing state persistence?

A The Dapr sidecar uses configured state stores to save and retrieve state data.

B State is managed by a separate external caching service unrelated to Dapr.

C Dapr uses a built-in database embedded in the sidecar for state management.

D The application service directly writes to the database without Dapr involvement.

💡 Hint

Consider how Dapr abstracts state management for your app.

Dapr sidecars connect to configured state stores like Redis or Azure Cosmos DB to manage state, so your app code doesn't handle storage directly.

❓ security

advanced

What is the primary security feature Dapr uses for service invocation?

Dapr secures service-to-service calls. Which method does it primarily use to ensure secure communication?

A Dapr requires manual API key management between services for authentication.

B Dapr uses mutual TLS (mTLS) to encrypt and authenticate service calls automatically.

C Dapr relies on IP whitelisting configured in the network firewall only.

D Dapr uses unencrypted HTTP calls and trusts the network security layer.

💡 Hint

Think about how Dapr ensures both encryption and identity verification.

Dapr automatically enables mutual TLS between sidecars to encrypt traffic and verify identities, enhancing security without extra developer effort.

✅ Best Practice

advanced

Which practice is recommended when deploying Dapr in production on Azure?

When deploying Dapr-enabled microservices on Azure Kubernetes Service (AKS), which practice helps ensure reliability?

A Deploy Dapr sidecars as part of each pod and configure health probes for readiness and liveness.

B Run Dapr sidecars on separate nodes to isolate them from application pods.

C Disable Dapr sidecars in production to reduce resource usage.

D Use a single shared Dapr sidecar for all services to simplify management.

💡 Hint

Think about how Kubernetes manages pod health and sidecar containers.

Deploying Dapr sidecars alongside each app pod with proper health checks ensures smooth operation and quick recovery in AKS.

❓ service_behavior

expert

What happens if a Dapr sidecar fails to start alongside a service pod?

In a Kubernetes cluster running Dapr, what is the expected behavior if the Dapr sidecar container fails to start in a pod?

A Kubernetes will remove the pod permanently and not attempt to restart it.

B The pod will start normally without the sidecar, but service calls through Dapr will fail silently.

C The pod will run but Dapr features will be disabled automatically without errors.

D The pod will fail its readiness check and Kubernetes will restart it until the sidecar starts successfully.

💡 Hint

Consider how Kubernetes handles container failures in pods with multiple containers.

Kubernetes treats the pod as unhealthy if any container, including the Dapr sidecar, fails. It restarts the pod to ensure all containers run properly.

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