Container Apps for microservices in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Architecture

intermediate

Microservice Communication in Azure Container Apps

You have deployed multiple microservices as Azure Container Apps. You want these microservices to communicate securely within the same environment without exposing them publicly.

Which configuration option ensures secure internal communication between microservices?

A Expose each microservice on a public port and secure with firewall rules.

B Enable ingress with external visibility and use public URLs for communication.

C Use Azure API Management to route traffic between microservices externally.

D Disable ingress and use internal Dapr service invocation between Container Apps.

💡 Hint

Think about how Azure Container Apps enable secure service-to-service calls without public exposure.

Disabling ingress and using Dapr service invocation allows microservices to communicate securely inside the Container Apps environment without exposing endpoints publicly.

❓ Configuration

intermediate

Scaling Microservices in Azure Container Apps

You want to configure automatic scaling for a microservice deployed as an Azure Container App based on HTTP request load.

Which scaling trigger should you configure to scale out the microservice when HTTP requests increase?

A Configure a Dapr pub/sub trigger to scale on message queue length.

B Configure a CPU-based scaling trigger to scale when CPU usage exceeds 70%.

C Configure an HTTP scaling trigger to scale based on concurrent HTTP requests.

D Configure a manual scale setting with fixed instance count.

💡 Hint

Consider which trigger directly relates to HTTP traffic load.

The HTTP scaling trigger automatically scales the Container App based on the number of concurrent HTTP requests, making it ideal for web-based microservices.

❓ security

advanced

Securing Secrets in Azure Container Apps Microservices

You have multiple microservices running as Azure Container Apps that require access to sensitive configuration values like database passwords.

What is the best practice to securely provide these secrets to your microservices?

A Use Azure Key Vault references integrated with Azure Container Apps secrets feature.

B Store secrets in environment variables directly in the Container App configuration.

C Embed secrets in the container image during build time.

D Store secrets in a public GitHub repository and pull them at runtime.

💡 Hint

Think about a secure, managed way to handle secrets without exposing them in code or environment variables.

Azure Container Apps supports integration with Azure Key Vault, allowing secrets to be securely referenced and injected at runtime without exposing them in code or environment variables.

❓ service_behavior

advanced

Observability in Azure Container Apps Microservices

You want to monitor logs and metrics from multiple microservices running as Azure Container Apps to troubleshoot performance issues.

Which Azure service should you configure to collect and analyze telemetry data from your Container Apps?

A Azure Functions to poll Container Apps logs periodically.

B Azure Monitor with Container Insights enabled for Container Apps.

C Azure DevOps pipelines for log collection.

D Azure Blob Storage to store logs manually from each Container App.

💡 Hint

Consider the Azure service designed for monitoring and diagnostics of container workloads.

Azure Monitor with Container Insights provides integrated monitoring, collecting logs and metrics from Container Apps for analysis and troubleshooting.

✅ Best Practice

expert

Designing a Resilient Microservices Architecture with Azure Container Apps

You are designing a microservices architecture using Azure Container Apps. You want to ensure that if one microservice fails, it does not cause the entire application to become unavailable.

Which design approach best supports this resilience?

A Use separate Container Apps for each microservice with independent scaling and health probes.

B Combine all microservices into one monolithic container to reduce network calls.

C Deploy all microservices in a single Container App instance to simplify management.

D Disable health checks to avoid automatic restarts that might cause downtime.

💡 Hint

Think about isolation and independent management of microservices for fault tolerance.

Deploying each microservice as a separate Container App allows independent scaling, health monitoring, and failure isolation, improving overall application resilience.