Test Flashcards

Question

How do you enable diagnostic logging in Azure App Service, and what can it troubleshoot?

Answer 1

**Enable Logging**: Via portal's **Monitoring settings** **Log Types**: - **App logs** - **Server logs** - **Failed request traces** **Troubleshoots**: Errors, performance issues, deployment problems

Answer 2

**Azure Functions**: A **serverless compute service** for running **event-driven code** without managing infrastructure **Primary Purpose**: Execute **small, single-purpose functions** in response to **triggers** like HTTP requests or timers

Answer 3

**Supported Languages**: - **C#** - **Java** - **JavaScript (Node.js)** - **Python** - **PowerShell** - **TypeScript** - **Custom handlers** for other languages

Answer 4

**Triggers**: Events that **invoke a function** **Examples**: - **HTTP requests** - **Timers** (TimerTrigger) - **Azure Blob storage** changes (BlobTrigger) - **Azure Service Bus** messages (ServiceBusTrigger)

Answer 5

**Bindings**: Connect functions to **external data or services** (input/output) without extra code **Difference from Triggers**: - **Triggers**: Start execution - **Bindings**: Handle data flow (e.g., Blob storage input, Cosmos DB output)

Answer 6

**Creation Methods**: - **Azure portal** - **Azure CLI** - **Development tools**: Visual Studio, Visual Studio Code, Maven **Requirements**: Azure subscription and **function app**

Answer 7

**Function App**: A **container** for one or more Azure Functions **Provides**: - **Runtime environment** - **Shared configuration** (app settings) - **Hosting plan** (Consumption, Premium, or App Service)

Answer 8

**Azure Functions Hosting Plans**: - **Consumption**: Serverless, pay-per-execution, **auto-scales** - **Premium**: **Pre-warmed instances**, VNet support, **longer execution** - **App Service**: **Dedicated VMs**, predictable costs, shared with web apps

Answer 9

**Automatic Scaling**: In Consumption/Premium plans **Scaling Drivers**: - **Event volume** (HTTP requests, queue depth) - **Scale Controller** monitors and adjusts **instance count** dynamically

Answer 10

**Durable Functions**: Extension for **stateful, long-running workflows** in serverless environment **Problem Solved**: Managing **state and orchestration** in event-driven applications

Answer 11

**Durable Function Patterns**: - **Function Chaining**: Sequential execution - **Fan-out/Fan-in**: Parallel tasks with aggregation - **Async HTTP APIs**: Long-running operations - **Monitor**: Recurring checks - **Human Interaction**: Approval workflows

Answer 12

**Configurable Settings**: - **App settings** (key-value pairs) - **Runtime version** - **Authentication** - **CORS** **Management**: Azure portal, CLI, or `host.json`/`local.settings.json`

Answer 13

**Security Methods**: - **Function keys** (host, function-specific) - **Microsoft Entra ID** for authentication - **API Management** integration - **Network security** (VNet, private endpoints in Premium plan)

Answer 14

**Monitoring Tools**: - **Azure Monitor** - **Application Insights** for logs, metrics, and tracing **Key Metrics**: Execution count, errors, performance **Configuration**: Via portal or CLI

Answer 15

**Deployment Options**: - **Zip deploy**: Push a .zip package - **GitHub/Azure DevOps**: Continuous deployment - **VS/VS Code**: Direct publishing **Target**: The **function app**

Answer 16

**HTTP Triggers**: - Invoke functions via **HTTP requests** (GET, POST, etc.) - Support **auth levels** (anonymous, function, admin) - Can **return responses** directly or via output bindings

Answer 17

**Timer Triggers**: Run functions on a **schedule** **Schedule Definition**: **CRON expression** (e.g., `0 */5 * * * *` for every 5 minutes) **Configuration**: In the function's settings

Answer 18

**Integration Services**: - **Blob Storage** - **Cosmos DB** - **Event Hubs** - **Service Bus** - **Event Grid** - **Queue Storage** For **input/output operations**

Answer 19

**Local Development**: - Use **Azure Functions Core Tools** - **IDE support**: VS Code, Visual Studio - **Local testing**: Simulate triggers/bindings with `local.settings.json`

Answer 20

**Azure IaaS**: Virtualized compute resources managed by Azure **Key Components**: - **Azure Virtual Machines (VMs)** - **Virtual networks (VNets)** - **Storage** Offers **full control** over OS and infrastructure

Answer 21

**Creation Methods**: Azure portal, CLI, or SDK **Basic Steps**: 1. Choose **image** (Windows/Linux) 2. Select **size** and **region** 3. Configure **VNet** and **authentication** (password/SSH) 4. Set up **disks** and **networking**

Answer 22

**Azure CLI VM Creation**: `az vm create --resource-group myRG --name myVM --image UbuntuLTS --admin-username azureuser --generate-ssh-keys`

Answer 23

**ARM Templates**: **JSON files** defining infrastructure **declaratively** **Purpose**: - **Automate** deployments - **Repeat** consistent infrastructure - **Manage** resources like VMs, storage, networks

Answer 24

**ARM Template Structure**: - `$schema` - `contentVersion` - `parameters` - `variables` - `resources` - `outputs`

Answer 25

**ARM Template VM Deployment**: 1. Define VM in `resources` section 2. Deploy with CLI: `az deployment group create --resource-group myRG --template-file vm-template.json --parameters vmName=myVM adminUsername=azureuser`

Answer 26

**Azure.ResourceManager SDK VM Creation**: ```csharp using Azure.ResourceManager; using Azure.ResourceManager.Compute; ArmClient client = new ArmClient(new DefaultAzureCredential()); ResourceGroupResource rg = client.GetResourceGroupResource(ResourceGroupResource.CreateResourceIdentifier(\"subscription-id\", \"myRG\")); VirtualMachineCollection vmCollection = rg.GetVirtualMachines(); VirtualMachineData vmData = new VirtualMachineData(rg.Data.Location) { /* Configure VM properties */ }; await vmCollection.CreateOrUpdateAsync(WaitUntil.Completed, \"myVM\", vmData); ```

Answer 27

**Custom Script Extension**: `az vm extension set --resource-group myRG --vm-name myVM --name CustomScriptExtension --publisher Microsoft.Azure.Extensions --settings '{\"fileUris\": [\"https://script.sh\"], \"commandToExecute\": \"./script.sh\"}'`

Answer 28

**VM Availability Options**: - **Availability Sets**: Distribute VMs across **fault/update domains** - **Availability Zones**: Place VMs in **separate physical locations** - **VM Scale Sets**: **Auto-scale** identical VMs **Reliability**: Improved via **redundancy**

Answer 29

**VM Scale Sets**: Manage **identical, load-balanced VMs** **Functionality**: - **Auto-scale** based on demand (CPU usage) - **Simplify deployment** and maintenance of multiple VMs

Answer 30

**VM Scale Set Creation**: `az vmss create --resource-group myRG --name myScaleSet --image UbuntuLTS --instance-count 2 --admin-username azureuser --generate-ssh-keys`

Answer 31

**Application Deployment Options**: - **Manual setup**: SSH/RDP, copy files - **Custom Script Extension**: Automated setup - **CI/CD**: Azure DevOps for automated deployment post-provisioning

Answer 32

**Container Deployment**: Run containers on VMs using **Docker** **Common Approach**: 1. Provision VM 2. Install Docker 3. Pull and run image: `docker run -d -p 80:80 myimage`

Answer 33

**Azure Container Instances**: **Serverless container hosting** **Deployment**: `az container create --resource-group myRG --name mycontainer --image myimage --ports 80`

Answer 34

**IaaS Security Methods**: - **Network Security Groups (NSGs)** - **Firewalls** - **Microsoft Entra ID (RBAC)** - **Disk encryption** - **VNet isolation** (private endpoints)

Answer 35

**Monitoring Tools**: - **Azure Monitor**: Metrics (CPU, disk) - **Log Analytics**: Detailed logs **Configuration**: Via portal or SDK

Answer 36

**VM Networking Configuration**: - Assign to **VNet/subnet** - Set **NSG rules** - Configure **public IP** or **load balancer** **CLI Example**: `az vm open-port --resource-group myRG --name myVM --port 80`

Answer 37

**VM vs App Service**: - **VMs (IaaS)**: Full control over OS/software, **manual management** - **App Service (PaaS)**: **Managed service**, **auto-scales**, **abstracts infrastructure**

Answer 38

**ACR Container Management**: 1. **Build and tag** Docker image: ```bash docker build -t myimage:latest . docker tag myimage:latest myregistry.azurecr.io/myimage:latest ``` 2. **Login and push**: ```bash az acr login --name myregistry docker push myregistry.azurecr.io/myimage:latest ``` 3. **Manage images**: ```bash az acr repository list --name myregistry --output table az acr repository delete --name myregistry --image myregistry.azurecr.io/myimage:latest ```

Answer 39

**Azure Container Apps Deployment**: `az containerapp create --name mycontainerapp --resource-group myResourceGroup --image myregistry.azurecr.io/myimage:latest --environment myenvironment --target-port 80 --ingress 'external' --min-replicas 1 --max-replicas 3` **Features**: **Scalable container app** with **external ingress**

Answer 40

**Containerized App Service Deployment**: `az webapp create --resource-group myResourceGroup --name mywebapp --plan myAppServicePlan --deployment-container-image-name myregistry.azurecr.io/myimage:latest` **Requirements**: App Service plan supports **Linux** and **Docker**

Answer 41

**App Service Autoscaling**: 1. Navigate to **App Service plan** and enable autoscale 2. **Azure CLI Configuration**: ```bash az appservice plan update --name myAppServicePlan --resource-group myResourceGroup --min-instances 1 --max-instances 5 --scale-up-rule \"CpuPercentage > 70 for 10 minutes\" ``` **Scaling**: 1 to 5 instances based on **CPU usage > 70%** for 10 minutes

Answer 42

**App Service Diagnostics & Logging**: 1. **Enable logging**: ```bash az webapp log config --name mywebapp --resource-group myResourceGroup --application-logging true --web-server-logging filesystem ``` 2. **View real-time logs**: ```bash az webapp log tail --name mywebapp --resource-group myResourceGroup ``` 3. **Application Insights**: ```csharp var builder = WebApplication.CreateBuilder(args); builder.Services.AddApplicationInsightsTelemetry(); ```

Answer 43

"**App Service Configuration**: 1. **TLS Certificate Binding**: ```bash az webapp config ssl bind --resource-group myResourceGroup --name mywebapp --certificate-thumbprint --ssl-type SNI ``` 2. **API Settings**: ```bash az webapp config appsettings set --name mywebapp --resource-group myResourceGroup --settings \"API_KEY=your-api-key\" ``` 3. **Connection Strings**: ```bash az webapp config connection-string set --name mywebapp --resource-group myResourceGroup --settings \"DefaultConnection=Server=tcp:server.database.windows.net ```

Answer 44

**Azure Functions App Creation**: ```bash az functionapp create --resource-group myResourceGroup --name myfunctionapp --storage-account mystorage --consumption-plan-location eastus --runtime dotnet ``` **Configure Settings**: ```bash az functionapp config appsettings set --name myfunctionapp --resource-group myResourceGroup --settings \"FUNCTIONS_EXTENSION_VERSION=~4\" ```

Answer 45

**Azure Function Bindings (.NET)**: ```csharp using Microsoft.Azure.Functions.Worker; using Microsoft.Extensions.Logging; public class MyFunction { [Function(\"ProcessData\")] public static void Run( [BlobTrigger(\"input-container/{name}\", Connection = \"AzureWebJobsStorage\")] string inputBlob, [Blob(\"output-container/{name}\", Connection = \"AzureWebJobsStorage\")] out string outputBlob, ILogger log) { log.LogInformation($\"Processing blob: {inputBlob}\"); outputBlob = inputBlob.ToUpper(); } } ``` **Features**: **Blob trigger** as input, **writes to output blob**

Answer 46

**Azure Function Triggers**: 1. **Data Operations (Blob Trigger)**: ```csharp [Function(\"BlobTrigger\")] public static void Run( [BlobTrigger(\"container-name/{name}\", Connection = \"AzureWebJobsStorage\")] string myBlob, ILogger log) { log.LogInformation($\"Blob trigger processed: {myBlob}\"); } ``` 2. **Timer Trigger**: ```csharp [Function(\"TimerTrigger\")] public static void Run([TimerTrigger(\"0 */5 * * * *\")] TimerInfo myTimer, ILogger log) { log.LogInformation($\"Timer trigger executed at: {DateTime.Now}\"); } ``` 3. **Webhook (HTTP Trigger)**: ```csharp [Function(\"WebhookTrigger\")] public static IActionResult Run( [HttpTrigger(AuthorizationLevel.Function, \"post\")] HttpRequest req, ILogger log) { log.LogInformation(\"Webhook triggered.\"); return new OkResult(); } ```

Answer 47

**ACR Quick Tasks**: Simple, **one-off builds** or maintenance of container images **Usage**: ```bash az acr build --registry myregistry --image myimage:latest . ``` **Purpose**: Triggers build from current directory and pushes to ACR, ideal for **rapid testing** or **single-step image updates**

Answer 48

**ACR Automatically Triggered Tasks**: Automate image builds based on **events** (code commits, base image updates) **Configuration**: ```bash az acr task create --registry myregistry --name mytask --trigger-source git --trigger-event commit --source-location https://github.com/myrepo --image myimage:latest --cmd \"docker build -t myregistry.azurecr.io/myimage:latest .\" ``` **Benefits**: **Continuous integration** for container images on git commits

Answer 49

**ACR Multi-step Tasks**: Support complex workflows with **multiple steps** (build, test, push) **Configuration**: ```bash az acr task create --registry myregistry --name multistep-task --file multistep-task.yaml ``` **Example YAML**: ```yaml steps: - cmd: docker build -t myregistry.azurecr.io/myimage:build . - cmd: docker test myregistry.azurecr.io/myimage:build - cmd: docker push myregistry.azurecr.io/myimage:build ``` **Purpose**: **Sequential execution** of build, test, and publish steps

Answer 50

**Azure Container Registry Service Tiers**: - **Basic**: - Cost-effective **entry-level** tier - **10 concurrent builds** - No geo-replication - Suitable for **development** - **Standard**: - Enhanced performance with **20 concurrent builds** - **Geo-replication support** - Ideal for **production workloads** - **Premium**: - Highest performance with **100 concurrent builds** - **Advanced features**: content trust, private endpoints - For **large-scale, secure scenarios**

Answer 51

**ACR Tasks Use Cases**: - **Image Distribution**: Pulling images from ACR to deployment targets (Kubernetes, AKS) - **Azure Services Support**: Building and running containerized applications at scale (Container Instances, App Service) - **CI/CD Automation**: Automating image builds and deployments for **consistent, scalable, repeatable workflows**

Answer 52

**ACI Multi-container Deployment Methods**: - **ARM Template**: - Recommended for deploying **additional Azure resources** alongside containers - **Full resource management** with JSON templates - **YAML File**: - Preferred for **container instances only** deployments - **Concise format** ideal for defining container groups **Difference**: ARM templates support **broader infrastructure**, YAML is **simpler for containers alone**

Answer 53

**ACI Resource Allocation**: Resources are **summed** from all container instances in the group **Configuration**: - Specify **CPU** (e.g., 1.0), **memory** (e.g., 1.5 GB), **GPUs** (preview) - **Group total**: Two containers with 1 CPU each = **2 CPUs total** **Example YAML**: ```yaml apiVersion: 2019-12-01 properties: containers: - name: mycontainer properties: resources: requests: cpu: 1.0 memoryInGB: 1.5 ```

Answer 54

**ACI Container Group Networking**: - **Shared IP address**: All containers share **single IP** - **Port namespace**: Shared across the group - **Internal communication**: Via `localhost` on exposed ports - **External access**: Expose ports on the group's IP **Example**: ```bash az container create --resource-group myResourceGroup --name mycontainer --image mcr.microsoft.com/azuredocs/aci-helloworld --ports 80 ``` Exposes **port 80** for external access

Answer 55

**ACI Persistent Storage with Azure Files**: 1. **Create storage account and file share**: ```bash az storage account create --name mystorage$RANDOM --resource-group myResourceGroup --location eastus --sku Standard_LRS az storage share create --name acishare --account-name mystorage$RANDOM ``` 2. **Mount file share in container**: ```bash az container create --resource-group myResourceGroup --name mycontainer --image mcr.microsoft.com/azuredocs/aci-hellofiles --azure-file-volume-account-name mystorage$RANDOM --azure-file-volume-account-key $(az storage account keys list --resource-group myResourceGroup --account-name mystorage$RANDOM --query '[0].value' -o tsv) --azure-file-volume-share-name acishare --azure-file-volume-mount-path /aci/logs/ ``` **Result**: Azure file share mapped to `/aci/logs/` for **persistent data**

Answer 56

**Multi-container Group Use Cases**: - **Web application** + **logging container** to collect logs - **Application container** + **sidecar** for health monitoring or content updates **Benefits**: - **Modular, isolated workloads** - **Improved scalability** and **maintainability** - **Complex task division** into smaller container images

Answer 57

**Container Apps API Endpoints**: Deploy **RESTful services** with scalable HTTP traffic handling **Configuration**: ```bash az containerapp create --name myapiapp --resource-group myResourceGroup --image myregistry.azurecr.io/myapi:latest --environment myenvironment --target-port 8080 --ingress 'external' --min-replicas 1 --max-replicas 5 ``` **Features**: **Externally accessible** API endpoint with **scaling based on HTTP traffic**

Answer 58

**Container Apps Background Processing**: Host **long-running** or **batch jobs** (data processing) **Configuration**: ```bash az containerapp create --name mybgapp --resource-group myResourceGroup --image myregistry.azurecr.io/mybg:latest --environment myenvironment --min-replicas 1 --max-replicas 1 --ingress 'internal' ``` **Features**: Supports **background tasks** without HTTP endpoints, **continuous** or **scheduled execution**

Answer 59

**Container Apps Event-Driven Processing**: Handle events from **Azure services** (Event Grid, Event Hubs) **Configuration**: ```bash az containerapp create --name myeventapp --resource-group myResourceGroup --image myregistry.azurecr.io/myevent:latest --environment myenvironment --trigger-type eventgrid --min-replicas 0 --max-replicas 10 ``` **Features**: **Event-driven scaling** processing **blob changes** or **custom events**

Answer 60

**Container Apps Microservices**: Run **independent, loosely coupled** microservices **Configuration**: ```bash # Service 1 az containerapp create --name myservice1 --resource-group myResourceGroup --image myregistry.azurecr.io/service1:latest --environment myenvironment --target-port 80 --ingress 'external' --min-replicas 1 --max-replicas 5 # Service 2 az containerapp create --name myservice2 --resource-group myResourceGroup --image myregistry.azurecr.io/service2:latest --environment myenvironment --target-port 8080 --ingress 'external' --min-replicas 1 --max-replicas 5 ``` **Benefits**: **Independent scaling** and **HTTP communication** between services

Answer 61

"**Container Apps Scaling Options**: - **HTTP Traffic**: Scale based on **request volume** (default) - **Event-driven Processing**: Scale on **event triggers** (Event Grid, Event Hubs) - **CPU/Memory Load**: Scale on **resource utilization** using KEDA scalers - **KEDA-supported Scalers**: Use **custom metrics** via Kubernetes Event-driven Autoscaling **Configuration**: ```bash az containerapp update --name mycontainerapp --resource-group myResourceGroup --min-replicas 0 --max-replicas 10 --scale-rule \"name=http ``` **Features**: Scaling based on **HTTP concurrency** or **CPU usage > 70%**"

Answer 62

**App Service Plan**: Defines a set of **compute resources (VMs)** for one or more web apps **Benefits**: Apps share the same resources for **cost efficiency** **Creation**: ```bash az appservice plan create --name myAppServicePlan --resource-group myResourceGroup --location eastus --sku B1 ``` **Specification**: Compute capacity (e.g., **Basic tier**, **1.75 GB RAM**, **1 core**)

Answer 63

**App Service Plan Pricing Tiers**: - **Shared**: - Runs on **shared VMs** - **Limited CPU minutes** - **No scaling out** (Free, Shared tiers) - **Dedicated**: - Runs on **dedicated VMs** (Basic, Standard, Premium) - Allows **scaling** and **full resource use** - **Isolated**: - Runs on **isolated VMs** in private VNet - **High security** and compliance - **Maximum control**

Answer 64

**Free/Shared Tiers**: - Apps receive **CPU minutes** on **shared VM instance** - **Cannot scale out** - Limited to **allocated CPU time** on single shared VM **Dedicated/Isolated Tiers**: - Apps run on **all VM instances** in App Service plan - Enable **scaling out** (manual or auto-scaling) across **multiple VMs** - **Higher performance** and **availability** **Check Scaling**: ```bash az appservice plan show --name myAppServicePlan --resource-group myResourceGroup ```

Answer 65

**GitHub CI/CD Configuration**: 1. **Enable GitHub deployment**: ```bash az webapp deployment source config --name mywebapp --resource-group myResourceGroup --repo-url https://github.com/myrepo --branch main --manual-integration ``` 2. **GitHub Actions Workflow** (`.github/workflows/deploy.yml`): ```yaml name: Deploy to Azure App Service on: [push] jobs: build-and-deploy: runs-on: ubuntu-latest steps: - uses: actions/checkout@v3 - uses: azure/login@v1 with: creds: ${{ secrets.AZURE_CREDENTIALS }} - run: az webapp deploy --resource-group myResourceGroup --name mywebapp --src-path . ``` **Result**: **Automated deployment** on code pushes to GitHub

Answer 66

**Bitbucket CI/CD Configuration**: 1. **Link Bitbucket repository**: ```bash az webapp deployment source config --name mywebapp --resource-group myResourceGroup --repo-url https://bitbucket.org/myrepo --branch main --manual-integration ``` 2. **Bitbucket Pipeline** (`bitbucket-pipelines.yml`): ```yaml image: mcr.microsoft.com/appsvc/php:8.0 pipelines: default: - step: script: - az login --service-principal -u $AZURE_SP_ID -p $AZURE_SP_SECRET --tenant $AZURE_TENANT - az webapp deploy --resource-group myResourceGroup --name mywebapp --src-path . ``` **Result**: **Automated deployment** on Bitbucket commits

Answer 67

**FTP/S Manual Deployment**: 1. **Retrieve FTP credentials**: ```bash az webapp deployment list-publishing-profiles --name mywebapp --resource-group myResourceGroup --query \"[0].publishUrl\" -o tsv ``` 2. **Upload files using FTP client** or **CLI**: ```bash curl -T myapp.zip ftp://@/site/wwwroot/ --ftp-password ``` **Result**: Files uploaded to `/site/wwwroot` directory for deployment

Answer 68

**App Service on Linux Support**: - **Native Linux hosting** for common stacks (Node.js, Python, PHP, Ruby) via **built-in images** - **Custom Linux stacks** or containers (**Web App for Containers**) **Configuration**: ```bash # Built-in runtime az webapp create --resource-group myResourceGroup --name mylinuxapp --plan myAppServicePlan --runtime \"DOCKER|mcr.microsoft.com/appsvc/static:0.1\" # Custom container az webapp config container set --name mylinuxapp --resource-group myResourceGroup --docker-custom-image-name myregistry.azurecr.io/mycustomimage:latest --docker-registry-server-url https://myregistry.azurecr.io ``` **Benefits**: **Custom Linux environments** or **containerized apps**

Answer 69

**Staging Environment Exploration**: 1. **Create deployment slot**: ```bash az webapp deployment slot create --name mywebapp --resource-group myResourceGroup --slot staging ``` 2. **Deploy code to staging**: ```bash az webapp deploy --resource-group myResourceGroup --name mywebapp --slot staging --src-path myapp.zip ``` 3. **Test staging environment**: Access via URL (e.g., `mywebapp-staging.azurewebsites.net`) **Benefits**: **Isolates staging from production** for testing

Answer 70

"**Slot Swap Examination**: Verify settings and configurations **before swapping** **Preparation Steps**: - Check **slot-specific settings** (connection strings) - Ensure `slotSetting: true` for **sticky settings**: ```bash az webapp config connection-string set --name mywebapp --resource-group myResourceGroup --slot staging --settings \"DefaultConnection=Server=tcp:server.database.windows.net ``` - **Review slot contents** and **test functionality** before swapping"

Answer 71

**Deployment Slot Swapping**: ```bash az webapp deployment slot swap --name mywebapp --resource-group myResourceGroup --slot staging ``` **Process**: - Moves **staging slot content** to production - Updates production URL (`mywebapp.azurewebsites.net`) - Preserves **slot settings** if marked as `slotSetting: true`

Answer 72

**Traffic Routing with Deployment Slots**: 1. **Enable traffic routing**: ```bash az webapp traffic-routing set --name mywebapp --resource-group myResourceGroup --slot staging --percentage 20 ``` 2. **Testing**: **20% of traffic** goes to staging slot, **80%** to production **Benefits**: **Gradual rollout** and **testing in production** before full swap

Answer 73

**Consider Autoscaling When**: - Autoscaling **improves elasticity** and **fault tolerance** - Autoscaling works by **adding or removing web servers** based on load - Autoscaling **isn't best for long-term growth** (use manual scaling instead) - **Number of instances** affects scalability needs **Key Benefits**: - **Availability** - **Fault tolerance** - **Cost efficiency** by scaling dynamically based on usage

Answer 74

**Solution**: **Enable ingress** and **configure an HTTP scaling rule** **Reasoning**: - **Enabling ingress** allows external requests to reach the app - **HTTP scaling rule** ensures app scales up with incoming traffic and down to zero when idle - **Prevents downtime** by dynamically adjusting to demand **Other options** (ASE, Traffic Manager, VNet integration) don't directly enable external access or handle scaling efficiently

Answer 75

**HTTP Scaling Rule**: Automatically scales the app based on **incoming HTTP requests** **Benefits**: - **Scales up instances** when traffic increases - **Scales down to zero** when idle - **Supports external access** by ensuring app is active to handle requests - **Prevents downtime** **Ideal for**: **Cost-efficient**, **demand-driven scaling** in serverless container apps

Answer 76

**AKS Configuration**: Use **AKS Deployment Strategy with rolling update policy** and **enable horizontal pod autoscaling (HPA)** **Benefits**: - **Rolling updates** replace pods gradually, ensuring **zero downtime** - **HPA** scales pod replicas based on **CPU usage**, handling peak loads automatically - **Managed identities** enable secure **Key Vault access** without credentials **Other options** (blue-green deployment, Helm charts, single-node pools) are less efficient or don't meet **high-availability** needs

Answer 77

**Rolling Update Policy**: Updates pods **incrementally**, replacing old pods with new ones while keeping others active **Zero Downtime Process**: - **Monitors new pods' health**, halting updates if issues arise - **Ensures availability** by maintaining active pods to serve traffic during update - **Gradual replacement** prevents service interruption **Ideal for**: **High-availability apps** like payment processing microservices

Answer 78

**Configuration**: Use **Durable Functions with checkpointing enabled** and **deploy in multiple regions** **Benefits**: - **Checkpointing** saves state, ensuring **no data loss** by resuming from last checkpoint after failures - **Multi-region deployment** enables **failover** to another region during outages, minimizing downtime - **Durable Functions** manage state to process data from multiple regions **without conflicts** **Other options** (geo-replication, ASE, Event Grid) don't provide **state management** or **automatic recovery**

Answer 79

**Autoscaling Methods**: Use **schedule recurrence** and **CPU utilization** **Benefits**: - **Schedule recurrence** scales instances up during **known peak times** each month - **CPU utilization** dynamically adjusts instances for **unexpected spikes** beyond scheduled scaling - **Cost optimization**: Ensures performance during peaks and **cost efficiency** during off-peak times **Other options** (predictive algorithms, fixed instances, manual intervention) lack **flexibility** or **efficiency**

Answer 80

**Optimization Strategy**: - **Schedule recurrence**: **Proactively scales up** instances during known peak times - **CPU utilization**: **Reacts to unexpected spikes**, adding instances as load increases - **Cost efficiency**: Scales down during **off-peak periods** **Result**: **Balanced, responsive approach** for predictable traffic patterns

Answer 81

**Configuration**: Use **Azure Service Bus Queue with sessions** instead of Storage Queue **Benefits**: - **Service Bus Queues** support **sessions**, ensuring messages with same **session ID** are processed **in order** - **Guarantees FIFO** (First In, First Out) processing within each session - **Unlike Storage Queues**, which don't support ordering, Service Bus meets **strict FIFO needs** **Other options** (Storage Queue settings, Timer triggers, Logic Apps) don't ensure **FIFO**

Answer 82

**Service Bus Queue with Sessions**: - **Groups messages** by **session ID**, processing them in **sent order** - **Guarantees FIFO** within each session, critical for **sequential workflows** - **Allows parallel processing** of different sessions while **maintaining order** within each **Ideal for**: Replacing Storage Queues when **strict ordering** is required

Answer 83

**Checkpointing**: Saves the **state of a workflow** at key points during execution **Disaster Recovery Support**: - **Allows functions** to **resume from last checkpoint** after failure or outage - **Prevents data loss** by maintaining workflow state - **Supports automatic recovery** with **minimal downtime** **Essential for**: **Reliable processing** in apps like **real-time GPS data systems**

Answer 84

**Configuration**: Set up a **Premium plan** and configure function to run on **multiple instances** **Benefits**: - **Premium plan** enables **multiple instances** for **concurrent file processing** - **Enhanced performance** with increased memory and **faster cold starts** - **Fine-tuning of concurrency** for optimal throughput **Other options** (single-threaded, Event Grid, Durable Functions) don't scale as efficiently for **simple concurrency**

Answer 85

**Premium Plan with Multiple Instances**: - **Runs multiple function instances** simultaneously for **parallel file processing** - **Boosts performance** with enhanced resources and **faster scaling** - **Supports high concurrency** to handle large file workloads efficiently **Ideal for**: **Maximizing throughput** in **file-heavy applications**

Answer 86

**Service**: Use **Azure Cosmos DB with the SQL API** **Benefits**: - **Scales horizontally** to handle **high-throughput** time-series data - **SQL API** enables **efficient temporal queries** with indexing - **Supports global distribution** for **low-latency access** **Other options** (SQL Database, Data Lake, Table Storage) don't offer the same **querying efficiency** and **scalability**

Answer 87

**Azure Cosmos DB with the SQL API**: - Manages **high-throughput data** with **automatic scaling** and **global distribution** - Provides **fast temporal queries** using **SQL API** and **indexing** - Stores **large volumes** of time-series data with **low-latency access** It's ideal for **high-performance time-series applications** in Azure.

Test Flashcards

(111 cards)