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 8

Question 70

An organization requires employees to reconfirm their registered SSPR recovery information every 180 days. Administrators want the prompt to appear when users sign in, rather than relying on manual reminders. Which setting combination is appropriate?

  1. Give every employee a 180-day Azure Resource Manager lock.
  2. Require periodic MFA reauthentication but do not enable SSPR method reconfirmation at sign-in.
  3. Disable SSPR registration at sign-in and expect automatic reconfirmation anyway.
  4. Enable the SSPR sign-in registration prompt and configure the supported reconfirmation interval to 180 days.

Explanation

Correct Answer

D:

The SSPR configuration can require users to register recovery methods at sign-in and periodically reconfirm them after a specified number of days. Enable the registration prompt first, then set the reconfirmation interval to the approved 180 days, which is within the documented supported range. Test with an eligible account and confirm the user is prompted appropriately after the configured period. This updates identity recovery information without altering passwords or granting unrelated Azure roles.

Incorrect Answers

A:

Azure management locks affect resource control-plane operations and do not track the age of a user's authentication methods. A 180-day lock would not ask anyone to review security information. This is an identity policy feature rather than an infrastructure lock requirement.

B:

MFA sign-in reauthentication proves a current access event, not that the user has reconfirmed their stored password-reset methods on the configured 180-day cadence. Microsoft documents a specific SSPR reconfirmation setting with a registration-at-sign-in prerequisite. Configure those identity recovery fields rather than relying on a separate MFA frequency policy.

C:

Microsoft documents that periodic confirmation of SSPR authentication information requires the Require users to register when signing in option to be enabled. Disabling that prerequisite prevents the intended prompt behavior. Ordinary reminders would not implement the requested conditional sign-in experience.

Question 71

A company's security policy prohibits SMS and voice-call verification for password recovery. The tenant wants users to retain a functional SSPR flow using only approved alternatives and to meet a two-method requirement. Which TWO actions are necessary? Select TWO answers.

  1. Disable SMS and voice in the SSPR authentication method policy and use approved supported methods instead.
  2. Keep SMS enabled but ask users to promise not to select it during recovery.
  3. Lower the reset verification requirement to zero methods so every user can recover.
  4. Ensure eligible users enroll enough distinct permitted methods to satisfy the configured two-method policy.
  5. Assign all users the Azure subscription Owner role to bypass recovery-factor checks.

Explanation

Correct Answers

A:

Microsoft Entra SSPR can be configured with approved authentication methods rather than allowing every available recovery channel. Remove prohibited SMS and voice options from the applicable policy, ensure a valid alternative set remains, and verify that each selected factor is supported for the required recovery workflow. Merely communicating a preference does not block disallowed methods. The policy must be enforceable and its effect checked on an eligible nonadministrator account.

D:

Requiring two methods means that users must have enough distinct permitted factors registered before they forget their passwords. Microsoft documents that Authenticator and related OATH mechanisms can count as one method category for the two-method requirement, so two gestures from the same app do not automatically qualify. Check eligible registrations against the actual policy, supply a valid supported method mix, and test reset and fallback flows. This operational preparation complements disabling prohibited recovery channels.

Incorrect Answers

B:

If SMS remains enabled, a user may still be offered it as an acceptable recovery method, contrary to the stated security policy. Administrative advice cannot enforce an authentication-factor prohibition. Disable the method in the applicable configuration, and validate that the resulting flow uses only supported alternatives.

C:

SSPR does not provide an anonymous zero-factor reset model for ordinary users. Removing verification would defeat the feature's account ownership checks and invite account takeover. A two-method recovery policy must be satisfied through permitted registered methods, not bypassed because the organization dislikes certain factors.

E:

Subscription Owner is an Azure resource-management role and cannot waive the Microsoft Entra SSPR verification requirements. Giving it to every user would add large infrastructure privileges while leaving their registered methods unchanged. The appropriate security boundary is the identity recovery-method policy.

Question 72

Following a reported suspicious password change, the identity operations team must determine which account initiated a Microsoft Entra SSPR recovery and whether an administrator reset another user's password. Which evidence should they inspect?

  1. Review only the latest successful sign-in record and assume it identifies who initiated every password reset.
  2. The storage-account redundancy settings for the user's home folder.
  3. Microsoft Entra audit and SSPR activity records with event time, target account, and actor details where available.
  4. Inspect only Azure Activity Log resource-management events for the affected subscription.

Explanation

Correct Answer

C:

Microsoft Entra audit and password-reset activity records are the appropriate evidence for distinguishing an end-user self-service event from an administrator-initiated change. Review the event type, timestamp, target user, recorded initiator and outcome, with correlation to relevant sign-in or security information events. Verify any gaps in available logging instead of relying solely on a user's narrative. This preserves source attribution and supports incident-response decisions without assuming every password change has the same trigger.

Incorrect Answers

A:

Sign-in logs can help correlate a recovery investigation but do not by themselves enumerate every SSPR or administrator-initiated password change. The event needs the target identity, actor and operation result. Review the relevant Microsoft Entra audit and SSPR activity records to establish provenance.

B:

Storage redundancy governs the durability of data copies and cannot identify the actor in a directory password-reset operation. The organization's files may be protected by storage policies, but those settings are unrelated to SSPR event provenance. Consult identity logs and recovery records instead.

D:

Azure Activity Log focuses on resource control-plane operations and is not a substitute for Microsoft Entra directory audit records of password reset activity. The password operation may occur without an Azure Resource Manager action. Identity audit events are needed to attribute the reset to the correct actor.

Question 73

A synchronized employee completes the Microsoft Entra SSPR challenge, but the attempt fails while updating their on-premises AD DS password. The connector account lacks required writeback rights. Which remediation addresses the actual failure?

  1. Grant the employee Azure subscription Owner so the on-premises directory accepts the password update.
  2. Correct supported hybrid password writeback service permissions and connector configuration, then retest under AD DS password rules.
  3. Add an inbound public RDP rule to every domain controller.
  4. Change the employee's display name so AD DS password protection no longer applies.

Explanation

Correct Answer

B:

Password writeback is performed through a supported Microsoft Entra Connect or cloud sync integration with rights to modify eligible on-premises AD DS accounts. Verify the connector configuration, service account delegation, protected-account limitations and domain policy requirements; repair the missing rights at the supported boundary. Run an authorized recovery test and inspect synchronous error feedback to confirm the on-premises password was changed. The security policy should not be weakened or bypassed merely because writeback currently fails.

Incorrect Answers

A:

Azure subscription Owner authorizes cloud infrastructure administration and does not give the SSPR connector authority to reset an AD DS account. The error occurs after identity verification at the on-premises writeback boundary. Broad Azure RBAC cannot replace domain directory permissions or resolve connector health.

C:

Supported password writeback uses secure outbound connectivity and does not require exposing domain controllers over inbound RDP. Opening public management access would create attack surface without granting a connector permission to modify users' passwords. Use the documented identity synchronization service channel instead.

D:

The display name is not the permission controlling an AD DS password change and is not an approved bypass for domain password policy. Changing it would leave connector rights unresolved and could create confusing account metadata. Fix the service integration and test the actual password writeback action.

Question 74

Security authorizes a staged SSPR deployment: only the ten-person pilot team should have self-service reset initially, and successful recovery must be demonstrated before tenant-wide activation. Which TWO actions are appropriate? Select TWO answers.

  1. Enable SSPR for every directory user immediately and assume pilot members can serve as a representative sample.
  2. Create or identify the approved pilot security group and scope SSPR enablement to that group.
  3. Require MFA registration for the ten pilot users but leave SSPR enabled for the entire tenant.
  4. Skip registration and require pilot users to recover through a shared password document.
  5. Validate pilot authentication-method registration and perform representative authorized recovery tests before expanding scope.

Explanation

Correct Answers

B:

Microsoft Entra SSPR can be restricted to a selected group rather than applying immediately to the entire tenant. Create or use the designated ten-person pilot group, configure the authorized password-reset policy for that scope, and verify only eligible accounts are included. This gives the security team a controlled population for measuring enrollment and recovery success. It is a separate necessary action from actually testing the configured verification process.

E:

A staged rollout is useful only if the organization verifies that eligible users have registered enough permitted recovery methods and can complete the intended password-reset flow. Test representative cloud-only or hybrid accounts as applicable, inspect failures, and ensure notifications and help-desk procedures are adequate. Only after the pilot meets the defined recovery checks should administrators consider expanding eligibility to additional groups or the full tenant. This validates the operational path independently of merely enabling the pilot scope.

Incorrect Answers

A:

Turning on SSPR for everyone would violate the explicit staged rollout constraint. It also exposes a larger population to registration and help-desk behavior changes without evidence that the chosen methods and policies work. Begin with an intentional eligible group so failures can be corrected before broad deployment.

C:

Security information registration prepares people to pass authentication challenges, but it does not restrict which accounts are eligible for SSPR. Enabling the recovery service tenant-wide conflicts with the explicit ten-person pilot. Scope SSPR to the approved group first, then test the members' registered methods before expansion.

D:

SSPR requires the user to prove identity through supported registered verification methods; sharing a password would defeat that security mechanism. Omitting enrollment makes first-time recovery fail for people without acceptable factors. The pilot should test real verification, not rely on an unauthorized common secret.

Question 75

A developer must examine settings for storage account stfinance01 but must not change those settings or read customer blobs. The developer has no existing grants. What is the least-privileged role assignment?

  1. Assign Reader on the subscription containing the account.
  2. Assign Contributor on the storage account.
  3. Assign Reader directly on storage account stfinance01.
  4. Assign Storage Blob Data Reader on the account.

Explanation

Correct Answer

C:

Reader allows examination of the storage account's Azure Resource Manager configuration without management write permission. Assigning it on the individual account, rather than its resource group or subscription, restricts the view to the intended resource. It also does not grant OAuth permissions to read blob contents. The case asks for management-plane visibility only, so a dedicated blob-data role would not replace the needed read access to resource properties.

Incorrect Answers

A:

Subscription Reader would provide configuration visibility to all resources throughout that subscription, not only the one storage account in scope. It grants read-only rather than write rights, but fails the least-privilege boundary defined in the scenario. Use account-scoped Reader when the developer needs to inspect only stfinance01.

B:

Contributor includes resource-management write operations, not just read-only visibility. Although it could display account settings, it also permits changing permitted account configuration. That conflicts with the explicit prohibition on modifications. The storage account Reader role at the narrower resource scope meets the requirement without unnecessary management privileges.

D:

Storage Blob Data Reader is designed for reading blob container content through Microsoft Entra authorization. This developer must inspect the storage account's ARM configuration, not retrieve customer blobs. A data-plane role alone is therefore aimed at the wrong permission set; it does not provide the required general ARM resource-reading role for this task.

Question 76

An operations engineer needs to restart and resize existing Azure VMs in a resource group. The engineer must not grant access to colleagues or modify other resource families. Which built-in role should be assigned at that resource group?

  1. Virtual Machine User Login.
  2. Virtual Machine Contributor.
  3. Role Based Access Control Administrator.
  4. Owner on the entire subscription.

Explanation

Correct Answer

B:

Virtual Machine Contributor includes Azure VM management actions needed for start, stop, resize, and associated compute administration. Assigned at the relevant resource group, it avoids granting subscription-wide access or authority to create Azure role assignments. The role does not automatically include management of every connected network or storage resource, so deployment dependencies must be checked separately. For operating existing VMs under this constraint, it is more appropriate than general resource ownership.

Incorrect Answers

A:

Virtual Machine User Login enables supported operating-system sign-in to a VM, not the Azure Resource Manager privileges to resize or restart its compute resource. Logging on to a machine and administering the Azure VM resource are separate authorization concerns. The engineer needs VM management operations, which Virtual Machine Contributor is designed to grant.

C:

Role Based Access Control Administrator concerns assigning and removing Azure RBAC role grants under a permitted scope. The engineer is expressly prohibited from managing other people's access and needs to operate the VMs instead. This role would delegate the wrong security function and would not by itself provide the requested compute-management actions.

D:

Owner includes broad permissions to manage resources and grant roles throughout the subscription. It could operate the VMs, but it also exposes unrelated workloads and violates the prohibition on changing access assignments. A resource-group-scoped Virtual Machine Contributor assignment more closely follows least privilege for the stated responsibilities.

Question 77

A customer support analyst authenticates with Microsoft Entra ID and must list and read blobs in exactly one container, but cannot upload or delete them. Which role is appropriate at the container scope?

  1. Storage Blob Data Reader.
  2. Reader on the storage account only.
  3. Storage Blob Data Contributor.
  4. Storage Account Contributor.

Explanation

Correct Answer

A:

Storage Blob Data Reader grants the data-plane permissions to list and read blobs using Microsoft Entra authorization. Scoping the assignment to the required container confines those data permissions to that container rather than every dataset in the storage account. The role does not confer blob write or delete operations. If the analyst uses the Azure portal's browse experience, an additional ARM Reader grant can be necessary for portal navigation, but that does not change the required blob-data role.

Incorrect Answers

B:

The generic Azure Reader role provides ARM management-plane visibility to the storage account resource. It does not, by itself, authorize reading arbitrary blob content through Microsoft Entra OAuth. The request explicitly includes listing and reading blob data, so the analyst requires a storage data-plane role in addition to any portal-management visibility.

C:

Storage Blob Data Contributor includes blob write and delete permissions in addition to reading. It is appropriate for a workload that changes blobs, not for an analyst who must only view data. Assigning that role would unnecessarily expand the analyst's data-plane privileges on sensitive container content. Choose the Reader variant for this read-only requirement.

D:

Storage Account Contributor manages account resources and can perform powerful management actions, including key-related operations in supported configurations. It is not the least-privilege way to grant Entra-based read-only blob access. The analyst does not need to change account settings, and a container-scoped Blob Data Reader directly addresses the required operations.

Question 78

An ETL application's managed identity currently has Storage Blob Data Reader on container incoming. It must now upload, overwrite, and delete blobs in that same container without touching other containers. Which change is sufficient?

  1. Assign Storage Blob Data Owner on the entire storage account.
  2. Assign Storage Blob Data Contributor to the identity at container incoming.
  3. Keep Storage Blob Data Reader and enable hierarchical namespace.
  4. Assign Reader at the subscription level.

Explanation

Correct Answer

B:

Storage Blob Data Contributor supplies blob read, write, and delete data actions for a Microsoft Entra principal. Applying the assignment at the target container gives the ETL identity the mutations it lacks while avoiding access to peer containers. The existing Blob Data Reader role cannot support overwrite or delete requests. Confirm the managed identity is the actual caller and that storage networking rules also allow its traffic; RBAC permissions alone cannot bypass the storage firewall.

Incorrect Answers

A:

Blob Data Owner includes extensive data permissions, including ownership and access-control capabilities relevant to hierarchical namespaces. It could perform the requested writes, but scoping it to the whole storage account grants more than the service needs. Blob Data Contributor on the one container provides the requested mutations with a smaller privilege and data boundary.

C:

Hierarchical namespace changes the storage account's namespace and Azure Data Lake Storage capabilities; it does not convert a read-only role into blob write or delete rights. The application lacks data actions in its current role, not a directory layout feature. Assigning Blob Data Contributor at the intended container addresses the authorization failure without changing account architecture.

D:

Subscription Reader can list Azure resource-management properties across the subscription. It does not authorize writing or deleting blob bytes using the application's Microsoft Entra identity. In fact, it would broaden unrelated control-plane visibility while leaving the missing container data actions unresolved. Use the specialized blob-data contributor role at container scope.

Question 79

A deployment identity must create Azure Storage accounts and change their network/firewall configuration in resource group rg-platform. Its Azure RBAC role must NOT directly grant Microsoft Entra OAuth Blob DataActions. Security also requires the reviewer to disclose any indirect data-access route through storage account keys. Which built-in role and caveat correctly meet that narrowly stated requirement?

  1. Storage Account Contributor at rg-platform: it permits storage account management without OAuth Blob DataActions but can list storage account keys, which may grant data access through Shared Key unless that authorization is disallowed.
  2. Reader at rg-platform: its view-only management permissions allow account creation and firewall modification and do not require keys.
  3. Storage Blob Data Contributor at rg-platform: its Blob DataActions manage ARM storage-account firewall settings without granting access to blob contents.
  4. Storage Blob Data Reader at rg-platform: it includes storage-account creation and network-rule writes but no access to Blob contents.

Explanation

Correct Answer

A:

Storage Account Contributor grants the storage management-plane actions used to create accounts and update networking, while lacking Blob OAuth DataActions. Crucially, Microsoft documents that this role can perform listKeys; possession of the account keys can allow Shared Key data access if the account permits it. It is NOT a strict data-confidentiality boundary without additional protections.

Incorrect Answers

B:

Reader provides ARM metadata read access and cannot perform storageAccounts/write or update network/firewall settings. It is insufficient for the required deployment operations, even though it does not directly grant Blob DataActions.

C:

Storage Blob Data Contributor grants data-plane blob read/write/delete operations and therefore conflicts with the explicit no-OAuth-Blob-DataActions requirement. A Blob data role does not grant the Storage account creation/network modification actions.

D:

Storage Blob Data Reader explicitly grants OAuth Blob read access, contrary to the requirement; it does not authorize creating storage accounts or changing their firewall settings.

Question 80

A delegated security administrator should create and remove Azure RBAC role assignments for resources in one existing resource group, but must not modify those resources. Which role and scope best satisfy that assignment?

  1. Reader on the subscription.
  2. Role Based Access Control Administrator on the resource group.
  3. Owner on the subscription.
  4. Contributor on the resource group.

Explanation

Correct Answer

B:

Role Based Access Control Administrator is designed for managing Azure role assignments without handing out general resource Contributor permissions. Assigning it at the relevant resource group delegates access-administration authority over that scope and its descendants, not over the whole subscription. Built-in role-assignment permissions remain subject to applicable conditions and deny assignments, so the organization should inspect the effective access and enforce any additional restrictions required by its policy.

Incorrect Answers

A:

Reader allows inspection of configuration and existing role assignments where permitted, but not creation or deletion of those grants. It also expands visibility beyond the one resource group that the delegate owns. The case requires the write and delete actions on Azure role assignments, which are provided by an access-administration role rather than read-only access.

C:

Owner can manage role assignments, but also grants extensive resource-management privileges throughout the subscription. The user expressly must not modify resources and needs authority only in one resource group. Giving subscription Owner would violate both the permissions and scope restrictions; the narrower specialized RBAC Administrator assignment is the appropriate delegation.

D:

Contributor generally manages Azure resources but excludes the permission to create or remove Azure RBAC role assignments. That makes it both too broad for unrelated resource modifications and insufficient for this specific access-administration task. The dedicated RBAC Administrator role provides the relevant assignment operations without turning the delegate into an infrastructure operator.