Microsoft Azure Administrator (AZ-104) — All Questions
← Back to practice4 questions
You need storage redundancy that keeps your data available even if an entire Azure region experiences a disaster, and you want the secondary copy in a geographically distant region. Which redundancy option meets this requirement at the lowest option that qualifies?
- a.Locally redundant storage (LRS)
- b.Zone-redundant storage (ZRS)
- c.Geo-redundant storage (GRS)✓
- d.Read-access geo-redundant storage (RA-GRS)
GRS replicates data to a secondary region hundreds of miles away, protecting against a full regional outage. LRS keeps three copies in one datacenter and ZRS spreads copies across zones in a single region, so neither survives a regional disaster. RA-GRS also protects against regional failure but additionally allows read access to the secondary, which exceeds the stated need.
You must give an external partner temporary, time-limited read access to a single blob container without sharing your storage account keys. What should you generate?
- a.A shared access signature (SAS) scoped to the container✓
- b.A new storage account access key
- c.A Microsoft Entra service principal with Owner rights
- d.A CanNotDelete resource lock
A shared access signature (SAS) provides delegated access with a defined expiry time, specific permissions, and a limited scope such as a single container, without exposing account keys. Sharing an account key grants full access with no expiry. A service principal with Owner would grant far more than temporary read access.
Log files in a blob container are rarely accessed after 30 days but must be retained. You want to reduce storage cost automatically. What should you configure?
- a.Change the account redundancy from GRS to LRS
- b.Manually move blobs to a different storage account each month
- c.Enable soft delete on the container
- d.A lifecycle management policy that moves blobs to the Cool or Archive tier after 30 days✓
A blob lifecycle management policy can automatically transition blobs to the Cool or Archive access tier based on the last-modified time, lowering cost for infrequently accessed data. Soft delete protects against accidental deletion but does not reduce cost. Changing redundancy affects durability, not tiering, and manual moves are error-prone.
You want to copy a large number of files from an on-premises server to Azure Blob Storage efficiently from the command line, with high throughput and resume support. Which tool is designed for this?
- a.Azure Bastion
- b.AzCopy✓
- c.Azure Policy
- d.Network Watcher
AzCopy is a command-line utility optimized for high-performance, resumable bulk data transfer to and from Azure Blob and File storage. Azure Bastion provides secure RDP/SSH to VMs, and Network Watcher and Azure Policy serve networking diagnostics and governance respectively, not data copy.