AZ-104 RENEWAL PRACTICE TEST 2026
QUESTIONS WITH SOLUTIONS GRADED A+
⩥ Storage account Access Keys. Answer: The "master keys" to the entire
account (all services). Powerful, simple, high risk if leaked.
⩥ Storage account SAS (Shared Access Signature). Answer: Time-
boxed, scope-limited tokens derived from a key or an identity. Designed
for least privilege and safe sharing.
⩥ Storage account preferred access methods. Answer: Microsoft Entra
ID + Role-based access control for applications.
Use SAS for temporary, delegated access.
Keep Access Keys off-limits except for narrow cases.
⩥ Stored Access Policies (SAPs). Answer: Let you centrally control
SAS permissions and expiry at different levels such as the container
level.
⩥ For storage accounts If a container-level immutability policy (time -
based retention or legal hold) is in effect, the data is? Answer: WORM
(write once, read many): no overwrite or delete is allowed.
⩥ Storage account Access tiers Answer: Online: Hot, Cool, and Cold
,Offline: Archive with rehydration of Standard (hours) or High (less than
1 hour for small objects)
⩥ Hot Access Tier Answer: Highest storage price, lowest access &
transaction cost, lowest latency. Choose for frequently read/ updated
data (web assets, active logs, app data ).
⩥ Cool Access Tier Answer: Lower storage price, higher read/ operation
cost. Good for infrequent access (recent backups, warm archives). 30-
day minimum: delete/ overwrite/ move earlier ⇒ early-deletion charge
⩥ Cold Access Tier Answer: Lower storage price than Cool, but higher
retrieval/ transaction cost. Good for data you rarely touch but still need
online. 90-day minimum with early-deletion charge if violated.
⩥ Archive Access Tier Answer: Lowest storage price, must rehydrate to
Hot/ Cool/ Cold before read/ write. 180-day minimum.
⩥ Storage Data Redundancy Answer: Azure Storage keeps multiple
copies of your data to survive hardware, zonal, or even regional failures
⩥ Where can extra storage copied be replicated to? Answer: • Within
one datacenter
• Across zones in a region
• Across regions
, ⩥ Storage Account redundancy options Answer: LRS (Locally
Redundant Storage)
ZRS (Zone-Redundant Storage)
GRS (Geo-Redundant Storage)
RA-GRS (Read-Access GRS)
GZRS (Geo-Zone-Redundant Storage)
RA-GZRS (Read-Access GZRS)
⩥ LRS (Locally Redundant Storage) Answer: 3 copies within a single
datacenter in the chosen region. Dev/test, low-criticality data, or when
compliance requires single-region only.
⩥ ZRS (Zone-Redundant Storage) Answer: Synchronous copies across
3+ availability zones in the same region. Survives a zonal outage with
no data loss.
⩥ GRS (Geo-Redundant Storage) Answer: Writes synchronously like
LRS in the primary region, then asynchronously replicates to a paired
secondary region. Disaster recovery across regions.
⩥ RA-GRS (Read-Access GRS) Answer: Same as GRS plus read access
to secondary endpoints. You want active -read DR—query the secondary
for analytics, reduce the pressure on the primary endpoint.
QUESTIONS WITH SOLUTIONS GRADED A+
⩥ Storage account Access Keys. Answer: The "master keys" to the entire
account (all services). Powerful, simple, high risk if leaked.
⩥ Storage account SAS (Shared Access Signature). Answer: Time-
boxed, scope-limited tokens derived from a key or an identity. Designed
for least privilege and safe sharing.
⩥ Storage account preferred access methods. Answer: Microsoft Entra
ID + Role-based access control for applications.
Use SAS for temporary, delegated access.
Keep Access Keys off-limits except for narrow cases.
⩥ Stored Access Policies (SAPs). Answer: Let you centrally control
SAS permissions and expiry at different levels such as the container
level.
⩥ For storage accounts If a container-level immutability policy (time -
based retention or legal hold) is in effect, the data is? Answer: WORM
(write once, read many): no overwrite or delete is allowed.
⩥ Storage account Access tiers Answer: Online: Hot, Cool, and Cold
,Offline: Archive with rehydration of Standard (hours) or High (less than
1 hour for small objects)
⩥ Hot Access Tier Answer: Highest storage price, lowest access &
transaction cost, lowest latency. Choose for frequently read/ updated
data (web assets, active logs, app data ).
⩥ Cool Access Tier Answer: Lower storage price, higher read/ operation
cost. Good for infrequent access (recent backups, warm archives). 30-
day minimum: delete/ overwrite/ move earlier ⇒ early-deletion charge
⩥ Cold Access Tier Answer: Lower storage price than Cool, but higher
retrieval/ transaction cost. Good for data you rarely touch but still need
online. 90-day minimum with early-deletion charge if violated.
⩥ Archive Access Tier Answer: Lowest storage price, must rehydrate to
Hot/ Cool/ Cold before read/ write. 180-day minimum.
⩥ Storage Data Redundancy Answer: Azure Storage keeps multiple
copies of your data to survive hardware, zonal, or even regional failures
⩥ Where can extra storage copied be replicated to? Answer: • Within
one datacenter
• Across zones in a region
• Across regions
, ⩥ Storage Account redundancy options Answer: LRS (Locally
Redundant Storage)
ZRS (Zone-Redundant Storage)
GRS (Geo-Redundant Storage)
RA-GRS (Read-Access GRS)
GZRS (Geo-Zone-Redundant Storage)
RA-GZRS (Read-Access GZRS)
⩥ LRS (Locally Redundant Storage) Answer: 3 copies within a single
datacenter in the chosen region. Dev/test, low-criticality data, or when
compliance requires single-region only.
⩥ ZRS (Zone-Redundant Storage) Answer: Synchronous copies across
3+ availability zones in the same region. Survives a zonal outage with
no data loss.
⩥ GRS (Geo-Redundant Storage) Answer: Writes synchronously like
LRS in the primary region, then asynchronously replicates to a paired
secondary region. Disaster recovery across regions.
⩥ RA-GRS (Read-Access GRS) Answer: Same as GRS plus read access
to secondary endpoints. You want active -read DR—query the secondary
for analytics, reduce the pressure on the primary endpoint.
