AKS vs App Service vs Functions decision in Azure - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Choosing the right Azure service for a microservices app

You have a microservices application with multiple components that need to scale independently and require container orchestration. Which Azure service is the best fit?

A Azure Blob Storage

B Azure App Service

C Azure Functions

D Azure Kubernetes Service (AKS)

💡 Hint

Think about container orchestration and independent scaling.

AKS is designed for container orchestration and managing microservices with independent scaling. App Service is for web apps without complex orchestration. Functions are for event-driven serverless tasks. Blob Storage is for storing files, not running apps.

❓ service_behavior

intermediate

Scaling behavior of Azure Functions

Which statement best describes how Azure Functions scale when demand increases?

A Azure Functions require manual scaling through the Azure portal.

B Azure Functions scale only vertically by increasing CPU and memory of a single instance.

C Azure Functions automatically scale out by creating more instances based on incoming events.

D Azure Functions do not support scaling and run on a fixed number of instances.

💡 Hint

Consider how serverless services handle load.

Azure Functions automatically scale out by adding instances in response to event triggers, without manual intervention. Vertical scaling is not how Functions scale. Manual scaling is not required.

❓ Architecture

advanced

Best Azure service for a long-running background job

You need to run a background job that processes large files and can take several hours to complete. Which Azure service is most suitable?

A Azure Kubernetes Service (AKS)

B Azure App Service WebJob

C Azure Logic Apps

D Azure Functions with a consumption plan

💡 Hint

Think about long-running processes and control over execution.

AKS supports long-running workloads with full control over containers and resources. Functions on consumption plan have execution time limits. App Service WebJobs can run background tasks but have less control and scaling flexibility. Logic Apps are for orchestrating workflows, not heavy processing.

❓ security

advanced

Securing sensitive environment variables in Azure App Service

Which method is the most secure way to manage sensitive environment variables like API keys in Azure App Service?

A Use Azure Key Vault references in App Service Application Settings.

B Hardcode them in the application source code.

C Store them directly in the App Service Application Settings.

D Save them in a public GitHub repository linked to the app.

💡 Hint

Consider secure storage and access management for secrets.

Azure Key Vault allows secure storage of secrets and can be referenced in App Service settings without exposing them in code or settings directly. Hardcoding or storing in public repos is insecure. Directly storing in settings is less secure than Key Vault.

✅ Best Practice

expert

Optimizing cost and performance for event-driven workloads

You have an event-driven workload with unpredictable traffic spikes. You want to minimize cost while ensuring fast response times. Which Azure service and plan combination is the best choice?

A Azure Kubernetes Service with fixed node count

B Azure Functions on a Premium plan with pre-warmed instances

C Azure App Service on a Standard plan with manual scaling

D Azure Functions on a Consumption plan without pre-warmed instances

💡 Hint

Think about balancing cost, scaling, and cold start delays.

Azure Functions Premium plan supports pre-warmed instances to avoid cold starts and scales automatically, balancing cost and performance for unpredictable traffic. Consumption plan is cheaper but can have cold start delays. App Service and AKS with fixed scaling are less cost-efficient for unpredictable spikes.