Confusing which slot settings follow a swap
The wrong answers move settings that stay put and pin settings that travel. Custom domain names are slot specific and stay in the same slot after a swap, as do scale settings, publishing endpoints and virtual network integration. Language framework version, the 32-bit versus 64-bit platform setting, WebSockets, handler mappings, public certificates and path mappings are swapped and follow the content into production. Treating a custom domain as swapped, or handler mappings as pinned, reverses the rule.
See it in a sample questionUsing scale out to change tier or isolate apps
The wrong answers reach for more instances when the problem is the tier or the plan. Scaling out adds instances of the same tier, so it does not unlock deployment slots, which need the Standard, Premium or Isolated tier. Autoscale changes the instance count for the whole plan, and apps in one plan still share those VM instances. Isolation needs a separate App Service plan. The Free tier cannot scale out at all, because it runs on a shared instance.
See it in a sample questionAttributing a container feature to the wrong service or tier
Each wrong answer credits a container feature to the wrong service, tier or capability. Geo-replication is a Premium Azure Container Registry feature, so it is not added to Basic or Standard by attaching a region, and it is not a Container Apps capability. Webhooks, geo-replication and content trust do not rebuild images; registry tasks do when a base image is updated. Per-second billing and exact CPU and memory sizing belong to Azure Container Instances, and registry tiers belong to the registry.
See it in a sample questionAssuming default encryption covers the temporary disk
The wrong answers credit default Azure Storage encryption with covering the VM temporary disk, or offer an in-guest or storage-layer option where encryption must start on the VM host. Server-side encryption covers managed OS and data disks at rest, but the temporary disk is not a managed disk. Azure Disk Encryption works inside the guest with BitLocker or DM-Crypt, and double encryption adds a second layer at the storage level. Encryption at host starts on the server hosting the VM, so the temporary disk and caches are encrypted without using VM CPU.
See it in a sample questionTreating orchestration mode as adjustable
The wrong answers offer a setting or a rule that would change a scale set's orchestration mode after creation. No such setting exists: the mode is defined when the scale set is created and cannot be changed or updated later. A Uniform scale set that now needs standard IaaS VMs, or mixed Linux and Windows instances, must be replaced by a new Flexible one. An autoscale rule cannot switch the mode, and the mode does not decide which in-guest counters autoscale can read.
See it in a sample question