|
| 1 | +### YamlMime:ModuleUnit |
| 2 | +uid: learn.wwl.manage-containers-azure-container-apps.module-assessment |
| 3 | +title: Module assessment |
| 4 | +metadata: |
| 5 | + title: Module Assessment |
| 6 | + description: Module assessment |
| 7 | + ms.date: 01/26/2026 |
| 8 | + author: jeffkoms |
| 9 | + ms.author: jeffko |
| 10 | + ms.topic: unit |
| 11 | +azureSandbox: false |
| 12 | +durationInMinutes: 5 |
| 13 | +content: | |
| 14 | +quiz: |
| 15 | + questions: |
| 16 | + - content: "You deploy a new image to a production container app. Which approach provides the best traceability and reduces the risk of deploying the wrong artifact?" |
| 17 | + choices: |
| 18 | + - content: "Reference the image by digest (for example, `myregistry.azurecr.io/app@sha256:<digest>`) when you update the container app." |
| 19 | + isCorrect: true |
| 20 | + explanation: "Digests identify an immutable image, so the deployment always uses the exact artifact you validated and approved." |
| 21 | + - content: "Reference the image by the `latest` tag to ensure the platform always pulls the most recent build." |
| 22 | + isCorrect: false |
| 23 | + explanation: "Tags like `latest` can move to a different image over time, which reduces traceability and can lead to deploying an unintended artifact." |
| 24 | + - content: "Rebuild the image locally on each environment to ensure the image matches the environment." |
| 25 | + isCorrect: false |
| 26 | + explanation: "Rebuilding in each environment can produce different artifacts and doesn't improve traceability. A single, immutable artifact is easier to audit and promote." |
| 27 | + - content: "A new revision starts but shouldn't receive traffic while you investigate. Which action removes the revision from traffic without deleting it?" |
| 28 | + choices: |
| 29 | + - content: "Run `az containerapp revision deactivate` for the revision." |
| 30 | + isCorrect: true |
| 31 | + explanation: "Deactivating a revision stops it from receiving traffic while keeping it available for inspection and later cleanup." |
| 32 | + - content: "Run `az containerapp revision delete` for the revision." |
| 33 | + isCorrect: false |
| 34 | + explanation: "Deleting removes the revision and makes investigation and comparison harder. Deactivation is the safer first step during troubleshooting." |
| 35 | + - content: "Run `az containerapp stop` for the container app." |
| 36 | + isCorrect: false |
| 37 | + explanation: "Stopping the app affects all revisions for the app and is typically too broad when the goal is to isolate one revision." |
| 38 | + - content: "A revision fails readiness checks immediately after deployment. Which issue is the most common root cause you should validate first?" |
| 39 | + choices: |
| 40 | + - content: "The readiness probe targets the wrong port or path for the container’s HTTP server." |
| 41 | + isCorrect: true |
| 42 | + explanation: "Probe misconfiguration is a frequent cause of immediate readiness failure, especially during image updates that change ports or routes." |
| 43 | + - content: "The container image is too small to include all required libraries." |
| 44 | + isCorrect: false |
| 45 | + explanation: "Image size doesn't directly determine library availability. Missing dependencies show up as application startup errors, not as a general image size issue." |
| 46 | + - content: "The container app environment can't route traffic to the public internet." |
| 47 | + isCorrect: false |
| 48 | + explanation: "Outbound routing issues can cause failures for dependency calls, but immediate readiness failures are more commonly due to probe settings or startup behavior." |
| 49 | + - content: "You suspect only one revision has a runtime exception after an update. What is the most effective first step to confirm the problem?" |
| 50 | + choices: |
| 51 | + - content: "Stream the container app logs and filter by revision while reproducing the request." |
| 52 | + isCorrect: true |
| 53 | + explanation: "Logs provide direct evidence of runtime exceptions and help you tie errors to a specific revision and time window." |
| 54 | + - content: "Delete older revisions to reduce noise in troubleshooting output." |
| 55 | + isCorrect: false |
| 56 | + explanation: "Deleting revisions removes rollback options and useful comparison points. Confirm the root cause first, then clean up later." |
| 57 | + - content: "Increase CPU and memory allocations before investigating." |
| 58 | + isCorrect: false |
| 59 | + explanation: "Resource increases can mask symptoms and increase cost. Confirm the failure mode with logs and health status first." |
| 60 | + - content: "Your AI API experiences high latency and log messages indicate CPU throttling during peak traffic. Which change most directly addresses the throttling?" |
| 61 | + choices: |
| 62 | + - content: "Increase the per-replica CPU allocation, and then reassess scaling rules based on throughput." |
| 63 | + isCorrect: true |
| 64 | + explanation: "CPU throttling indicates the replica doesn't have enough CPU for its workload. Increasing CPU per replica is a direct fix, and you can then tune scaling for cost and throughput." |
| 65 | + - content: "Deactivate the newest revision to reduce load on the system." |
| 66 | + isCorrect: false |
| 67 | + explanation: "Deactivation changes which revision receives traffic but doesn't directly resolve CPU limits if the active revision still runs underprovisioned." |
| 68 | + - content: "Switch the image reference from digest to tag." |
| 69 | + isCorrect: false |
| 70 | + explanation: "Image identity affects traceability, not runtime CPU availability." |
0 commit comments