Placing billing and policy at the wrong level
The wrong answers put a boundary at whichever level sounds closest. A resource group is offered as the invoice unit, a single resource as the access boundary, and a management group as the billing unit. Azure generates separate invoices per subscription and applies access-management policies at the subscription level. Management groups sit above subscriptions and push inherited governance down to them. A resource group lives inside one subscription, so it cannot sit above subscriptions in the hierarchy.
See it in a sample questionSwapping VPN Gateway, ExpressRoute and peering
The wrong answers trade the network links for one another. Peering joins two Azure virtual networks on the Microsoft backbone, so it cannot reach an on-premises datacentre. A site-to-site VPN gateway wraps traffic in an encrypted tunnel that still crosses the public internet. ExpressRoute reaches Azure through a connectivity provider and bypasses the public internet, so it suits a private, consistently low-latency circuit. A point-to-site VPN connects single client devices, not a whole datacentre.
See it in a sample questionOverstating what each redundancy option protects
The wrong answers treat any replicated option as protection against every failure. LRS keeps three copies in one datacentre. ZRS spreads copies across three availability zones in the primary region, so a zone outage leaves reads and writes working. GRS replicates to a distant secondary region but uses a single datacentre locally, and that secondary is not readable until failover unless RA-GRS is enabled. GZRS combines zone spread with geo-replication.
See it in a sample questionReaching for the wrong data-transfer tool
The wrong answers pick a tool that sounds right but does not fit the transfer. AzCopy is a command-line copier whose synchronize option runs one way and depends on the network link. Azure File Sync keeps a Windows file server synced in both directions with Azure Files and supports cloud tiering. Azure Data Box ships an appliance of up to 80 TB for a one-off offline load. Azure Storage Explorer is a graphical app that uses AzCopy on the backend, and Azure Migrate assesses and migrates servers.
See it in a sample questionConfusing sign-in decisions with resource permissions
The wrong answers give one control the job of another. Conditional Access works at sign-in, weighing signals such as user, location and device to allow, block or challenge for multifactor authentication. Azure RBAC works after authentication, granting permissions at a scope that Azure Resource Manager enforces. Single sign-on only reuses one sign-in across trusted apps. Authorisation decides what a verified identity may do, and it follows authentication, which only establishes who is making the request.
See it in a sample question