Dapr simplifies communication between microservices. Which option best describes how Dapr manages this?
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.
In a Dapr-enabled application, which component is responsible for managing state persistence?
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.
Dapr secures service-to-service calls. Which method does it primarily use to ensure secure communication?
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.
When deploying Dapr-enabled microservices on Azure Kubernetes Service (AKS), which practice helps ensure reliability?
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.
In a Kubernetes cluster running Dapr, what is the expected behavior if the Dapr sidecar container fails to start in a pod?
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.