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 27

Question 260

An automation service rotates an Azure Storage account key. Security requires the new key never appear in pipeline console logs or plain text configuration. Which operational design is suitable?

  1. Store and retrieve updated key material through Azure Key Vault or an approved secret store, using restricted identities and nonlogging deployment variables.
  2. Print the entire key once for debugging, then delete the build log later.
  3. Store the key as a resource-group tag so it is searchable by the operations team.
  4. Put the new key in an ARM template output that every deployment engineer can read.

Explanation

Correct Answer

A:

Azure Key Vault and comparable managed secret systems can hold sensitive storage credentials with access controlled by identity and auditable permissions. During rotation, automation should update protected secret versions and configure consumers to retrieve them securely, without printing the value to build logs or committing it to source control. Restrict who can list or regenerate storage account keys and test clients after the update. Where workloads support managed identities, removing the Shared Key dependency entirely can further reduce exposure.

Incorrect Answers

B:

Pipeline output can be retained, forwarded or copied before anyone deletes a log. Printing a newly generated storage account key violates the secrecy requirement and creates an avoidable exposure. Keep credential values in secure secret stores and use redacted status or authentication success indicators for troubleshooting.

C:

Azure resource tags are metadata, not a secure vault for secrets. Users who can inspect resource metadata could read the credential, and tags may be copied into inventory and billing systems. Store storage account keys in a protected secret store and avoid plaintext handling during deployment.

D:

Publishing sensitive key material as a broadly visible deployment output can expose it to logs, history and users without a legitimate need. The requirement is protected handling and distribution, not convenient display. Use an approved secret reference and narrowly scoped access instead of emitting the credential itself.

Question 261

A company rotates key1 on a storage account. Several vendors have service SAS URLs originally signed with key1 and report authentication failures. What explains this behavior?

  1. Assigning subscription Reader to every vendor restores tokens signed with the old key.
  2. Regenerating key1 invalidated its key-signed service SAS signatures; replacement SAS tokens must be issued using a valid signing key.
  3. The storage account must have been moved to a different Azure region during key rotation.
  4. Every SAS remains valid regardless of the signing key that created it.

Explanation

Correct Answer

B:

Service SAS and account SAS tokens are signed using a storage account key. Rotating the key changes the signing secret, so existing tokens derived from the regenerated key can no longer be verified and must be reissued. The team should determine which SAS issuers and clients were dependent on key1 and distribute correctly scoped replacements. User delegation SAS tokens use Entra-backed delegation keys and have different revocation behavior. Do not broaden firewall or Azure RBAC permissions to compensate for an invalid signature.

Incorrect Answers

A:

Azure Reader grants management-plane resource visibility but cannot make a service SAS signature valid after its signing key changes. Vendors presenting the old token will continue to fail authentication. Generate replacement SAS URLs with proper scope, permissions and expiry instead of granting unrelated Azure resource roles.

C:

Access key regeneration changes authentication material and does not automatically relocate storage resources to another region. The failures arise from invalidated signatures rather than changes to physical data placement. Reissue service SAS tokens with an active signing credential while maintaining existing network controls.

D:

A key-signed SAS relies on Azure Storage validating its signature with the applicable signing key. After that key is regenerated, tokens signed with the previous value no longer authenticate. The vendors need newly signed SAS URLs or another supported access method, not an assumption of permanent token validity.

Question 262

A storage account has key1 and key2. Most clients currently use key1, and the company wants to rotate both keys safely. Which TWO actions support a no-surprise rollover? Select TWO answers.

  1. After key1 is regenerated, move clients to its new value, verify operation and then regenerate key2 separately.
  2. Give every caller the account's two keys in a shared spreadsheet so fallback always works.
  3. Regenerate key1 and key2 together, because clients automatically discover the replacements.
  4. Move clients from key1 to working key2 and verify application connections before regenerating key1.
  5. Enable anonymous Blob access as a temporary fallback if both keys are invalid.

Explanation

Correct Answers

A:

Once a valid new key1 exists, workloads can migrate back to that key and confirm successful authenticated requests before key2 is rotated. Separating the regenerations avoids invalidating credentials that applications are still using. Update protected secret references and account-key-signed SAS tokens as required, and capture successful connection checks between the steps. This sequence follows the two-key rollover model rather than changing both signing secrets simultaneously.

D:

Azure Storage's two access keys support a staged credential rollover. When most applications currently depend on key1, the operator should update their connection strings or protected secrets to use key2 and test that those workloads can continue. Only then is regenerating key1 unlikely to interrupt legitimate clients. Identify any key1-signed service or account SAS tokens as well, because their signatures will require replacement after regeneration.

Incorrect Answers

B:

Distributing both account keys widens sensitive credential exposure and defeats the goal of controlled rotation. Applications should retrieve only approved key material through secure configuration or use Entra authentication where supported. Keep signing secrets out of spreadsheets and deployment logs while performing staged rollover.

C:

Shared Key clients typically use a connection string or secret containing a particular key; regenerating both at once invalidates both old values. Azure Storage does not automatically rewrite every client's stored credential. That creates avoidable outages and may invalidate signed SAS tokens. Rotate one key at a time after verified client migration.

E:

Anonymous access would undermine the data security model and does not support workloads that need authenticated writes or other restricted storage services. It is not a safe availability mechanism for key rotation. The two-key sequence permits continuity without making private data public.

Question 263

An analyst has Storage Blob Data Reader at container scope but cannot view the storage account's two master keys. The analyst asks for Storage Account Contributor merely to see blobs. How should an administrator respond?

  1. Disable the storage firewall because listKeys and blob read permissions are the same operation.
  2. Assign Global Administrator in Microsoft Entra so the account keys become visible automatically.
  3. Keep the limited Blob Data Reader grant and avoid granting the separate listKeys management permission unless a specific approved task requires it.
  4. Grant Storage Account Contributor because every blob reader must see the master keys.

Explanation

Correct Answer

C:

Storage Blob Data Reader provides Entra-authorized blob read actions without granting a principal permission to list storage account Shared Keys. Key retrieval is a management action that can expose credentials with broad data access when Shared Key is allowed. The analyst's ordinary read workload should use a supported OAuth data client and retain least-privilege container scope. If the Azure portal needs ARM navigation visibility, a narrow Reader role may be appropriate, but it does not justify granting Storage Account Contributor or master-key retrieval.

Incorrect Answers

A:

Storage network admission and Azure RBAC management/data actions are distinct controls. Changing the firewall would not convert Blob Data Reader into listKeys authority or grant missing key access. The analyst should not require master keys to read blobs through Microsoft Entra, so retain secure networking and role separation.

B:

Microsoft Entra Global Administrator is a powerful directory role, not the appropriate narrowly scoped key-listing permission for a storage account. Making an analyst a tenant-wide administrator would violate least privilege and would not be necessary for normal blob data reads. Preserve scoped data authorization instead.

D:

Blob data reading through Microsoft Entra authorization does not require the client to retrieve storage account keys. Storage Account Contributor exposes much broader management powers and key-related actions than the analyst needs. Keep the data-plane Reader role and add only narrowly necessary resource view permissions if the chosen client experience requires them.

Question 264

An external support engineer needs to download one confidential Blob object during a 15-minute authorized support session. They request the storage account primary key because it would be easy to reuse. What is the least-privilege way to provide the file?

  1. Refuse the storage account key and issue a short-lived, read-only blob-scoped user-delegation SAS over HTTPS when the issuer has the required Entra permissions.
  2. Grant subscription Owner so the engineer can download the blob without a URL token.
  3. Enable anonymous access on the entire blob container to avoid handling any credentials.
  4. Send the storage account primary key for this download and rotate it at the end of the session.

Explanation

Correct Answer

A:

A user-delegation SAS is signed with a key obtained using Microsoft Entra permissions rather than sharing the storage account master key. Scope it to the single Blob, grant read only, and set a short validity interval matching the approved support window; deliver it over HTTPS. A SAS authorizes multiple eligible requests while valid, so do not describe it as inherently single-use. This option minimizes the external engineer's access compared with a storage account access key.

Incorrect Answers

B:

Subscription Owner includes highly privileged resource and access-management capabilities and is not required to read one Blob. It also does not itself guarantee Blob data-plane authorization through an Entra OAuth client. Expanding the contractor's privileges for a short download would violate the stated least-privilege requirement. The precise solution is delegated data access restricted to the selected object.

C:

Anonymous Blob container access can expose information to anyone who discovers an eligible URL. It is inappropriate for a confidential support artifact and cannot provide individually delegated access with a short expiration. Making an entire container public also broadens access far beyond the one object specified in the scenario. Keep private access and use scoped authorization.

D:

A storage account primary key is a powerful shared secret that can authorize broad requests and sign additional SAS tokens. Sending that key to a temporary external engineer could expose unrelated stored objects, even if rotation is planned. Rotating a key can also disrupt other integrations using it. A short-lived Blob-scoped user-delegation SAS avoids disclosing the account key.

Question 265

A company is migrating a department file share to Azure Files. Domain-joined Windows laptops must access the SMB share using each employee’s own directory identity, with share-level and NTFS permissions enforced. The Azure storage account does not yet have a directory identity source configured for SMB. Which configuration meets all three requirements?

  1. Configure a supported directory identity source, but rely on the Azure Reader resource role as the only permission granted to the SMB users.
  2. Grant an Azure Files SMB share-level data role and NTFS ACLs, but continue mounting the share using the storage account key.
  3. Switch the share to NFS 4.1 and use POSIX UID/GID authorization for the existing Windows SMB client connections.
  4. Configure a supported Azure Files SMB directory identity source, grant a suitable share-level SMB data role, and enforce Windows directory/file ACLs.

Explanation

Correct Answer

D:

Azure Files identity-based SMB access requires a supported directory authentication source configured for the account, such as the supported Active Directory or Microsoft Entra Kerberos approach. After authentication is enabled, administrators must authorize the appropriate users or groups with an eligible SMB share-level role or supported default permission and enforce Windows ACLs at the directory and file levels. The combination meets both the individual identity requirement and layered share/file authorization. Verify the supported identity prerequisites and test an actual user mount; a storage account key or generic management Reader role alone is not equivalent.

Incorrect Answers

A:

A configured directory identity source is necessary, but it does not independently authorize file access over SMB. The Azure Reader role covers resource management-plane viewing and does not grant the required Azure Files share-level data access. Users would still lack an appropriate share-level grant, and file and directory ACLs would not be evaluated as a complete authorized path.

B:

The share-level role and Windows ACLs are important for authorization, but mounting with a shared storage account key does not authenticate individual employees. Account-key based access is broader and does not meet the requirement to connect as each person with their own directory credentials. Enable the supported SMB identity source before assigning the correct user permissions.

C:

Azure Files NFS uses a different authentication and permission model from identity-based SMB. NFS clients use network access and POSIX permissions rather than a Windows domain user identity being authorized through SMB share roles and Windows ACLs. Moving the workload to NFS would not provide the requested access path for the existing Windows SMB clients.

Question 266

A domain-joined employee can authenticate to an Azure Files SMB share using Kerberos. The employee already has the Storage File Data SMB Share Reader role at the file-share scope. The share root is accessible, but a folder named Payroll returns Access denied, and its Windows ACL does not include the employee or an eligible group. What is the minimum relevant fix?

  1. Grant the required read permission on the Payroll folder through its Windows directory/file ACL to the appropriate employee or group.
  2. Assign the same SMB Share Reader role again at subscription scope and leave the Payroll folder ACL unchanged.
  3. Assign Storage Blob Data Reader on the storage account because Blob and Files share the same authorization plane.
  4. Disable the share's selected-network firewall restrictions to bypass authorization failures inside the Payroll directory.

Explanation

Correct Answer

A:

The Kerberos sign-in and share-level Azure Files SMB Reader assignment are already working, as shown by successful access to the share root. Directory and file access is a separate authorization layer enforced by Windows ACLs. Granting the intended employee or group the specific Payroll read rights at the folder, with proper inheritance where needed, corrects the missing layer without broadening share-wide management permissions. Verify effective ACL entries and any explicit denies before making the smallest change, rather than altering storage networking.

Incorrect Answers

B:

Another Reader role assignment at a wider scope does not overcome an explicit absence of Windows ACL permissions on the Payroll folder. The existing share-level role has already granted the employee access to the SMB share. Azure Files evaluates file and directory ACLs separately after share-level authorization, so duplicating or broadening the same Azure RBAC role is not the minimum corrective operation.

C:

Storage Blob Data Reader controls Azure Blob data access, not the Windows ACLs evaluated by Azure Files SMB. It does not grant entry into a protected SMB folder simply because the blob and file services share an Azure storage account. Since Kerberos authentication and SMB share-level access already work, a blob-specific role is both misdirected and insufficient.

D:

Storage networking rules control whether a client can reach the storage endpoint, while this client has already reached the SMB share and listed its root. The observed failure occurs at one protected directory, which points to an ACL problem. Relaxing the storage firewall would unnecessarily expand network exposure without granting the missing NTFS-equivalent read permission.

Question 267

Azure VMs use their on-premises AD DS computer accounts to access a classic Azure Files share over identity-based SMB. The storage account's AD DS integration is already enabled, but those computer accounts have no corresponding Microsoft Entra user or group identities for Azure RBAC role assignments. Storage account keys are prohibited. Windows file ACLs must still determine which folders each computer account can read. Which share-level authorization approach supports this design?

  1. Assign Storage File Data SMB Share Reader directly to each AD DS computer account through Azure RBAC.
  2. Grant each VM Storage Account Contributor, which automatically creates directory-level SMB file access.
  3. Set an appropriate default share-level permission for authenticated SMB identities, then enforce the required Windows folder and file ACLs.
  4. Mount the share using the storage account key, then rely on Windows ACLs to enforce the computer account identity.

Explanation

Correct Answer

C:

Azure Files allows a default share-level permission for all authenticated identities when a computer account cannot be synchronized or assigned directly through Microsoft Entra RBAC. The storage account must already have the supported AD DS identity source, as this scenario states. Default share-level authorization only opens the share-level gate; the computer identity still needs suitable Windows ACL permissions on the root and each required folder or file. The design avoids exposing storage account keys and preserves per-path authorization through directory ACLs.

Incorrect Answers

A:

Computer accounts do not have matching identities in Microsoft Entra ID for the normal Azure RBAC share role assignment workflow. Microsoft documents default share-level permissions as a supported approach for these identities. Attempting to assign Storage File Data SMB Share Reader directly to a computer account cannot implement the stated identity-based access design, even though that role is valid for eligible Entra identities.

B:

Storage Account Contributor is an Azure resource-management role, not an SMB directory permission. It can perform storage account administration but does not make individual computer accounts recognized as eligible Azure Files share RBAC principals. It also exceeds the least-privilege intent and cannot replace the Windows folder ACLs that determine which paths a computer may read after it authenticates.

D:

Mounting with an account key violates the explicit prohibition and generally provides privileged storage credentials rather than access in the computer account's Kerberos identity. Account-key access also changes the authorization model instead of using the existing AD DS SMB configuration. Even if a mount technically succeeds, it would not meet the requirement for identity-based computer-account access controlled by appropriate folder ACLs.

Question 268

An administrator must give an auditor read-only access to one Azure Files SMB share using identity-based authentication. The auditor already has Windows read ACLs on the target directories and network connectivity. The only assigned data role is Storage Blob Data Reader, so SMB access fails. Which least-privileged Azure RBAC data role fixes the share-level authorization?

  1. Storage File Data SMB Share Contributor, which permits writing and deleting files as well as reading them.
  2. Storage File Data SMB Share Elevated Contributor, which also allows changing file and directory ACLs.
  3. Storage Blob Data Owner, because its blob control extends automatically to Azure Files SMB shares.
  4. Storage File Data SMB Share Reader at the target share scope for the auditor's eligible identity.

Explanation

Correct Answer

D:

Storage File Data SMB Share Reader provides the Azure Files share-level read access needed by an eligible Microsoft Entra identity without granting write or ACL-management authority. This is the narrowest built-in role for the specified audit task. The previously granted Windows ACLs control which directories and files can actually be read after the auditor passes the share-level gate. Scope the Reader assignment to the one share and recheck the effective identity and ACL; the existing Blob Data Reader assignment is irrelevant to SMB authorization.

Incorrect Answers

A:

SMB Share Contributor would allow read operations, but it also authorizes write and delete activity beyond the stated audit requirement. The question asks specifically for the least-privileged built-in role needed for read-only access. Although a broader share data role might remove part of the access denial, it is not the appropriate security choice when the auditor must not modify files.

B:

Elevated Contributor includes the ability to modify file and directory access control lists, which is substantially more authority than simply reading audit evidence. Existing Windows read ACLs already provide the path-level authorization the auditor needs. Assigning an elevated share role would unnecessarily increase the damage possible if the audit identity were compromised or misused.

C:

Blob Data Owner applies to the Azure Blob data plane. Azure Files over SMB has its own share-level data roles, and the auditor needs one of those roles in addition to the established Windows ACL. The fact that Blob and Files live in a storage account does not make their RBAC permissions interchangeable. Granting more blob rights will not be the required SMB share permission.

Question 269

An Azure Files SMB share uses a configured, supported identity source and has the required directory users represented in Microsoft Entra ID. The auditors need approved finance readers to open files, but not modify or delete them. Which TWO authorization settings enforce this read-only access? Select TWO answers.

  1. Assign Storage Blob Data Reader to the users; Blob role permissions also authorize SMB file reads.
  2. Assign Storage File Data SMB Share Contributor to the readers, granting write and delete unnecessarily.
  3. Grant Storage File Data SMB Share Reader to the approved user or group at the applicable file-share scope.
  4. Configure only Windows NTFS ACLs and leave all share-level authorization absent for the authenticated users.
  5. Apply Windows directory and file ACL entries that allow necessary read operations but deny unapproved write operations.

Explanation

Correct Answers

C:

Azure Files checks share-level authorization in addition to directory/file ACLs. The SMB Share Reader role grants the approved Entra identity read access at the intended share scope without the write/delete rights of Contributor. Because a share-level grant does not override a restrictive directory ACL, the administrator must also verify file and directory-level permissions. This combined design meets the read-only business need while respecting least privilege at both enforced layers.

E:

Windows access control lists provide granular effective permissions on Azure Files directories and files, including the share root. Applying ACL entries that permit the finance readers only to read ensures they cannot alter documents even where the share-level role permits entry. This complements the SMB share Reader role rather than replacing it. Verify inherited entries and group memberships so an unrelated broad ACL does not inadvertently give write access.

Incorrect Answers

A:

Storage Blob Data Reader authorizes Azure Blob service data access, not identity-based SMB file share authorization. Azure Files has its own share-data roles for the SMB protocol. Using the Blob role would not grant the required share access and would add an irrelevant permission on a different storage service.

B:

Storage File Data SMB Share Contributor allows users to change and delete file content, exceeding the auditors’ required read-only privileges. Even if restrictive NTFS permissions happen to prevent some writes, granting an unnecessarily broad share role violates least privilege. The supported SMB Share Reader role is the appropriate share-level grant for this stated access pattern.

D:

Azure Files enforces both an identity-based share-level authorization layer and Windows ACLs for granular directory/file access. For users who require a specific share role, omitting share-level permission can block them before file ACLs are evaluated. NTFS configuration alone is not the requested complete design; grant the appropriate share reader role and then apply the restrictive ACLs.

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.