Fundamental
Prepare and test your skills
Fundamental
Prepare and test your skills
Automatic Hot to Cool Blob Tiering With Lifecycle Rules
Free sample question, answered and explained below. The AZ-900 Microsoft Azure Fundamentals Exam practice bank has 688 more like it. Try 10 free: instant score, no account.
An organization stores large volumes of operational logs in Azure Blob Storage in the Hot access tier. The logs are frequently queried during the first 30 days after creation, but access drops significantly afterward.
To optimize storage costs while avoiding manual administrative effort, the organization wants to automatically move any log files that have not been modified or accessed for more than 30 days to the Cool tier.
Which feature should the organization configure to meet this requirement?
Explanations
Azure Resource Manager resource locks
Azure Resource Manager resource locks
What Azure Resource Manager Locks Are
Azure Resource Manager (ARM) resource locks are management safeguards applied at the subscription, resource group, or resource level to prevent accidental modification or deletion of Azure infrastructure components.
Why It Doesn't Meet the Requirement
- Management Plane Constraint: Resource locks prevent administrative operations like deleting a storage account (
CannotDelete) or changing account settings (ReadOnly). - No Data-Level Intelligence: Locks do not monitor individual blob objects, evaluate data access patterns, or perform automated data tiering.
Key Characteristics and Limitations
- Two Lock Types: Available exclusively as
ReadOnlyorDeletelocks. - Infrastructure Scope: Applies broadly to management operations rather than individual blob objects stored inside containers.
- Static Protection: Locks remain in place until explicitly removed by an authorized administrator.
This Answer Would Be Correct If
The organization wanted to prevent administrators and automated scripts from accidentally deleting an entire storage account or resource group.
Shared Access Signature (SAS) expiration policies
Shared Access Signature (SAS) expiration policies
What SAS Expiration Policies Are
Shared Access Signature (SAS) expiration policies are security and governance controls that enforce validity boundaries on delegated access tokens. These policies define the maximum allowable lifetime for SAS tokens generated to access Azure Storage resources.
Why It Doesn't Meet the Requirement
- Security vs. Storage Management: SAS expiration policies manage delegated authorization and access control lifetimes, not the underlying storage tier of the data.
- No Data Movement: SAS policies have no ability to inspect data modification dates or move blobs between access tiers.
Key Characteristics and Limitations
- Token Lifetime Limits: Restricts how long a generated token remains valid for client authentication.
- Compliance Governance: Integrated with Azure Policy to audit or flag storage accounts that lack recommended SAS expiration limitations.
- Access Scope: Governs service-level and account-level SAS credentials rather than blob storage optimization.
This Answer Would Be Correct If
The organization needed to enforce a maximum token lifespan on generated access URLs to ensure delegated security credentials expire after a specific time period.
Azure Backup operational policies
Azure Backup operational policies
What Azure Backup Operational Policies Are
Azure Backup operational policies are data protection mechanisms configured within a Backup vault to safeguard data against accidental deletion, corruption, or ransomware. They govern operational backups for storage accounts by utilizing features such as blob versioning, soft delete, and point-in-time restore.
Why It Doesn't Meet the Requirement
- Purpose Mismatch: Azure Backup focuses on recovery points, retention schedules, and data resilience rather than moving live data across storage access tiers.
- No Tiering Actions: Operational backup policies do not evaluate days since modification or access to transition active block blobs between Hot, Cool, and Archive tiers.
Key Characteristics and Limitations
- Protection-Centric: Designed exclusively for backup, snapshot recovery, and disaster recovery scenarios.
- Applies Locks: Can place Delete Locks on storage accounts to prevent unintentional removal of storage infrastructure.
- Retention Enforcement: Configures soft delete duration and point-in-time restore windows rather than cost-optimization tier transitions.
This Answer Would Be Correct If
The organization needed to implement automated point-in-time restoration capabilities and protect blob data from accidental deletion or malicious modification.
Azure Blob Storage lifecycle management
Azure Blob Storage lifecycle management
What Azure Blob Storage Lifecycle Management Is
Azure Blob Storage lifecycle management is a built-in feature that offers a rule-based policy engine for managing the lifecycle of your data. It allows administrators to define automated rules using conditions and actions to manage data progression across different access tiers or delete expired data.
How It Meets the Requirement
- Automated Tier Transitions: Lifecycle management rules can evaluate criteria such as creation time, last modified time, or last access time.
- Policy Enforcement: By setting a condition to check if blobs have not been modified or accessed for greater than 30 days, the policy automatically applies the
tierToCoolaction without requiring custom scripts or manual tasks. - Targeted Scope: The policy can be scoped to entire storage accounts, specific containers, or defined blob prefixes (such as log directories).
Key Advantages and Capabilities
- Cost Optimization: Reduces overall storage expenses by placing aging data in lower-cost storage tiers such as Cool or Archive.
- Zero Overhead: Native automated execution eliminates the need to develop, host, and maintain custom background jobs or automation runbooks.
- Reversible Automation: Supports bi-directional tiering capabilities, such as automatically returning data from Cool to Hot when accessed if configured.
- No Added Platform Cost: The lifecycle management policy feature itself is free of charge.
Why This Is Optimal
Lifecycle management provides the exact native rule-based automation needed to evaluate blob age and access patterns, seamlessly transitioning data to cost-efficient tiers without manual intervention.
Try 10 interactive questions like this one, free
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
- 688 practice questions across all 3 exam domains
- Every answer explained: why it is right, and why the others are not
- Scout, an AI tutor that answers your follow-up questions
- Readiness tracking by domain, so you know when to book the exam
Related questions
Keep the momentum going with these hand-picked practice scenarios
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Storage Encryption at Rest
Describe storage tiers
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure File Sync Cloud Tiering
Describe storage tiers
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Blob Archive Tier
Describe storage tiers
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Blob Storage Archive Tier
Describe storage tiers
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Site Recovery
Describe the benefits of reliability and predictability in the cloud
AdvancedAZ-104 Microsoft Azure Administrator Exam
Availability Zones High Availability
Deploy virtual machines to availability zones and availability sets
Last updated Validated