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 6

Question 50

An outside consultant from a partner Microsoft Entra tenant needs to sign in to a single enterprise application hosted in your tenant. The application requires an assignable user object in your directory. An engineer proposes B2B direct connect because it is already used for a separate Teams shared channel. What identity design meets the application requirement?

  1. Invite the consultant through Microsoft Entra B2B collaboration, creating the guest representation in your tenant, then grant the narrowly required enterprise application assignment.
  2. Use B2B direct connect alone; it automatically creates a guest user object for every arbitrary enterprise application.
  3. Give the consultant subscription Owner without a guest identity or application assignment.
  4. Enable anonymous access to the enterprise application and replace its authentication policy with a resource tag.

Explanation

Correct Answer

A:

B2B collaboration represents the external user in the resource tenant so the enterprise application can receive a scoped user or app-role assignment. The consultant continues to authenticate through their home organization and should receive only the intended application permissions.

Incorrect Answers

B:

B2B direct connect is supported for Teams shared-channel collaboration and does not create a guest object in the resource tenant. It cannot by itself satisfy an unrelated enterprise application that requires a local B2B representation and assignment.

C:

Subscription Owner is an Azure Resource Manager privilege, not enterprise application sign-in provisioning. It would exceed the request and would not create the required guest assignment.

D:

Anonymous access would remove the required individual identity and application authorization controls. Azure resource tags do not replace Entra sign-in and app-role assignments.

Question 51

A B2B guest from a named partner organization receives an invitation but cannot redeem it. Your tenant has restrictive inbound cross-tenant settings for that partner, and the partner may have outbound restrictions for your tenant. Which TWO checks are appropriate? Select TWO answers.

  1. Review your tenant's inbound B2B collaboration settings for the partner, including relevant user and application scopes.
  2. Ignore your tenant's inbound controls because an invitation always overrides cross-tenant access policy.
  3. Delete the guest's home-tenant account and create a local shared administrator credential.
  4. Coordinate with the partner to verify its outbound B2B collaboration restrictions allow the intended connection.
  5. Grant Azure subscription Owner to the guest before fixing the authentication policy.

Explanation

Correct Answers

A:

Your tenant's cross-tenant access settings govern whether external identities from the partner can authenticate for B2B collaboration, independent of merely sending an invitation. Inspect the partner-specific inbound settings, users and groups, and application scope to ensure the approved reviewer is allowed. Also check external collaboration domain restrictions that may independently block invitations. Authorization to a resource can only be tested after this authentication policy path succeeds; the guest's resource role does not override a cross-tenant block.

D:

Cross-tenant B2B collaboration can require both the resource tenant's inbound policy and the partner tenant's outbound policy to permit the user and target application. Ask the partner administrator to inspect its outbound rules for your tenant and the relevant permitted identities. This is an independent prerequisite from configuring your own inbound settings, so both checks are necessary. Neither tenant should grant blanket access where narrower partner-specific permissions can satisfy the request.

Incorrect Answers

B:

Invitations do not bypass inbound cross-tenant access policies. A resource tenant can invite someone whose home organization or your own security controls still block authentication. Ignoring that policy would leave redemption failing and potentially encourage unsafe workarounds. Inspect the documented inbound rules and partner scope instead.

C:

A tenant administrator cannot legitimately delete an external partner's home account, and shared local administrator credentials would violate individual accountability. The guest already has an external identity intended for federation or B2B. Repair the compatible cross-tenant access policies rather than creating an overprivileged local workaround.

E:

Azure subscription Owner affects resource management after a principal is authorized; it cannot force acceptance of an invitation blocked by identity-provider or cross-tenant policy. Giving Owner prematurely would broaden the guest's eventual privileges without solving the failed redemption. Validate the collaboration boundary first.

Question 52

A company collaborates with two approved suppliers but prohibits guest invitations to any other external email domain. The security team wants a directory-level restriction enforced when users send invitations. Which configuration should it use?

  1. Place an Azure resource-group ReadOnly lock on the company's application deployment.
  2. Restrict invitation rights to Guest Inviter role holders without controlling destination email domains.
  3. Configure Microsoft Entra external collaboration restrictions to allow invitations only to the approved supplier domains.
  4. Restrict access to approved applications after guests sign in, but leave tenant invitation domains unrestricted.

Explanation

Correct Answer

C:

Microsoft Entra external collaboration settings include a domain-based invitation allowlist or blocklist. Under a policy that permits only two suppliers, allowlist those specific external domains and verify that cross-tenant access settings are compatible with the intended invitations. Invitations to unlisted domains can then be rejected according to the configured restriction. This controls B2B onboarding at the identity boundary rather than relying on user instructions or downstream resource assignment checks.

Incorrect Answers

A:

An Azure management lock restricts control-plane changes to resources; it does not inspect or authorize B2B invitation email domains. The invitation policy belongs to Microsoft Entra external identities, not a locked application resource group. This would leave unauthorized domain invitations possible.

B:

Guest Inviter restrictions govern who can send invitations, not which external domains may receive them. An authorized inviter could still invite an unapproved supplier unless a domain policy blocks it. Add the explicit approved-domain collaboration restriction to meet the destination requirement.

D:

Application assignments can limit which resources authenticated guests use but do not prevent an invitation to a prohibited external email domain. The policy expressly requires enforcement when inviting. Apply the directory external collaboration domain allowlist and check cross-tenant settings as necessary.

Question 53

An organization wants only designated directory administrators and Guest Inviter role holders to send B2B invitations. Today ordinary member users can also invite partners. What must be changed?

  1. Disable Azure Monitor alerting for invitation operations.
  2. Set the external collaboration Guest invite restriction to only supported administrator roles and delegate Guest Inviter selectively.
  3. Turn every B2B guest account into an internal member, regardless of its home tenant.
  4. Grant the approved inviters Azure subscription Contributor and assume that disables other inviters.

Explanation

Correct Answer

B:

The external collaboration Guest invite settings allow administrators to restrict invitation capability to users with specified directory roles. Choose the restrictive setting and grant the Guest Inviter role only to authorized staff who need that narrow operation. Verify that ordinary member users no longer have invitation rights, and retain audit monitoring for permitted invitations. This meets the policy without granting all designated inviters broad tenant-wide administrative privileges or altering existing guest accounts unnecessarily.

Incorrect Answers

A:

Azure Monitor reporting can record activity and alerts, but disabling it does not enforce which directory users can send B2B invitations. The required control is an authorization setting in Microsoft Entra external collaboration. Monitoring is useful for audit, not a replacement for invitation permissions.

C:

Converting external guests to members changes their identity classification without fixing the directory policy determining who may invite. It can also expand their default visibility and introduce inappropriate workforce lifecycle obligations. Adjust invitation-role restrictions while keeping legitimate guest identities in their intended collaboration category.

D:

Azure subscription Contributor permits certain infrastructure operations, not B2B invitation policy control. Assigning it to inviters would grant unrelated resource modification rights. It also would not automatically revoke the invitation capability from ordinary directory users, so the policy violation would remain.

Question 54

A B2B guest successfully redeems an invitation and signs in, but receives AuthorizationFailed when trying to read a private blob container assigned to the audit project. The container uses Azure RBAC data authorization. What should the administrator examine?

  1. Reset the user's home-tenant password because the initial sign-in proved authentication failed.
  2. Create a public container so authorization is no longer needed.
  3. Grant the guest Azure subscription Owner without checking the requested blob permission scope.
  4. Check the guest principal's data-plane RBAC access and assign the required blob role at the narrowest eligible scope.

Explanation

Correct Answer

D:

B2B authentication establishes who the guest is, while Azure RBAC determines what the principal can do to a protected storage resource. Inspect effective assignments, scope, and whether a suitable Storage Blob Data Reader or other required data role is present for the guest or eligible group. Assign only the needed data-plane permission on the container or appropriate minimal scope and allow propagation. This resolves an authenticated-but-not-authorized problem without broadening tenant or subscription administration privileges.

Incorrect Answers

A:

Successful B2B redemption and sign-in show that the user's identity was authenticated through the supported path. Resetting a partner user's password is not a resource-tenant fix for missing data-plane Azure RBAC. The authorization failure occurs after authentication, when permissions are evaluated for the blob.

B:

Changing a private container to public access would make data available without the approved authorization controls and could expose audit documents to unauthorized users. The scenario expects identity-based access for an approved guest. Correct the data-role assignment rather than removing access protection.

C:

Subscription Owner is an extremely broad control-plane role and does not directly represent the minimum Azure Blob data-plane permission. It can also enable unrelated resource and role management capabilities. The guest needs access to one audit container, so examine the proper data-role and scope rather than escalating to Owner.

Question 55

A partner developer reports two slightly different email addresses for the same colleague. Your tenant already contains a redeemed B2B guest object, but another admin is about to invite the second address as a brand-new guest. What should be checked first?

  1. Search for the existing guest object and verify the colleague's authoritative external identity before creating a duplicate representation.
  2. Delete the existing redeemed guest and issue a new invitation to the second address without checking identity continuity.
  3. Reset the existing guest’s redemption status for the second address without first verifying that it belongs to the same person.
  4. Change the partner's public MX records so both email addresses automatically map to one Entra directory object.

Explanation

Correct Answer

A:

An existing guest may represent the same human under an older email or identity-provider redemption path. Confirm the object's directory ID, current redemption identity and verified partner details before issuing another invitation. If the user legitimately changed email or identity provider, a supported redemption reset can preserve established object memberships rather than proliferating guest objects. This reduces duplicate access grants and avoids an offboarding gap where one alias is disabled but another remains authorized.

Incorrect Answers

B:

Deleting the current guest destroys the resource-tenant object referenced by existing application and group assignments. If the second email belongs to the same person, a supported redemption reset may preserve those links. Establish external identity continuity before choosing an operation that unnecessarily creates a new principal.

C:

Resetting redemption can change the identity used to access an existing guest object while preserving permissions. Doing so for an unverified second address could redirect access to the wrong external person. The administrator must first correlate identity and approved ownership, then use the supported update workflow if appropriate.

D:

Public mail routing records determine how email reaches a domain, not whether your Microsoft Entra tenant links two external identities to the same guest object. The home organization must govern its identity aliases. In your tenant, inspect the guest representation and supported redemption-update workflow.

Question 56

A quarterly external research project ends. Several partner B2B guests have group-based application access plus some directly shared document links. The organization must revoke access without affecting internal members. What should offboarding include?

  1. Delete the underlying enterprise application so every user loses it.
  2. Remove or disable the relevant guest permissions and objects as approved, then review residual shared links and sessions.
  3. Disable the guest objects but assume previously issued anonymous document-sharing links are automatically revoked.
  4. Remove guest membership from the research group but leave their direct enterprise application assignments intact.

Explanation

Correct Answer

B:

B2B guest access is managed by your resource tenant even though authentication may occur in the partner's tenant. Remove the guests from project groups and applications, disable or remove the approved guest objects where appropriate, and examine direct sharing links that might continue to grant access. Consider session revocation or access review when applicable and verify effective authorization after propagation. This distinguishes complete offboarding from merely removing one group membership while leaving another resource path active.

Incorrect Answers

A:

Deleting the entire application would disrupt internal and external users who still depend on it. The requirement targets only expired external project access. Directory guest and group permissions can be revoked without destroying the shared application or changing unrelated employees' assignments.

C:

Disabling authenticated guest accounts can block future guest sign-ins, but separately created anonymous or otherwise independent sharing links may remain usable. The scenario explicitly mentions direct document shares. Offboarding must inventory and revoke these alternative access paths before claiming all partner access has ended.

D:

Group removal may revoke inherited application access, but a directly assigned guest application role can remain effective. The project uses both group and direct access paths. Review and remove all approved guest grants as appropriate, then check existing shares and session state.

Question 57

An audit finds that invited B2B guests can enumerate more Microsoft Entra groups and directory profiles than the organization's privacy policy permits. The application itself works correctly. Which setting should be evaluated?

  1. Set enterprise application assignment required, but do not change the guest directory visibility restriction.
  2. An Azure resource-group delete lock, because it hides directory objects from guests.
  3. The Microsoft Entra external collaboration Guest user access restriction level.
  4. Block additional inbound partner organizations in cross-tenant access settings while keeping existing guests’ directory permissions broad.

Explanation

Correct Answer

C:

Microsoft Entra external collaboration settings offer different Guest user access levels, including a restrictive option that limits guests to their own directory profile information. Check the configured level, its interaction with application needs, and the effective directory visibility seen by a representative guest. Apply the most restrictive policy consistent with authorized collaboration. This fixes overbroad directory enumeration without changing the guest's legitimate application role or using infrastructure controls that do not govern identity visibility.

Incorrect Answers

A:

Application assignment requirements can protect a particular app, but the audit finding concerns what guests can enumerate in the Microsoft Entra directory itself. The two permission surfaces are separate. Change the external collaboration Guest user access level to restrict directory visibility while preserving the approved application path.

B:

Azure management locks can prevent deleting or editing resources but do not define the visibility of Microsoft Entra directory information to external users. An application resource group cannot substitute for the guest directory access configuration. The privacy control must operate at the identity directory.

D:

Cross-tenant access rules influence which external identities can authenticate, but they do not directly narrow directory enumeration for guests who remain authorized to sign in. The stated users are already authenticated and browsing too much. Apply the guest-specific directory visibility control to address that permission boundary.

Question 58

A company grants temporary B2B guests access to selected groups and enterprise applications. Security wants managers to reapprove guest membership each quarter and remove access when reviewers deny renewal. What feature best supports this ongoing control?

  1. Use Azure Resource Manager locks on the guests' application resource groups.
  2. Rely entirely on a one-time invitation email and never inspect membership again.
  3. Convert all external guests into perpetual tenant Global Administrators.
  4. Use appropriately licensed Microsoft Entra access reviews with assigned reviewers and enforceable review outcomes.

Explanation

Correct Answer

D:

Microsoft Entra access reviews can evaluate guest membership in groups and assignments to enterprise applications and collect periodic reviewer decisions. Configure the review scope, designated approvers, schedule and actions for denied or nonresponsive access according to the supported feature and licensing requirements. Verify that review outcomes are applied and auditable rather than merely collecting responses. This makes temporary external collaboration conditional on continued approval and supports targeted revocation when a project ends.

Incorrect Answers

A:

Resource locks govern Azure management actions, not the periodic governance of guest membership in Entra groups or enterprise applications. They do not ask managers for access decisions or automatically process guest review results. The scenario needs identity governance rather than resource immutability.

B:

A successful invitation authorizes initial collaboration but does not determine whether an external contract is still valid three months later. Permanent membership without review can preserve stale access. A recurring review evaluates current business justification instead of relying on an old onboarding decision.

C:

Global Administrator grants highly privileged directory control and is the opposite of time-limited least-privilege access. Making all guests administrators would compound rather than resolve governance risk. Reviewer decisions should narrow or remove existing resource permissions, not promote temporary collaborators who require only scoped project access.

Question 59

A B2B partner consultant needs to use one enterprise application, but an administrator has granted the consultant Global Administrator on the resource tenant. What is the better permission model?

  1. Remove the unnecessary directory-wide role and grant only the application role and any separately necessary resource-scoped permissions.
  2. Leave Global Administrator because every guest must be a tenant admin to access an application.
  3. Create a new Azure subscription and make the consultant Owner of all its resources.
  4. Give the consultant a shared global administrator account to make auditing simpler.

Explanation

Correct Answer

A:

Application authorization should reflect the single approved service, not confer tenant-wide directory administration. Remove the inappropriate Global Administrator assignment and grant the consultant the particular enterprise application role or group-based application membership required. If the application also accesses Azure resources, evaluate those RBAC roles separately at the smallest supported scope. Validate the guest's effective permissions after changes. This respects the distinction between authentication through B2B and authorization to a specific application or resource.

Incorrect Answers

B:

B2B guests can authenticate and be authorized for a specific application without becoming Global Administrators. Keeping such a role expands the consultant's ability to change unrelated tenant identity settings. The narrow application requirement does not justify directory-wide control or bypass normal least-privilege reviews.

C:

Azure subscriptions provide resource management and billing boundaries but do not represent a narrowly scoped enterprise application role. Making the consultant Owner would add broad infrastructure privileges unrelated to using the app. The identity should receive an approved application assignment, not an unnecessary cloud account-management position.

D:

Shared administrator accounts obscure which person performed an action and are difficult to revoke for a single consultant. They also multiply high-privilege credential exposure. An individually identifiable B2B guest with narrowly scoped application permission is safer and easier to audit.

Question 60

A B2B collaborator has changed companies and must redeem access using a new email address. Your tenant wants to preserve the existing guest object ID, group memberships, and app assignments. What Microsoft Entra feature is appropriate?

  1. Permanently delete the existing guest and create an unrelated local workforce account.
  2. Reset the existing guest's redemption status, set the supported new email information, and send a new invitation.
  3. Update only the guest object’s UPN string but do not reset redemption against the new sign-in identity.
  4. Ask the partner to use the old employee's password after leaving that company.

Explanation

Correct Answer

B:

Microsoft Entra supports resetting B2B guest redemption when a person needs a different sign-in email or identity provider. Update the intended new email in the existing guest's supported properties, reset redemption through the admin center or documented API, and reinvite the authorized person. The original guest object ID and its group and application assignments can be retained, subject to feature permissions and limitations. Validate the newly redeemed identity before assuming it has the desired access.

Incorrect Answers

A:

Deleting the guest discards the directory object referenced by existing group and enterprise application assignments. A new workforce account also changes the collaboration identity lifecycle and may not belong to the intended external person. The requirement specifically asks to preserve existing identity links, so use the supported redemption-update flow.

C:

A guest UPN in the resource tenant is not by itself the external identity-provider credential used for B2B redemption. Microsoft documents a redemption-reset flow that updates sign-in email while retaining the original guest object. Editing a display or UPN string alone would not reliably rebind authentication.

D:

Using a former employee's password violates identity ownership and security policy and might be impossible after home-tenant offboarding. The collaboration should transfer to the approved individual's new identity with a verifiable invitation and preserved resource-tenant object where supported. A redemption reset avoids unsafe credential sharing.