You have an Azure subscription that contains the devices shown in the following table.On which devices can you install Azure Storage Explorer?
Answer(s): D
Microsoft Azure Storage Explorer is a standalone app that makes it easy to work with Azure Storage data on Windows, macOS, and Linux.
https://learn.microsoft.com/en-us/azure/vs-azure-tools-storage-manage-with-storage-explorer
HOTSPOT (Drag and Drop is not supported)You have an Azure Storage account named storage1 that contains a container named container1. The container1 container stores thousands of image files.You plan to use an Azure Resource Manager (ARM) template to create a blob inventory rule named rule1.You need to ensure that only blobs whose names start with the word finance are stored daily as a CSV file in container1.How should you complete rule1? To answer, select the options in the answer area.NOTE: Each correct answer is worth one point.Hot Area:
Answer(s): A
Box 1: blockBlobBlock blobs are optimized for uploading large amounts of data efficiently. Block blobs are composed of blocks, each of which is identified by a block ID. A block blob can include up to 50,000 blocks. Each block in a block blob can be a different size, up to the maximum size permitted for the service version in use.Block blobs include features that help you manage large files over networks. With a block blob, you can upload multiple blocks in parallel to decrease upload time.Incorrect:append blobAn append blob is composed of blocks and is optimized for append operations. When you modify an append blob, blocks are added to the end of the blob only, via the Append Block operation. Updating or deleting of existing blocks is not supported. Unlike a block blob, an append blob does not expose its block IDs.Page blobs are a collection of 512-byte pages optimized for random read and write operations.Box 2: container1/financeprefixMatch - An array of strings for prefixes to be match.The blob prefix match string didn't apply the policy to the expected blobsThe blob prefix match field of a policy is a full or partial blob path, which is used to match the blobs you want the policy actions to apply to. The path must start with the container name. If no prefix match is specified, then the policy will apply to all the blobs in the storage account. The format of the prefix match string is [container name]/[blob name].Keep in mind the following points about the prefix match string:A prefix match string like container1/ applies to all blobs in the container named container1. A prefix match string of container1, without the trailing forward slash character (/), applies to all blobs in all containers where the container name begins with the string container1. The prefix will match containers named container11, container1234, container1ab, and so on.A prefix match string of container1/sub1/ applies to all blobs in the container named container1 that begin with the string sub1/. For example, the prefix will match blobs named container1/sub1/test.txt or container1/sub1/ sub2/test.txt.
https://learn.microsoft.com/en-us/azure/templates/microsoft.storage/storageaccounts/managementpolicies https://learn.microsoft.com/en-us/azure/storage/blobs/storage-blob-faqhttps://learn.microsoft.com/en-us/rest/api/storageservices/understanding-block-blobs--append-blobs--and- page-blobs
HOTSPOT (Drag and Drop is not supported)You have an Azure subscription that contains a storage account named storage1. The storage1 account contains blobs in a container named container1.You plan to share access to storage1.You need to generate a shared access signature (SAS). The solution must meet the following requirements: Ensure that the SAS can only be used to enumerate and download blobs stored in container1.Use the principle of least privilege.Which three settings should you enable? To answer, select the appropriate settings in the answer area.Hot Area:
Box 1: Allowed resource type: Container Blob serviceThe following table lists Blob service operations and indicates which signed resource type and signed permissions to specify when you delegate access to those operations.Box 2: Allowed resource type: Object Box 3: Allowed permissions: ReadRead (r): Valid for all signed resources types (Service, Container, and Object). Permits read permissions to the specified resource type.Incorrect:* Allowed permissions: ListList (l): Valid for Service and Container resource types only.Note:Blob serviceThe following table lists Blob service operations and indicates which signed resource type and signed permissions to specify when you delegate access to those operations.
https://learn.microsoft.com/en-us/answers/questions/67751/azure-sas-terms https://learn.microsoft.com/en-us/rest/api/storageservices/create-account-sas¨
HOTSPOT (Drag and Drop is not supported)You have an Azure subscription. The subscription contains a storage account named storage1 that has the lifecycle management rules shown in the following table.On June 1, you store two blobs in storage1 as shown in the following table.For each of the following statements, select Yes if the statement is true. Otherwise, select No.NOTE: Each correct selection is worth one point.Hot Area:
Box 1: NoAt June 4 Rule1 applied and File1 was moved to archive storage.At June 6 Rule2, move to cool storage, was not applied as File1 already is in archive storage.Note: If you define more than one action on the same blob, lifecycle management applies the least expensive action to the blob. For example, action delete is cheaper than action tierToArchive. Action tierToArchive is cheaper than action tierToCool.Box 2: YesOn June1 File2 is in container2. The Access tier is hot.On June4 Rule2 applies and File2 is moved to cool storage. File2 is in the Cool Access tier on June 7.On June 7 no rule applies to File2, and it would be stored in the Hot tier. Box 3: NoOn June6 File2 would be moved to the cool storage by Rule2. One June11 File2 would be deleted by Rule3.
https://learn.microsoft.com/en-us/azure/storage/blobs/lifecycle-management-overview
HOTSPOT (Drag and Drop is not supported)You have an Azure Storage account named contoso2024 that contains the resources shown in the following table.You have users that have permissions for contoso2024 as shown in the following table.The contoso2024 account is configured as shown in the following exhibit.For each of the following statements, select Yes if the statement is true. Otherwise, select No.NOTE: Each correct selection is worth one point.Hot Area:
Box 1: YesYes - User1 has the Reader role.The Reader role is an Azure Resource Manager role that permits users to view storage account resources, but not modify them. It does not provide read permissions to data in Azure Storage, but only to account management resources. The Reader role is necessary so that users can navigate to blob containers in the Azure portal.Box 2: NoNo - User2 can read File2.User2 has a Storage Account Contributor role for constoso2024. We see: Allow storage account key access: DisabledNote: Storage Account ContributorPermits management of storage accounts. Provides access to the account key, which can be used to access data via Shared Key authorization.Box 3: NoNo - User3 can read File1 and file2.User3 has an access key for contoso2024.We see: Allow storage account key access: Disabled
https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles
HOTSPOT (Drag and Drop is not supported)You have an Azure subscription linked to a hybrid Microsoft Entra tenant. The tenant contains the users shown in the following table.You create the Azure Files shares shown in the following table.You configure identity-based access for contoso2024 as shown in the following exhibit.For each of the following statements, select Yes if the statement is true. Otherwise, select No.NOTE: Each correct selection is worth one point.Hot Area:
Box 1: NoNo - User1 can access the content on share1. On-premises sync is not enabled for User1.Box 2: YesYes - User2 can access the content on share2.On-premises sync is enabled for User2 Share2 is defined in contoso2024.contoso2024 is enabled as an Active Directory source.Box 3: NoNo - User2 can access the content on share3.On-premises sync is enabled for User2 Share2 is defined in contoso2025.As far as we know contoso2025 is not enabled as an Active Directory source.
https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/how-to-connect-sync-whatis
HOTSPOT (Drag and Drop is not supported)Your network contains an on-premises Active Directory Domain Services (AD DS) domain. The domain contains the identities shown in the following table.You have an Azure subscription that contains a storage account named storage1. The file shares in storage1 have an identity source of AD DS and Default share-level permissions set to Enable permissions for all authenticated users and groups.You create an Azure Files share named share1 that has the roles shown in the following table.You have a Microsoft Entra tenant that contains a cloud-only user named User3.You use Microsoft Entra Connect to sync OU1 from the AD DS domain to the Microsoft Entra tenant. For each of the following statements, select Yes if the statement is true. Otherwise, select No.NOTE: Each correct selection is worth one point.Hot Area:
Box 1: YesYes - User1 can access content in share1.User1 is in OU2.OU2 is not synced to the on-premises Active Directory Domain Services (AD DS) domain. However, User1 is member of Group1.Group1 is member of OU1.OU1 is synced to the on-premises Active Directory Domain Services (AD DS) domain.So, User1 is synced to the on-premises Active Directory Domain Services (AD DS) domain.Box 2: YesYes - User2 can access content in share1.User2 is in OU1.OU1 is synced to the on-premises Active Directory Domain Services (AD DS) domain.Box 3: NoNo - User3 can access content in share1.User3 is not member of OU2. User3 is not member of Group1.
You have an Azure subscription that contains the storage accounts shown in the following table.Which storage account can be converted to zone-redundant storage (ZRS) replication?
ZRS currently supports standard general-purpose v2, FileStorage and BlockBlobStorage storage account types.Incorrect:storage2storage2 is no LRS.storage3storage3 is premium.Also, only standard storage account types support live migration. Premium storage accounts must be migrated manually.
https://docs.microsoft.com/en-us/azure/storage/common/storage-redundancy-zrs
Post your Comments and Discuss Microsoft AZ-104 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the AZ-104 content, but please register or login to continue.