mcAfee Secure Website
23

Microsoft AZ-104 Bundle

Exam Code: AZ-104

Exam Name Microsoft Azure Administrator

Certification Provider: Microsoft

Corresponding Certification: Microsoft Certified: Azure Administrator Associate

AZ-104 Training Materials $44.99

Reliable & Actual Study Materials for AZ-104 Exam Success

The Latest AZ-104 Exam Questions as Experienced in the Actual Test!

  • 24
    Questions & Answers

    AZ-104 Questions & Answers

    606 Questions & Answers

    Includes questions types found on actual exam such as drag and drop, simulation, type in, and fill in the blank.

  • 25
    AZ-104 Video Course

    AZ-104 Training Course

    132 Video Lectures

    Based on Real Life Scenarios which you will encounter in exam and learn by working with real equipment.

  • exam =30
    Study Guide

    AZ-104 Study Guide

    458 PDF Pages

    Study Guide developed by industry experts who have written exams in the past. They are technology-specific IT certification researchers with at least a decade of experience at Fortune 500 companies.

exam =32

Microsoft Azure Administrator (AZ-104) Practice Tests

Guarantee

Satisfaction Guaranteed

Pass4sure has a remarkable Microsoft Candidate Success record. We're confident of our products and provide no hassle product exchange. That's how confident we are!

99.3% Pass Rate
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • exam =34
    Questions & Answers

    Questions & Answers

    606 Questions

    $124.99
    exam =35
  • exam =37
    AZ-104 Video Course

    Training Course

    132 Video Lectures

    $39.99
  • exam =36
    Study Guide

    Study Guide

    458 PDF Pages

    $29.99

Microsoft AZ-104 Practice Test 28

Question 270

An audit team uses Kerberos SMB to read a restricted set of folders in an Azure Files share with Storage File Data SMB Share Reader and NTFS permissions. The compliance officer now explicitly approves this auditor to read ALL files in the designated share through Azure portal browsing, even files that the SMB NTFS ACLs would otherwise restrict. Storage account keys are prohibited. The auditor already has Azure Resource Manager Reader for the storage account, but Entra-authorized portal browsing fails. Which authorization plan meets the newly approved scope, and what important security effect must be acknowledged?

  1. Assign Storage File Data SMB Share Reader again and keep the existing NTFS ACLs; the Azure portal will automatically use Kerberos SMB authentication for its file-data REST requests.
  2. Grant only Storage Blob Data Reader; Blob OAuth permissions also authorize the Azure Files REST service without privileged file permissions.
  3. Grant Storage File Data Privileged Contributor and subscription Owner because portal read-only browsing requires full file write and vault-wide management rights.
  4. Grant the narrowest supported Storage File Data Privileged Reader assignment for the approved Azure Files data scope, plus portal-required OAuth backup-semantics permissions and existing ARM Reader; document that privileged FileREST reads bypass NTFS ACLs.

Explanation

Correct Answer

D:

Azure Files portal browsing with a Microsoft Entra identity requires suitable privileged FileREST data authorization (Storage File Data Privileged Reader for read-only files), a management-plane Reader role, and documented readFileBackupSemantics/writeFileBackupSemantics permissions for portal browsing. Critically, Storage File Data Privileged Reader bypasses underlying NTFS ACLs for supported OAuth FileREST operations, unlike SMB Share Reader. Constrain the RBAC assignment to the approved data scope and record that broader data visibility as part of security approval; the role is not a method of retaining file-level NTFS restrictions.

Incorrect Answers

A:

SMB Share Reader together with NTFS ACLs applies to the SMB/Kerberos access path. Entra-authenticated Azure portal browsing uses Azure Files FileREST, not the same SMB ticket and ACL evaluation. Reassigning the SMB role does not provide the special OAuth data actions required by the portal; the newly approved all-files read scenario needs a privileged FileREST data role and an explicit ACL-bypass review.

B:

Storage Blob Data Reader grants data-plane operations for Blob objects, not the Azure Files shares/files FileREST permissions. It cannot authorize the missing file-data OAuth operation and cannot replace Storage File Data Privileged Reader. The cross-service boundary is decisive even when both services live inside one storage account.

C:

Storage File Data Privileged Contributor can write, delete and modify file permissions as well as read, and subscription Owner brings excessive resource-management and access-delegation capability. The compliance officer approved read-only FileREST access, so those broad roles are unnecessary and violate the stated authorization ceiling.

Question 271

An Azure Files SMB share uses on-premises AD DS Kerberos authentication and Windows file ACLs. On the storage account, a default share-level permission of Storage File Data SMB Share Elevated Contributor applies to all authenticated identities. An auditor also has an explicit Storage File Data SMB Share Reader assignment on the reports share. The reports folder NTFS ACL separately allows that auditor Modify. Despite the explicit Reader assignment, the auditor can change files. Which administrative assessment and least-privilege correction address the effective share permission?

  1. The auditor’s explicit SMB Share Reader assignment always overrides a higher default permission; investigate only whether the operating system cached the file.
  2. Because a user has an explicit Reader role, Windows NTFS Modify permissions automatically become NTFS Read even when a broad default share-level permission remains configured.
  3. The more permissive default share-level role is effective over the narrower explicit Reader role. Reduce or remove the broad default grant, use specifically scoped SMB share permissions for authorized principals, and verify NTFS ACLs.
  4. Replace the Azure Files SMB share with an NFS share; the SMB default-permission and explicit-role precedence will then enforce Windows NTFS Reader on existing SMB clients.

Explanation

Correct Answer

C:

Microsoft Learn explicitly states the higher-level of a default share permission and a specific SMB share RBAC assignment is effective. With account-wide default Elevated Contributor and folder NTFS Modify, the user can write despite an explicit Share Reader role. Replace the broad default grant with appropriate group-scoped share roles (ensuring other authorized identities retain required access) and review NTFS ACLs for least privilege.

Incorrect Answers

A:

Microsoft documents that when an authenticated identity has both a default share-level permission and a specific share-level RBAC assignment, Azure Files uses the higher permission. Explicit Reader does not reduce an Elevated Contributor default. An unchanged NTFS Modify ACL then permits writes. Reconfigure the broad default and access-specific roles rather than treating client caching as the authorization cause.

B:

Azure Files evaluates SMB share-level authorization together with file/directory ACLs. The NTFS Modify ACL does not downgrade itself merely because a narrower explicit share role exists. Here the account-wide default Elevated Contributor is more permissive than the explicit Reader and remains effective, so removing or narrowing that default is necessary to establish the intended share-level boundary.

D:

NFS and SMB are separate Azure Files protocols. Converting the share would disrupt existing SMB clients and Windows ACL-based access, and would not implement a Windows SMB share-role precedence fix. The case uses supported AD DS Kerberos SMB authorization; the correct control is the default-versus-specific share-level grant and the existing NTFS ACL, not an NFS migration.

Question 272

An authorized file-share administrator can read and write files over a domain-authenticated Azure Files SMB share using Storage File Data SMB Share Contributor. The administrator must now change the Windows ACL on the share root without using a storage account key, but the current share-level role lacks modify-permissions rights. Which narrowly scoped built-in role adds the required capability?

  1. Storage File Data SMB Share Reader at the affected share scope.
  2. Storage File Data SMB Share Elevated Contributor at the affected share scope.
  3. Storage Blob Data Owner at the storage-account scope.
  4. A second Storage File Data SMB Share Contributor assignment at subscription scope.

Explanation

Correct Answer

B:

Storage File Data SMB Share Elevated Contributor grants SMB read/write/delete plus modify-permissions actions on files and directories, including ACL administration. Assign it to the authorized identity at the required file share scope and validate the Windows security changes.

Incorrect Answers

A:

Storage File Data SMB Share Reader allows SMB file reads, not changing Windows file or folder ACLs. It would reduce rather than extend the administrator’s needed permission.

C:

Storage Blob Data Owner applies to Blob service data access and cannot grant the Azure Files SMB modify-ACL action. Sharing a storage account does not merge Blob and File data-plane roles.

D:

The standard SMB Share Contributor role grants file read/write/delete, but not the separate modifypermissions/action. Reassigning it at a wider scope adds exposure without enabling ACL modification.

Question 273

A department migrates an AD DS file server to an Azure Files SMB share. Supported AD DS identity integration and share-level Azure RBAC are already configured, but users lose the prior per-folder NTFS access restrictions after a basic file copy. What step preserves those restrictions?

  1. Assign subscription Owner to all department users to avoid preserving ACLs.
  2. Switch the destination share to NFS 4.1 and assume Windows ACLs are preserved automatically.
  3. Replace the destination SMB share with a Blob container with anonymous read.
  4. Use a supported copy/migration process that preserves and validates Windows directory and file ACLs in addition to existing share-level rights.

Explanation

Correct Answer

D:

Windows ACL permissions must be transferred and tested on the destination files/directories; share-level RBAC alone does not recreate per-folder restrictions.

Incorrect Answers

A:

Subscription Owner is unrelated to NTFS file ACL preservation and introduces excessive Azure management authority.

B:

Azure Files NFS uses different authorization semantics; moving SMB content to NFS would not solve Windows permission preservation.

C:

A public Blob container neither preserves SMB per-folder access controls nor protects private Windows file data.

Question 274

A project worker needs SMB read, create, modify and delete rights inside one authorized Azure Files share, with matching NTFS ACLs already granted. The user must not administer the storage account or other shares. Which Azure role best fits?

  1. Storage Blob Data Reader at subscription scope, which covers all SMB write operations.
  2. Storage File Data SMB Share Contributor scoped to the required file share.
  3. Storage Account Contributor at subscription scope to manage every storage account.
  4. Storage File Data SMB Share Reader, which includes data modification and deletion.

Explanation

Correct Answer

B:

The Azure Files SMB Share Contributor role permits standard share data operations at a narrow scope, while the existing NTFS ACLs continue to apply.

Incorrect Answers

A:

Blob Reader authorizes Blob reads, not SMB file share writes or deletion.

C:

Storage Account Contributor is broader management-plane authority and is unnecessary for ordinary SMB share data changes.

D:

SMB Share Reader is read-oriented and does not grant the requested create, edit or delete operations.

Question 275

Windows clients cannot mount a healthy Azure Files SMB share because their corporate egress firewall blocks outbound TCP 445. The share IAM and credentials are valid. What addresses the actual failure?

  1. Increase the VM vCPU quota in the Azure subscription.
  2. Add a Storage Blob Data Reader role for every user even though SMB network traffic never reaches Azure Files.
  3. Establish an approved reachable SMB TCP 445 path, such as permitted network routing/VPN, or use a supported alternate file-access pattern.
  4. Disable anonymous Blob protection on the storage account.

Explanation

Correct Answer

C:

An SMB mount requires TCP 445 connectivity along the approved path, so restore transport reachability or change to a supported connectivity model.

Incorrect Answers

A:

Compute quota does not change whether the client network can establish SMB sessions.

B:

Data authorization cannot repair a blocked outbound SMB TCP connection; the request cannot reach the file service.

D:

Anonymous Blob settings concern HTTP Blob access and do not remove TCP 445 egress restrictions for Azure Files.

Question 276

An external B2B guest object has no corresponding identity in the AD DS forest used for an Azure Files SMB share. Its attempted Kerberos mount fails, despite an approved app invitation. Which conclusion is correct?

  1. An Entra B2B invitation automatically creates the required on-prem AD DS Kerberos identity and file ACLs.
  2. The guest invitation alone is insufficient: use an identity source and user membership supported by the SMB authentication configuration and grant file permissions.
  3. Give the guest Storage Blob Data Owner, which replaces SMB Kerberos authentication.
  4. Change the Blob public access level, which causes AD DS to recognize the external guest.

Explanation

Correct Answer

B:

Identity-based SMB access depends on a supported directory source, corresponding authenticated identity, share-level roles and effective Windows ACLs.

Incorrect Answers

A:

B2B collaboration establishes a guest representation for eligible applications; it does not automatically provision an AD DS account for Azure Files Kerberos.

C:

Blob authorization cannot authenticate an AD DS SMB Kerberos session or grant access to file-share paths.

D:

Blob anonymous access is a different storage service setting and does not create the missing directory principal.

Question 277

An application must place standard block blobs and ordinary Azure Files SMB shares in a newly created account, with no premium-only performance requirement. Which storage account kind is appropriate?

  1. Premium BlockBlobStorage, which automatically includes Azure Files SMB share support.
  2. Standard general-purpose v2 (StorageV2) with the supported Blob and File services.
  3. Premium FileStorage, which exposes every standard block-blob feature by default.
  4. A classic BlobStorage-only account, which also creates SMB file shares.

Explanation

Correct Answer

B:

Standard GPv2 is the supported general-purpose storage account kind for both Blob and File services with general-purpose workload features.

Incorrect Answers

A:

Premium block blob specialization is not the standard general-purpose account that also exposes ordinary Azure Files SMB shares.

C:

Premium FileStorage targets Azure Files performance, not a combined standard Blob and File service requirement.

D:

BlobStorage account kinds focus on Blob service and do not satisfy the ordinary Azure Files SMB share requirement.

Question 278

A regulated dataset must remain inside the selected Azure geography; the organization explicitly forbids geo-replication to a distant secondary region. What redundancy decision fits?

  1. Select RA-GRS because its secondary read endpoint does not count as geographic replication.
  2. Use GZRS automatically, since zone redundancy removes its cross-region replication component.
  3. Select an eligible storage region inside the approved geography and use LRS or ZRS as the required intra-region failure domain permits.
  4. Create the storage account in an unapproved region and apply a residency tag afterward.

Explanation

Correct Answer

C:

LRS and ZRS keep copies in the chosen primary Azure region and can meet a locality constraint while providing different failure-domain protection.

Incorrect Answers

A:

RA-GRS replicates asynchronously to a secondary region and violates a prohibition on secondary geographic copies.

B:

GZRS includes both zonal primary copies and asynchronous geo-replication, so it still introduces a secondary-region data copy.

D:

Tags cannot relocate stored data or make an unapproved Azure storage region satisfy residency requirements.

Question 279

Creating an Azure Storage account named `auditarchive` fails even though that name is unused within the current resource group and subscription. What naming rule should be checked?

  1. Azure Storage account names are globally unique in Azure DNS; choose another valid lowercase account name.
  2. Azure storage names need only be unique among resource groups of the same subscription.
  3. Choose the same name in another availability zone; storage names are zonal-only.
  4. Give the deployment identity Storage Blob Data Owner to override a name conflict.

Explanation

Correct Answer

A:

A storage account contributes to a globally addressable service endpoint, so its compliant DNS name must not collide with an existing account.

Incorrect Answers

B:

Subscription or resource-group uniqueness alone cannot satisfy the storage account global naming constraint.

C:

Availability zone is a storage redundancy consideration, not a namespace partition permitting the same global account name.

D:

Role assignment can affect deployment authorization but cannot reserve a storage account name already in use.

Question 280

A legacy HTTPS storage client fails after the account minimum permitted TLS version is increased to the security-approved baseline. What is the durable remediation?

  1. Disable storage-network firewall restrictions to allow legacy TLS negotiation.
  2. Upgrade the client to negotiate a supported TLS version while retaining the approved storage minimum TLS setting.
  3. Change the storage account replication from LRS to GRS.
  4. Issue a SAS with write permission so the old TLS handshake is accepted.

Explanation

Correct Answer

B:

The client must support the account minimum TLS protocol for HTTPS requests to succeed without weakening the required security baseline.

Incorrect Answers

A:

Storage firewall rules govern network admission; removing them cannot add an obsolete TLS version to a secure handshake.

C:

Data redundancy is unrelated to TLS protocol negotiation between the client and storage service.

D:

SAS permission bits authorize operations after a secure connection and cannot bypass TLS version negotiation.