Explanation:

Box 1: Zone-redundant storage (ZRS)
Zone-redundant storage (ZRS) replicates your data synchronously across three storage clusters in a single region.
LRS would not remain available if a data center in the region fails
GRS and RA GRS use asynchronous replication.
Box 2: StorageV2 (general purpose V2)
ZRS only support GPv2.
References:
https://docs.microsoft.com/en-us/azure/storage/common/storage-redundancy
https://docs.microsoft.com/en-us/azure/storage/common/storage-redundancy-zrs

Explanation:

" A resource can only be created in a virtual network that exists in the same region and subscription as the resource. " https://learn.microsoft.com/en-us/azure/virtual-network/virtual-network-vnet-plan-design- arm#regions

This question focuses on creating guest user accounts (B2B users) in Azure Active Directory (Microsoft Entra ID) using bulk operations. The requirement is to import 500 external users from a CSV file and invite them as guest users into the tenant contoso.com.
# Understanding the Goal
You must create guest accounts (B2B collaboration users) - not regular internal users.
Guest accounts in Azure AD have:
UserType = Guest
Their identity originates from an external organization (using their own email domain).
They are invited via B2B invitations.
The key operation used to accomplish this is Bulk invite users, not Bulk create users.
# Why "Bulk Create Users" Does NOT Meet the Goal
The Bulk create users operation in the Azure portal is used for adding internal users to the directory (i.e., users who belong to the same Azure AD tenant).
It creates standard member accounts, not guest accounts.
It cannot send invitations to external users or create guest-type identities (UserType = Guest).
In contrast:
The Bulk invite users operation imports external user data from a CSV file and automatically sends invitations to the listed email addresses.
It creates user objects with UserType = Guest in Azure AD, meeting the scenario's goal.
Hence, the Bulk create user method fails to create guest users and does not meet the goal.
# Correct Method (for Reference)
From Microsoft Entra ID # Users # Bulk operations # Bulk invite, you can:
Download a CSV template.
Fill in external users' names and email addresses.
Upload the CSV file.
Azure AD then creates guest user accounts and sends invitations to join the directory.
This is the only correct approach for mass-adding external (guest) users.
# Verified Documentation Extract (Microsoft Learn)
"The Bulk invite operation in Azure AD allows administrators to invite multiple external users at once by uploading a CSV file. Bulk create operation, on the other hand, is for adding internal users to your organization's directory." (Source: Microsoft Learn - Invite external users in bulk to Microsoft Entra ID, AZ-104 Study Guide)
# Final Verified Answer:
B). No
Using the Bulk create users operation adds internal member accounts, not external guest accounts. To create guest accounts, the correct action is to use the Bulk invite users operation in Azure AD.

Explanation:

Azure Blob Storage Lifecycle Management enables you to automatically transition data to cooler storage tiers, archive data, or delete data based on specified conditions related to creation, last modification, or last access time. These policies are defined in a JSON-based rule structure under the rules property.
As per Microsoft Azure Administrator Study Guide and Official Documentation ("Manage the Azure Blob storage lifecycle"), each rule must define:
Actions: What operation to perform (e.g., tierToCool, tierToArchive, delete).
Filters: Which objects (blobs) the rule applies to, typically filtered by container name, prefix, or blob type.
Conditions: When to perform the action, defined by properties such as:
" daysAfterCreationGreaterThan " - Number of days since blob creation.
" daysAfterLastAccessTimeGreaterThan " - Number of days since last read operation (used when last access tracking is enabled).
" daysAfterModificationGreaterThan " - Number of days since last modification (used for update or write operations).
According to the scenario, the requirement is to move blobs that were not updated for 45 days. The "not updated" condition refers to the last modification date, not creation or access date. Therefore, the correct property to use is:
" daysAfterModificationGreaterThan " : 45
The blob type must be specified under " filters " . Azure Lifecycle Management currently supports lifecycle actions for:
BlockBlob - the primary type for uploaded files.
AppendBlob - supported, but typically used for log data.
PageBlob - not supported for lifecycle tiering (used for virtual machine disks).
Per Microsoft Docs - "Lifecycle management policy definition", lifecycle tiering actions (tierToCool or tierToArchive) only apply to BlockBlob and AppendBlob, with BlockBlob being the standard choice for data that benefits from tier transitions between Hot, Cool, and Archive tiers.
Hence, the correct configuration is:
" tierToCool " : {
" daysAfterModificationGreaterThan " : 45
}
" blobTypes " : [
" BlockBlob "
]
This policy automatically transitions block blobs in container1 to the Cool access tier when they have not been modified for 45 days, optimizing storage cost while retaining availability.