Treating key-signed SAS tokens as Entra-secured
The wrong answers treat a service SAS or an account SAS as if Microsoft Entra credentials secured it. Both are signed with the storage account key, so the app needs that key to create them, and rotating the key revokes them. Only a user delegation SAS is secured with Microsoft Entra credentials, which is why it is the recommended type and why it keeps working after key rotation.
See it in a sample questionCrediting a redundancy option with protection it lacks
Each wrong answer gives a redundancy option protection it does not offer. LRS keeps every replica in one physical datacenter, so a fire or flood at that site can lose all of them. ZRS spreads copies across availability zones inside the primary region but has no secondary region, so it cannot offer secondary read access. Only the geo options replicate to a second region, and only the read-access geo options expose a secondary endpoint.
See it in a sample questionApplying a protection feature to the wrong object or level
Blob soft delete restores an individual blob, snapshot or version, so it cannot bring back a deleted container; that needs container soft delete, and versioning does not recover a container either. With versioning enabled, deleting a blob turns the current version into a previous version instead of starting the soft delete retention period. File share soft delete is set at the storage account level and applies to every share in the account.
See it in a sample questionAttaching a retention figure to the wrong feature
The wrong options swap numbers between unrelated settings. The archive tier has a minimum of 180 days, the cool tier 30 days and the cold tier 90 days, and these are early deletion thresholds. The figure of 365 days is the maximum soft delete retention period, not an archive minimum, and 180 days is not a soft delete ceiling.
See it in a sample questionCrediting an AzCopy command with another command's job
Each AzCopy command gets a job it does not do. Sync replicates the source to the destination so the destination matches it, yet it does not rename files, and AzCopy has no rename command. Copy transfers data without deleting destination items that are absent from the source. Make only creates a container or file share, and remove only deletes. Set-properties changes access tier, metadata and index tags, not file names.
See it in a sample question