nerdexam
Microsoft

SC-300 · Question #5

You need to implement the planned changes and technical requirements for the marketing department. What should you do? To answer, select the appropriate options in the answer area. NOTE: Each…

The correct answer is To configure user access:: An access package; To enable collaboration with fabrikam.com:: A connected organization. Hotspot Explanation: Marketing Department Access & Collaboration --- Dropdown 1: To configure user access -> An access package Why it's correct: The requirement is an automated approval workflow for new marketing users to gain access to a SharePoint site, group, and app…

Submitted by miguelv· Mar 6, 2026Plan and implement identity governance
Case Study ScenarioShared context for this question
Case Study 1 - Contoso, Ltd Overview Contoso, Ltd. is a consulting company that has a main office in Montreal and branch offices in London and Seattle. Contoso has a partnership with a company named Fabrikam, Inc. Fabrikam has an Azure Active Directory (Azure AD) tenant named fabrikam.com. Existing Environment. Existing Environment The on-premises network of Contoso contains an Active Directory domain named contoso.com. The domain contains an organizational unit (OU) named Contoso_Resources. The Contoso_Resources OU contains all users and computers. The contoso.com Active Directory domain contains the users shown in the following table. Existing Environment. Microsoft 365/Azure Environment Contoso has an Azure AD tenant named contoso.com that has the following associated licenses: Microsoft Office 365 Enterprise E5 Enterprise Mobility + Security Windows 10 Enterprise E3 Project Plan 3 Azure AD Connect is configured between Azure AD and Active Directory Domain Services (AD DS). Only the Contoso_Resources OU is synced. Helpdesk administrators routinely use the Microsoft 365 admin center to manage user settings. User administrators currently use the Microsoft 365 admin center to manually assign licenses. All users have all licenses assigned besides the following exceptions: The users in the London office have the Microsoft 365 Phone System license unassigned. The users in the Seattle office have the Yammer Enterprise license unassigned. Security defaults are disabled for contoso.com. Contoso uses Azure AD Privileged Identity Management (PIM) to protect administrative roles. Existing Environment. Problem Statements Contoso identifies the following issues: Currently, all the helpdesk administrators can manage user licenses throughout the entire Microsoft 365 tenant. The user administrators report that it is tedious to manually configure the different license requirements for each Contoso office. The helpdesk administrators spend too much time provisioning internal and guest access to the required Microsoft 365 services and apps. Currently, the helpdesk administrators can perform tasks by using the User administrator role without justification or approval. When the Logs node is selected in Azure AD, an error message appears stating that Log Analytics integration is not enabled. Requirements. Planned Changes Contoso plans to implement the following changes: Implement self-service password reset (SSPR). Analyze Azure audit activity logs by using Azure Monitor. Simplify license allocation for new users added to the tenant. Collaborate with the users at Fabrikam on a joint marketing campaign. Configure the User administrator role to require justification and approval to activate. Implement a custom line-of-business Azure web app named App1. App1 will be accessible from the internet and authenticated by using Azure AD accounts. For new users in the marketing department, implement an automated approval workflow to provide access to a Microsoft SharePoint Online site, group, and app. Contoso plans to acquire a company named Adatum Corporation. One hundred new ADatum users will be created in an Active Directory OU named Adatum. The users will be located in London and Seattle. Requirement. Technical Requirements Contoso identifies the following technical requirements: All users must be synced from AD DS to the contoso.com Azure AD tenant. App1 must have a redirect URI pointed to https://contoso.com/auth- response. License allocation for new users must be assigned automatically based on the location of the user. Fabrikam users must have access to the marketing department's SharePoint site for a maximum of 90 days. Administrative actions performed in Azure AD must be audited. Audit logs must be retained for one year. The helpdesk administrators must be able to manage licenses for only the users in their respective office. Users must be forced to change their password if there is a probability that the users' identity was compromised.

Question

You need to implement the planned changes and technical requirements for the marketing department. What should you do? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point. Answer:

Answer Area

  • To configure user access:An access package
    An access packageAn access reviewA conditional access policy
  • To enable collaboration with fabrikam.com:A connected organization
    An accepted domainA connected organizationA custom domain name

Explanation

Hotspot Explanation: Marketing Department Access & Collaboration


Dropdown 1: To configure user access -> An access package

Why it's correct:

The requirement is an automated approval workflow for new marketing users to gain access to a SharePoint site, group, and app - bundled together, with Fabrikam users limited to 90 days.

Azure AD Entitlement Management uses access packages to:

  • Bundle multiple resources (SharePoint site + group + app) into a single requestable unit
  • Configure approval workflows (automated, with approvers)
  • Set time-limited access (e.g., expiration after 90 days for guests)
  • Allow external users from connected organizations to request access

This maps exactly to the requirements stated.

Why the others are wrong:

  • Access review - Used to periodically audit existing access (e.g., "should this user still have access?"). It doesn't provision or automate initial access grants.
  • Conditional access policy - Controls how users authenticate (MFA, compliant device, location). It doesn't bundle resources or create approval workflows for new access requests.

Dropdown 2: To enable collaboration with fabrikam.com -> A connected organization

Why it's correct:

A connected organization is an Entitlement Management concept that registers an external Azure AD tenant (fabrikam.com) so its users can be granted access to access packages. Once configured:

  • Fabrikam users can discover and request the access package
  • Policies can target "users from connected organizations" specifically
  • The 90-day expiration policy applies cleanly to these external users

Why the others are wrong:

  • An accepted domain - This is an Exchange Online / email routing concept. It defines domains that receive email in your tenant. It has no bearing on cross-tenant resource access or Entitlement Management.
  • A custom domain name - This adds a verified domain to your own Azure AD tenant (e.g., so your users can sign in as [email protected]). It does nothing to enable external collaboration with Fabrikam's tenant.

Core Concept Summary

Both answers fall under Azure AD Entitlement Management, which is part of the Identity Governance feature set (requires Azure AD P2 / EMS E5 - which Contoso has). The pattern is:

  1. Register Fabrikam as a connected organization
  2. Create an access package bundling the SharePoint site/group/app
  3. Set a policy targeting connected org users, with approval workflow and 90-day expiration

Topics

#Azure AD Identity Governance#Access Packages#Entitlement Management#External Collaboration

Community Discussion

No community discussion yet for this question.

Full SC-300 Practice