ACI is suitable for short-lived groups but lacks the desired managed revision and HTTP autoscaling features. In this case, a continuously managed HTTP container service needs revisions and event-driven autoscaling. “Azure Container Instances for one-off jobs” would not satisfy that requirement; the supported action is “Azure Container Apps for managed revisions and scaling”. Container Apps supplies application-oriented ingress, revisions and scale rules that standalone ACI lacks.

Blob storage does not run a continuously managed HTTP microservice. In this case, a continuously managed HTTP container service needs revisions and event-driven autoscaling. “A new Azure Storage blob container” would not satisfy that requirement; the supported action is “Azure Container Apps for managed revisions and scaling”. Container Apps supplies application-oriented ingress, revisions and scale rules that standalone ACI lacks.

An individual VM does not provide managed Container Apps revision/scaling features. In this case, a continuously managed HTTP container service needs revisions and event-driven autoscaling. “An Azure VM with a manually restarted process” would not satisfy that requirement; the supported action is “Azure Container Apps for managed revisions and scaling”. Container Apps supplies application-oriented ingress, revisions and scale rules that standalone ACI lacks.

the plan's OS determines compatible application runtime and deployment options. In this case, an organization must run several related web apps on a shared set of compute resources. “The App Service plan operating system type” would not satisfy that requirement; the supported action is “An App Service plan supporting those web apps”. An App Service plan defines the compute tier and workers shared by its associated applications.

scale-out adds compute workers for horizontal capacity rather than changing the per-worker size. In this case, an organization must run several related web apps on a shared set of compute resources. “Scale out the App Service plan instance count” would not satisfy that requirement; the supported action is “An App Service plan supporting those web apps”. An App Service plan defines the compute tier and workers shared by its associated applications.

scale-up increases per-instance resources rather than adding more workers. In this case, an organization must run several related web apps on a shared set of compute resources. “Scale up the App Service plan to a larger supported SKU” would not satisfy that requirement; the supported action is “An App Service plan supporting those web apps”. An App Service plan defines the compute tier and workers shared by its associated applications.

plan tiers differ in price, scale capabilities and included App Service features. In this case, a web app needs production deployment slots and advanced scaling features. “Choose the lowest supported App Service SKU meeting its features and capacity” would not satisfy that requirement; the supported action is “Choose an App Service plan tier that supports deployment slots and required scale features”. App Service capabilities depend on plan SKU and should be checked before selecting a tier.

scale-up increases per-instance resources rather than adding more workers. In this case, a web app needs production deployment slots and advanced scaling features. “Scale up the App Service plan to a larger supported SKU” would not satisfy that requirement; the supported action is “Choose an App Service plan tier that supports deployment slots and required scale features”. App Service capabilities depend on plan SKU and should be checked before selecting a tier.

the plan's OS determines compatible application runtime and deployment options. In this case, a web app needs production deployment slots and advanced scaling features. “The App Service plan operating system type” would not satisfy that requirement; the supported action is “Choose an App Service plan tier that supports deployment slots and required scale features”. App Service capabilities depend on plan SKU and should be checked before selecting a tier.

scale-out adds compute workers for horizontal capacity rather than changing the per-worker size. In this case, a web app is experiencing CPU saturation and needs more memory per worker. “Scale out the App Service plan instance count” would not satisfy that requirement; the supported action is “Scale up the App Service plan to a larger supported SKU”. Scale-up increases per-instance resources rather than adding more workers.

the plan's OS determines compatible application runtime and deployment options. In this case, a web app is experiencing CPU saturation and needs more memory per worker. “The App Service plan operating system type” would not satisfy that requirement; the supported action is “Scale up the App Service plan to a larger supported SKU”. Scale-up increases per-instance resources rather than adding more workers.

app Service capabilities depend on plan SKU and should be checked before selecting a tier. In this case, a web app is experiencing CPU saturation and needs more memory per worker. “Choose an App Service plan tier that supports deployment slots and required scale features” would not satisfy that requirement; the supported action is “Scale up the App Service plan to a larger supported SKU”. Scale-up increases per-instance resources rather than adding more workers.

scale-up increases per-instance resources rather than adding more workers. In this case, a web application needs additional worker instances during traffic spikes. “Scale up the App Service plan to a larger supported SKU” would not satisfy that requirement; the supported action is “Scale out the App Service plan instance count”. Scale-out adds compute workers for horizontal capacity rather than changing the per-worker size.

the plan's OS determines compatible application runtime and deployment options. In this case, a web application needs additional worker instances during traffic spikes. “The App Service plan operating system type” would not satisfy that requirement; the supported action is “Scale out the App Service plan instance count”. Scale-out adds compute workers for horizontal capacity rather than changing the per-worker size.

A rule that caps the plan at one worker cannot actually add capacity during the described traffic spikes. In this case, a web application needs additional worker instances during traffic spikes. “Configure autoscale with a maximum of one worker so the plan can never add instances” would not satisfy that requirement; the supported action is “Scale out the App Service plan instance count”. Scale-out adds compute workers for horizontal capacity rather than changing the per-worker size.

scale-up increases per-instance resources rather than adding more workers. In this case, a team wants automatic scale-out when CPU exceeds a threshold. “Scale up the App Service plan to a larger supported SKU” would not satisfy that requirement; the supported action is “Autoscale rules for the eligible App Service plan”. Autoscale adjusts worker count using metrics and configured thresholds where supported.

the plan's OS determines compatible application runtime and deployment options. In this case, a team wants automatic scale-out when CPU exceeds a threshold. “The App Service plan operating system type” would not satisfy that requirement; the supported action is “Autoscale rules for the eligible App Service plan”. Autoscale adjusts worker count using metrics and configured thresholds where supported.

an App Service plan defines the compute tier and workers shared by its associated applications. In this case, a team wants automatic scale-out when CPU exceeds a threshold. “An App Service plan supporting those web apps” would not satisfy that requirement; the supported action is “Autoscale rules for the eligible App Service plan”. Autoscale adjusts worker count using metrics and configured thresholds where supported.

app Service capabilities depend on plan SKU and should be checked before selecting a tier. In this case, a web workload has low cost requirements and no need for deployment slots. “Choose an App Service plan tier that supports deployment slots and required scale features” would not satisfy that requirement; the supported action is “Choose the lowest supported App Service SKU meeting its features and capacity”. Plan tiers differ in price, scale capabilities and included App Service features.

scale-up increases per-instance resources rather than adding more workers. In this case, a web workload has low cost requirements and no need for deployment slots. “Scale up the App Service plan to a larger supported SKU” would not satisfy that requirement; the supported action is “Choose the lowest supported App Service SKU meeting its features and capacity”. Plan tiers differ in price, scale capabilities and included App Service features.

an App Service plan defines the compute tier and workers shared by its associated applications. In this case, a web workload has low cost requirements and no need for deployment slots. “An App Service plan supporting those web apps” would not satisfy that requirement; the supported action is “Choose the lowest supported App Service SKU meeting its features and capacity”. Plan tiers differ in price, scale capabilities and included App Service features.

an App Service plan defines the compute tier and workers shared by its associated applications. In this case, a web app must run under a Linux runtime rather than Windows. “An App Service plan supporting those web apps” would not satisfy that requirement; the supported action is “The App Service plan operating system type”. The plan's OS determines compatible application runtime and deployment options.

scale-up increases per-instance resources rather than adding more workers. In this case, a web app must run under a Linux runtime rather than Windows. “Scale up the App Service plan to a larger supported SKU” would not satisfy that requirement; the supported action is “The App Service plan operating system type”. The plan's OS determines compatible application runtime and deployment options.

app Service capabilities depend on plan SKU and should be checked before selecting a tier. In this case, a web app must run under a Linux runtime rather than Windows. “Choose an App Service plan tier that supports deployment slots and required scale features” would not satisfy that requirement; the supported action is “The App Service plan operating system type”. The plan's OS determines compatible application runtime and deployment options.

an App Service plan defines the compute tier and workers shared by its associated applications. In this case, several apps share one plan and one app consumes nearly all CPU. “An App Service plan supporting those web apps” would not satisfy that requirement; the supported action is “Shared plan workers can cause resource contention across the apps”. Apps on the same worker plan compete for the plan's allocated compute capacity.

the plan's OS determines compatible application runtime and deployment options. In this case, several apps share one plan and one app consumes nearly all CPU. “The App Service plan operating system type” would not satisfy that requirement; the supported action is “Shared plan workers can cause resource contention across the apps”. Apps on the same worker plan compete for the plan's allocated compute capacity.

scale-up increases per-instance resources rather than adding more workers. In this case, several apps share one plan and one app consumes nearly all CPU. “Scale up the App Service plan to a larger supported SKU” would not satisfy that requirement; the supported action is “Shared plan workers can cause resource contention across the apps”. Apps on the same worker plan compete for the plan's allocated compute capacity.

Domain verification alone does not enable HTTPS for the custom hostname. In this case, a web app needs HTTPS for a hostname owned by the company. “A DNS TXT verification record without any TLS certificate binding” would not satisfy that requirement; the supported action is “A custom domain binding and appropriate TLS certificate binding”. HTTPS on a custom name requires ownership mapping plus a valid certificate and TLS binding.

Enforcing HTTPS cannot fix an invalid or absent TLS binding for the hostname. In this case, a web app needs HTTPS for a hostname owned by the company. “HTTPS Only setting without a valid custom-domain certificate” would not satisfy that requirement; the supported action is “A custom domain binding and appropriate TLS certificate binding”. HTTPS on a custom name requires ownership mapping plus a valid certificate and TLS binding.

An NSG does not configure the App Service certificate for the public hostname. In this case, a web app needs HTTPS for a hostname owned by the company. “An NSG rule allowing TCP 443 to a backend VM” would not satisfy that requirement; the supported action is “A custom domain binding and appropriate TLS certificate binding”. HTTPS on a custom name requires ownership mapping plus a valid certificate and TLS binding.

hTTPS on a custom name requires ownership mapping plus a valid certificate and TLS binding. In this case, a certificate for an App Service custom hostname is expiring. “A custom domain binding and appropriate TLS certificate binding” would not satisfy that requirement; the supported action is “The TLS certificate bound to that hostname”. Certificate validity and binding determine whether clients trust the custom-domain HTTPS endpoint.

clients validate that the certificate covers the host name presented in the URL. In this case, a certificate for an App Service custom hostname is expiring. “The custom domain TLS binding and certificate subject names” would not satisfy that requirement; the supported action is “The TLS certificate bound to that hostname”. Certificate validity and binding determine whether clients trust the custom-domain HTTPS endpoint.

a minimum TLS version rejects older client protocol negotiations while HTTPS policy enforces encrypted requests. In this case, a certificate for an App Service custom hostname is expiring. “App Service minimum TLS version and HTTPS enforcement” would not satisfy that requirement; the supported action is “The TLS certificate bound to that hostname”. Certificate validity and binding determine whether clients trust the custom-domain HTTPS endpoint.