SC-300 domain - 25% of the exam

Implement and Manage User Identities

Implement and Manage User Identities is 25% of the SC-300 exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

70
Practice questions
6
Objectives
46
Medium
24
Hard

Where people go wrong

  • Confusing which cross-tenant capability creates guest objects

    The wrong answers swap B2B collaboration, B2B direct connect and cross-tenant synchronisation. B2B collaboration and cross-tenant synchronisation both produce B2B user objects in the resource or target tenant, so they fail a requirement that forbids guest accounts. B2B direct connect builds mutual trust for Teams shared channels without any guest object. When the need is guest objects that Conditional Access can target, direct connect is the wrong choice. B2C serves consumer-facing apps.

    See it in a sample question
  • Misassigning what each hybrid sign-in feature does

    The wrong answers give a sign-in feature a job it does not have. Password hash synchronisation uploads a re-hashed credential, so it fails a mandate against storing any hash in the cloud; pass-through authentication validates against on-premises Active Directory instead. Pass-through authentication does not by itself sign users in silently. Seamless single sign-on is an add-on that issues Kerberos tickets on domain-joined devices. It cannot validate passwords alone, and it does not give FIDO2 sign-ins on-premises access, which needs Microsoft Entra Kerberos.

    See it in a sample question
  • Mistaking staging mode for monitoring, matching or cutover

    Staging mode appears as a wrong option in questions about monitoring, matching and domain conversion. It is a standby Microsoft Entra Connect Sync configuration that does not export until promoted. It cannot monitor AD FS or pass-through authentication agent health, match on-premises objects to existing cloud accounts, or change a domain's federation setting. Microsoft Entra Connect Health covers monitoring, soft matching covers matching on mail or proxyAddresses, and converting the domain from federated to managed covers the cutover.

    See it in a sample question
  • Crediting one synchronisation engine with the other's strengths

    The wrong options give Connect Sync and Cloud Sync each other's capabilities. Connect Sync can serve multiple forests but needs a full synchronisation server, so it is not the lightweight, Microsoft-managed choice for disconnected forests; Cloud Sync is. Cloud Sync cannot deliver full Exchange hybrid writeback or device synchronisation for hybrid join, which keeps Connect Sync required for those workloads. Within Cloud Sync, organisational unit scope comes from scoping filters, not attribute mappings.

    See it in a sample question
  • Misjudging how administrative unit scope limits a role

    The wrong answers misread how scope limits a role. A role assigned at tenant scope applies across the directory, so it cannot confine a help desk to one branch; an administrative unit assignment does. Roles combine per assignment, so a tenant-scoped read role neither cancels nor widens a Helpdesk Administrator assignment scoped to one unit. A standard administrative unit also leaves tenant-scoped administrators with their power over the members; a restricted management administrative unit is what blocks them.

    See it in a sample question

Objectives in this domain

What to study

The official documents this domain's practice questions cite most.

Sample questions from this domain

Free sampleImplement and Manage User Identitieshard

Two partner organisations on separate Microsoft Entra tenants want their members to join each other's Microsoft Teams shared channels and use shared apps with their home accounts, and a requirement states that no guest user objects may be created in either tenant. Which cross-tenant capability satisfies this without creating guest accounts?

  • AConfigure B2B collaboration in cross-tenant access settings, because inviting the partners as collaboration users grants the same shared-channel access through their home credentials.
  • BConfigure B2B direct connect in cross-tenant access settings, because it establishes a mutual trust that lets external members access Teams shared channels without any guest object being created. Correct
  • CConfigure cross-tenant synchronisation from each tenant to the other, because it links the partner members so they can reach shared channels without separate accounts.
  • DConfigure direct federation with each partner domain, because federating the domains lets the members sign in to shared channels using their existing identity provider.
B2B direct connect establishes a mutual tenant trust for Teams shared-channel and shared-app access using home accounts and creates no guest user object. B2B direct connect is configured in cross-tenant access settings as inbound and outbound trust, allowing users to participate in Teams Connect shared channels with their own home-tenant identity and no guest provisioning. B2B collaboration and cross-tenant synchronisation both create guest objects, and direct federation only changes how an invited guest authenticates.

Why A is wrong: B2B collaboration does grant access with home credentials, but it creates a guest user object in the resource tenant, which directly violates the no-guest-object requirement.

Why B is correct: B2B direct connect creates a mutual trust between tenants that authorises shared-channel and shared-app access using the user's home account, and it provisions no guest object in either tenant.

Why C is wrong: Cross-tenant synchronisation reaches shared resources only by provisioning B2B collaboration guest objects, so it creates the very accounts the requirement forbids.

Why D is wrong: Direct federation governs how invited external users authenticate, but it still relies on a guest object being created for the user and is not the shared-channel trust mechanism.

Free sampleImplement and Manage User Identitieshard

An organisation must let on-premises users sign in to Microsoft 365 with their Active Directory password, but a security mandate forbids any password hashes, even hashed twice, from being stored in the cloud. Authentication must succeed even if a single authentication agent is offline. Which sign-in method satisfies the mandate?

  • AConfigure password hash synchronisation, because the synchronised hash is itself hashed again before upload, which the mandate treats as acceptable cloud storage.
  • BConfigure pass-through authentication and install at least two authentication agents, because passwords are validated against on-premises Active Directory and no hashes are stored in the cloud. Correct
  • CConfigure federation with Active Directory Federation Services as the only authority and rely on a single federation server for password validation.
  • DConfigure seamless single sign-on with no other sign-in method, because Kerberos-based seamless single sign-on validates the Active Directory password without storing a hash.
Pass-through authentication validates passwords against on-premises Active Directory and stores no password hash in the cloud, with multiple agents giving high availability. Pass-through authentication uses on-premises agents to validate each sign-in against Active Directory in real time, so no password hash is ever placed in Microsoft Entra ID, and deploying additional agents removes the single point of failure. Password hash synchronisation uploads a credential, federation alone needs redundant servers, and seamless single sign-on is only a convenience feature.

Why A is wrong: Password hash synchronisation does upload a re-hashed credential into the cloud, which directly violates the mandate forbidding any password hashes from being stored in the cloud.

Why B is correct: Pass-through authentication validates each password directly against on-premises Active Directory and stores no password hash in Microsoft Entra ID, and multiple agents provide resilience if one is offline.

Why C is wrong: Federation keeps authentication on-premises, but a single federation server has no resilience, so it fails the requirement that authentication survive one component being offline.

Why D is wrong: Seamless single sign-on only removes the prompt on domain-joined devices; it is an add-on and cannot validate passwords on its own as a sign-in method.

Free sampleImplement and Manage User Identitiesmedium

A hybrid environment uses pass-through authentication with two authentication agents. The identity team needs a dashboard showing whether each authentication agent is active, the volume of authentication requests, and alerts when an agent stops responding, without writing custom monitoring scripts. Which feature delivers this visibility?

  • AThe Microsoft Entra sign-in logs filtered by authentication method, because they list every pass-through authentication agent and raise alerts when an agent goes offline.
  • BMicrosoft Entra Connect Health for pass-through authentication, because it shows each agent's status, authentication request volume, and raises alerts when an agent is unhealthy. Correct
  • CMicrosoft Entra Connect Sync staging mode reporting, because a staging server tracks the status of each pass-through authentication agent and alerts on failures.
  • DThe Microsoft Entra service health page, because it reports the operational status of each customer pass-through authentication agent and request volumes.
Microsoft Entra Connect Health monitors pass-through authentication agents, reporting per-agent status, request volume, and alerts without custom scripting. Connect Health extends beyond AD FS and sync monitoring to cover pass-through authentication agents, presenting each agent's active state, authentication request throughput, and proactive alerts in the Microsoft Entra admin centre. Sign-in logs track user events, staging mode is a sync role, and the service health page covers Microsoft incidents rather than customer agents.

Why A is wrong: Sign-in logs record individual user authentications but do not show per-agent health status or generate alerts when a pass-through authentication agent stops responding.

Why B is correct: Connect Health monitors pass-through authentication agents, displaying per-agent active status and request throughput while alerting when an agent stops responding, which matches the requirement exactly.

Why C is wrong: Staging mode is a standby synchronisation role and has no relationship to pass-through authentication agent health monitoring or alerting.

Why D is wrong: The service health page reports Microsoft service incidents, not the status of a customer's own pass-through authentication agents or their request volumes.

Free sampleImplement and Manage User Identitieshard

A company has three disconnected Active Directory forests acquired through mergers, each managed by a separate IT team, and wants to synchronise all of them to one Microsoft Entra tenant. The architecture team requires a lightweight, Microsoft-managed provisioning service that avoids deploying a full synchronisation server per forest. Which synchronisation technology meets this requirement?

  • ADeploy Microsoft Entra Cloud Sync with a lightweight provisioning agent in each forest, because the service is Microsoft-managed and supports disconnected multi-forest topologies. Correct
  • BDeploy Microsoft Entra Connect Sync on a server in each forest, because only the full sync engine can read objects from multiple disconnected Active Directory forests.
  • CDeploy a single Microsoft Entra Connect Sync server with a custom rule set that reaches across all three disconnected forests over the public internet.
  • DDeploy Microsoft Entra Connect Health agents in each forest, because the health service can provision identities from disconnected forests into the tenant.
Microsoft Entra Cloud Sync uses lightweight Microsoft-managed agents and is the preferred choice for synchronising disconnected multi-forest Active Directory environments. Cloud Sync places a lightweight provisioning agent in each forest and performs the synchronisation logic in a Microsoft-managed cloud service, so disconnected forests with no trust between them are supported without a full sync server per forest. Connect Sync requires a server and network reachability, and Connect Health only monitors.

Why A is correct: Cloud Sync uses lightweight agents that report to a Microsoft-managed cloud service and natively supports disconnected forests, matching the lightweight multi-forest requirement exactly.

Why B is wrong: Connect Sync can serve multiple forests, but it requires a full synchronisation server and is not the lightweight Microsoft-managed agent service the architecture team asked for.

Why C is wrong: Disconnected forests have no shared trust path for one Connect Sync server to reach them, and reaching across forests over the internet is not a supported synchronisation design.

Why D is wrong: Connect Health only monitors the health and performance of identity synchronisation; it does not provision or synchronise any directory objects into the tenant.

Free sampleImplement and Manage User Identitiesmedium

A help desk team manages only the staff in the Sydney branch and must be able to reset those users' passwords, but must not be able to reset passwords for staff in any other branch. The identity team wants to grant this with the least standing privilege. Which approach meets the requirement?

  • AAssign the help desk team the Helpdesk Administrator role at tenant scope, then create a dynamic group that contains only the Sydney branch users for reference.
  • BCreate a custom role with password reset permissions and assign it to the help desk team at tenant scope, relying on a naming convention to limit it.
  • CCreate an administrative unit containing the Sydney branch users, then assign the help desk team the Helpdesk Administrator role scoped to that administrative unit. Correct
  • DCreate a security group of the Sydney branch users, make the help desk team owners of that group, and rely on group ownership to allow password resets.
Administrative units scope a directory role assignment to a defined set of users, enforcing least-privilege management boundaries for delegated administration. Administrative units act as containers that bound a role assignment so the assigned administrator can act only on the members of that unit. Scoping Helpdesk Administrator to the Sydney administrative unit limits password resets to those users, whereas tenant-scoped roles apply directory-wide and group ownership does not confer password reset rights.

Why A is wrong: A tenant-scoped Helpdesk Administrator role can reset passwords for users across the whole directory, and a reference group does not constrain where the role applies, so the Sydney-only boundary is not enforced.

Why B is wrong: A custom role assigned at tenant scope still applies directory-wide, and a naming convention is not an access boundary, so members could reset passwords for users in other branches.

Why C is correct: An administrative unit restricts the role assignment to its members, so a Helpdesk Administrator scoped to the Sydney administrative unit can manage only those users and no others, matching least-privilege scope.

Why D is wrong: Group ownership lets owners manage membership, not reset member passwords, so this confuses object management with directory role permissions and does not grant the required capability.

Other domains in this exam

See also the SC-300 cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by Microsoft. Original, blueprint-aligned practice material only.