先試後買

Explanation:
Stored access policies: # 2
Immutable blob storage policies: # 1
From the scenario in the earlier case study (A. Datum Corporation):
* The planned change requires creating a new container named cont2 in storage1, with the following:
* Three stored access policies (Stored1, Stored2, Stored3)
* A legal hold for immutable blob storage
Also, recall from the table:
* storage1 has Hierarchical namespace = Yes (Data Lake Storage Gen2 enabled).
* storage2 has Hierarchical namespace = No.
The question asks: "What is the maximum number of additional access policies you can create for cont2?" According to Microsoft Azure Storage documentation:
* A blob container can have a maximum of five stored access policies.
* These policies allow shared access signatures (SAS) to be managed centrally, letting you define start times, expiry times, and permissions at the container level.
Since three stored access policies (Stored1, Stored2, Stored3) already exist, the maximum additional policies that can still be created is:
# 5 (maximum allowed) - 3 (already existing) = 2
For immutable blob storage policies:
* A container can have one active immutability policy at a time.
* This can be either a time-based retention policy or a legal hold policy.
* Since cont2 already has a legal hold applied, no additional immutable policy can coexist with it, but it can have one defined policy type (the legal hold).
Therefore:
* Stored access policies: 2 additional policies can still be created.
* Immutable blob storage policies: 1 policy (the existing legal hold).
This aligns exactly with Microsoft Learn: Azure Storage Blob Service limits and immutable storage documentation:
"A container may have up to five stored access policies. Immutable storage supports either a time-based retention policy or legal hold policy per container." Final Verified Answer:
# Stored access policies: 2
# Immutable blob storage policies: 1

說明：（僅 NewDumps 成員可見）

Explanation:

Scenario:
1. Web administrators will deploy Azure web apps for the marketing department.
2. Each web app will be added to a separate resource group.
3. The initial configuration of the web apps will be identical.
4. The web administrators have permission to deploy web apps to resource groups.
Steps:
1 -- > Create a resource group, and then deploy a web app to the resource group.
2 -- > From the Automation script blade of the resource group , click Add to Library.
3 -- > From the Templates service, select the template, and then share the template to the web administrators .
References:
https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/quickstart-create-templates-use-the- portal

Explanation:

https://learn.microsoft.com/en-us/powershell/module/az.resources/new-azresourcegroupdeployment?
view=azps-9.3.0#-resourcegroupname
Specifies the name of the resource group to deploy.
https://learn.microsoft.com/en-us/powershell/module/az.resources/new-azresourcegroupdeployment?
view=azps-9.3.0#-mode
Specifies the deployment mode. The acceptable values for this parameter are:
-Complete: In complete mode, Resource Manager deletes resources that exist in the resource group but are not specified in the template.
- Incremental: In incremental mode, Resource Manager leaves unchanged resources that exist in the resource group but are not specified in the template.

Explanation:
Box 1 = max value
Box 2 = 20
Explanation:
Use max for platformFaultDomainCount
2 or 3 is max value, depending on which region you are in.
Use 20 for platformUpdateDomainCount
Increasing the update domain (platformUpdateDomainCount) helps with capacity and availability planning when the platform reboots nodes. A higher number for the pool (20 is max) means that fewer of their nodes in any given availability set would be rebooted at once.
References:
https://www.itprotoday.com/microsoft-azure/check-if-azure-region-supports-2-or-3-fault-domains-managed- disks
https://github.com/Azure/acs-engine/issues/1030

說明：（僅 NewDumps 成員可見）

Explanation:

Azure Storage ensures durability and high availability of data by replicating it within and/or across datacenters depending on the replication option selected. The exhibit shows that the replication type configured is Locally-redundant storage (LRS), and the access tier (default) is Hot.
1. Minimum Number of Copies - Locally-redundant storage (LRS)
According to Microsoft Azure Storage Documentation (AZ-104 Study Guide):
"Locally redundant storage (LRS) replicates your data three times (3 copies) within a single physical location in the primary region." Each piece of data is written synchronously to three separate storage nodes in the same datacenter. This provides protection against hardware failures within that facility.
Replication options and their redundancy levels:
Replication Type
Number of Copies
Location of Copies
Locally-redundant storage (LRS)
3
Same datacenter (single region)
Zone-redundant storage (ZRS)
3
Across availability zones in same region
Geo-redundant storage (GRS)
6
3 copies in primary region + 3 in paired region
Read-access geo-redundant storage (RA-GRS)
6
Same as GRS, plus read access to secondary region
Therefore, with LRS, the minimum number of copies is 3.
2. Reducing Cost of Infrequently Accessed Data
Azure Storage provides access tiers designed for different usage patterns:
Tier
Description
Typical Use Case
Hot
Highest storage cost, lowest access cost
Frequently accessed data
Cool
Lower storage cost, higher access cost
Infrequently accessed data
Archive
Lowest storage cost, highest retrieval cost
Long-term, rarely accessed data
As per Microsoft Learn - Manage access tiers in Azure Blob Storage:
"To reduce costs for data that is infrequently accessed, you can move blobs from the Hot tier to the Cool or Archive access tier." Hence, to minimize the cost of infrequently accessed data, you should modify the Access tier (default) setting from Hot to Cool or Archive.
Official Microsoft Extract:
From Microsoft Learn - Redundancy in Azure Storage:
"With LRS, three copies of your data exist in a single datacenter."
"To optimize storage costs for infrequently accessed data, set the access tier to Cool or Archive."
# Final Verified Answers:
Statement
Correct Answer
The minimum number of copies of the storage account will be:
3
To reduce the cost of infrequently accessed data in the storage account, you must modify the:

說明：（僅 NewDumps 成員可見）

說明：（僅 NewDumps 成員可見）

Explanation:

Reference:
https://docs.microsoft.com/en-us/azure/storage/files/storage-files-identity-ad-ds-assign-permissions?
tabs=azure-portal
Azure Files supports Azure Active Directory Domain Services (Azure AD DS) authentication for SMB access, allowing you to use your existing Active Directory (AD) identities and groups to control access to Azure file shares.In this scenario, the configuration snippet shows that the storage account (storage1) is using Active Directory (AD) authentication through azureFilesIdentityBasedAuthentication with directoryServiceOptions: " AD " .
According to Microsoft Azure documentation, the Storage File Data SMB Share built-in roles (Reader, Contributor, Elevated Contributor) can only be assigned to Azure AD users, groups, or service principals, not to computer objects.
Statement 1: # User1 is an on-premises AD user synchronized to Azure AD. Since Azure Files uses identity- based authentication through AD, User1 can be assigned roles like Storage File Data SMB Share Contributor to access share1.
Statement 2: # Computer1 is a computer account and cannot have Azure RBAC roles directly assigned in Azure. Therefore, you cannot assign SMB Share Reader to it.
Statement 3: # User2 is an Azure AD user (cloud-only identity). Azure RBAC roles for storage shares can also be assigned to Azure AD users. Hence, you can assign Storage File Data SMB Share Elevated Contributor to User2.

說明：（僅 NewDumps 成員可見）

說明：（僅 NewDumps 成員可見）

說明：（僅 NewDumps 成員可見）