Microsoft MS-102 (Microsoft 365 Administrator) Practice Test 10

Question 90

An organization retains Microsoft Entra Connect Sync but wants a standby configuration available during server failure. What supported deployment pattern is relevant?

  1. Configure a staging-mode Connect Sync server
  2. Microsoft Entra Connect synchronization rules
  3. Microsoft Entra Cloud Sync
  4. Configure OU-based synchronization filtering

Explanation

Correct Answer

A:

A staging-mode server imports and synchronizes directory data but does not actively export changes until promoted. This supports a controlled failover model without two servers exporting simultaneously.

Incorrect Answers

B:

Although the option maps and transforms attributes within the synchronization engine, the actual requirement is designing standby sync-engine recovery. The appropriate control keeps a secondary Connect Sync server ready without active exports.

C:

This choice synchronizes identities using lightweight agents and cloud orchestration. The scenario concerns designing standby sync-engine recovery; the relevant function keeps a secondary Connect Sync server ready without active exports.

D:

The feature constrains directory synchronization to selected on-premises OUs, a separate task from designing standby sync-engine recovery; the appropriate configuration keeps a secondary Connect Sync server ready without active exports.

Question 91

Only staff in selected on-premises organizational units should be synchronized to the tenant. Where should the scope restriction be established?

  1. Deploy multiple active Cloud Sync provisioning agents
  2. Cloud-only identities in Microsoft Entra ID
  3. Configure OU-based synchronization filtering
  4. Pass-through authentication
  5. Configure a staging-mode Connect Sync server

Explanation

Correct Answer

C:

Organizational-unit filtering in a supported synchronization configuration limits which source directory containers are included. It prevents unnecessary identities from being provisioned when the scope is defined correctly.

Incorrect Answers

A:

This setting supplies redundant lightweight provisioning agents for cloud-managed sync. The missing piece for limiting the synchronized identity population is a capability that constrains directory synchronization to selected on-premises OUs.

B:

This feature creates users directly in the cloud without an on-premises source. To handle limiting the synchronized identity population, use a feature that constrains directory synchronization to selected on-premises OUs.

D:

This setting checks cloud sign-ins against on-premises AD through agents. The question instead concerns limiting the synchronized identity population; its solution constrains directory synchronization to selected on-premises OUs.

E:

That choice keeps a secondary Connect Sync server ready without active exports; it does not implement limiting the synchronized identity population. The relevant feature constrains directory synchronization to selected on-premises OUs.

Question 92

A directory architect must verify which attribute transformations the Connect Sync engine will apply before export. Which configuration area should be inspected?

  1. Configure OU-based synchronization filtering
  2. Configure a staging-mode Connect Sync server
  3. Microsoft Entra Connect synchronization rules
  4. IdFix directory attribute remediation tool

Explanation

Correct Answer

C:

Synchronization rules govern supported inbound and outbound attribute flows and transformations in the Connect Sync engine. Changes to these rules require care because they can alter identity matching or exported values.

Incorrect Answers

A:

OU-based filtering decides which on-premises directory objects enter the synchronization scope. It does not reveal the attribute-flow or transformation logic needed for this investigation.

B:

The alternative keeps a secondary Connect Sync server ready without active exports. By contrast, the requested outcome of inspecting attribute flow logic needs a control that maps and transforms attributes within the synchronization engine.

D:

This feature checks source directory attributes for common synchronization blockers. The distinct requirement—inspecting attribute flow logic—is met by a control that maps and transforms attributes within the synchronization engine.

Question 93

An organization wants cloud sign-in to validate a synchronized password without redirecting each login to an on-premises authentication server. Which strategy is suitable?

  1. Pass-through authentication
  2. Password hash synchronization
  3. Federated authentication
  4. Correct duplicate proxyAddresses in the source directory

Explanation

Correct Answer

B:

Password hash synchronization provides Entra ID with a derived form of the on-premises password hash for cloud authentication. User sign-ins can be validated by the cloud service without contacting a local agent at every login.

Incorrect Answers

A:

The feature checks cloud sign-ins against on-premises AD through agents, a separate task from authenticating synchronized users without per-login on-premises checks; the appropriate configuration supports cloud password validation using synchronized password hash material.

C:

This operation delegates authentication to an external trusted identity provider; the present scenario instead involves authenticating synchronized users without per-login on-premises checks. The fitting solution supports cloud password validation using synchronized password hash material.

D:

That option resolves duplicate mail alias attributes in the authoritative directory, which serves a different purpose. The specified task, authenticating synchronized users without per-login on-premises checks, calls for functionality that supports cloud password validation using synchronized password hash material.

Question 94

A company must validate each synchronized user's password against on-premises Active Directory without deploying federation. Which model fits?

  1. Federated authentication
  2. Pass-through authentication
  3. Microsoft Entra Connect synchronization rules
  4. Cloud-only identities in Microsoft Entra ID

Explanation

Correct Answer

B:

Pass-through authentication sends validation requests through supported on-premises agents to Active Directory. It preserves on-premises password validation but depends on sufficient agent availability and connectivity.

Incorrect Answers

A:

Its effect is different: it delegates authentication to an external trusted identity provider. Meeting the stated objective of keeping password validation in Active Directory depends on a feature that checks cloud sign-ins against on-premises AD through agents.

C:

The choice maps and transforms attributes within the synchronization engine, but it is not enough for keeping password validation in Active Directory. The correct type of configuration checks cloud sign-ins against on-premises AD through agents.

D:

This creates users directly in the cloud without an on-premises source, but it does not provide keeping password validation in Active Directory; the necessary control instead checks cloud sign-ins against on-premises AD through agents.

Question 95

A legacy enterprise uses its own federated identity provider and needs sign-in decisions handled through that provider under a supported trust. Which model applies?

  1. Federated authentication
  2. Source-anchor and identity matching
  3. Password hash synchronization
  4. Pass-through authentication

Explanation

Correct Answer

A:

Federation redirects authentication to a trusted identity provider according to the configured domain arrangement. It introduces external identity infrastructure dependencies that differ from cloud password hash validation.

Incorrect Answers

B:

Although the option associates source directory identities with the correct cloud objects, the actual requirement is using established federation for user sign-in. The appropriate control delegates authentication to an external trusted identity provider.

C:

This choice supports cloud password validation using synchronized password hash material. The scenario concerns using established federation for user sign-in; the relevant function delegates authentication to an external trusted identity provider.

D:

This setting checks cloud sign-ins against on-premises AD through agents. The missing piece for using established federation for user sign-in is a capability that delegates authentication to an external trusted identity provider.

Question 96

A startup has no on-premises Active Directory and creates every employee directly in Microsoft Entra ID. Which identity model needs no directory synchronization?

  1. Cloud-only identities in Microsoft Entra ID
  2. Configure a staging-mode Connect Sync server
  3. Federated authentication
  4. Pass-through authentication

Explanation

Correct Answer

A:

Cloud-only users are authoritative in Entra ID and do not depend on an on-premises synchronization engine. Their credentials and supported user attributes can be managed in the cloud.

Incorrect Answers

B:

The feature keeps a secondary Connect Sync server ready without active exports, a separate task from avoiding unnecessary hybrid synchronization; the appropriate configuration creates users directly in the cloud without an on-premises source.

C:

This feature delegates authentication to an external trusted identity provider, but the administrator needs avoiding unnecessary hybrid synchronization. The appropriate control creates users directly in the cloud without an on-premises source.

D:

This feature checks cloud sign-ins against on-premises AD through agents. To handle avoiding unnecessary hybrid synchronization, use a feature that creates users directly in the cloud without an on-premises source.

Question 97

Users were created in Microsoft Entra ID before hybrid sync, and IT wants corresponding on-premises accounts correctly linked rather than duplicated. Which identity concept must be planned?

  1. Source-anchor and identity matching
  2. Correct duplicate proxyAddresses in the source directory
  3. Verify and configure the required domain suffix in Microsoft Entra ID
  4. Accidental delete prevention threshold in Connect Sync

Explanation

Correct Answer

A:

Microsoft Entra synchronization uses stable source identifiers and supported matching behavior to associate on-premises and cloud objects. An incorrect match strategy can generate duplicates or conflicts rather than joining intended identities.

Incorrect Answers

B:

That option resolves duplicate mail alias attributes in the authoritative directory, not the mechanism for linking pre-existing cloud and on-premises accounts. A suitable service associates source directory identities with the correct cloud objects.

C:

That choice establishes an accepted sign-in domain namespace in the tenant; it does not implement linking pre-existing cloud and on-premises accounts. The relevant feature associates source directory identities with the correct cloud objects.

D:

The option blocks unusually large synchronized deletion exports, not the action specified. For linking pre-existing cloud and on-premises accounts, the needed service associates source directory identities with the correct cloud objects.

Question 98

A new company's AD user UPN suffix is not an accepted verified domain in the Microsoft 365 tenant. What should be addressed before relying on that sign-in name?

  1. Verify and configure the required domain suffix in Microsoft Entra ID
  2. Password hash synchronization
  3. The synchronized attribute is mastered in on-premises Active Directory
  4. Correct duplicate proxyAddresses in the source directory

Explanation

Correct Answer

A:

User principal names must use an appropriate accepted domain for the target sign-in experience. Adding and verifying the intended custom domain allows consistent user naming across hybrid identity systems.

Incorrect Answers

B:

The alternative supports cloud password validation using synchronized password hash material. By contrast, the requested outcome of aligning synchronized user principal names needs a control that establishes an accepted sign-in domain namespace in the tenant.

C:

This feature keeps selected account attributes under on-premises source authority. The distinct requirement—aligning synchronized user principal names—is met by a control that establishes an accepted sign-in domain namespace in the tenant.

D:

This operation resolves duplicate mail alias attributes in the authoritative directory; the present scenario instead involves aligning synchronized user principal names. The fitting solution establishes an accepted sign-in domain namespace in the tenant.

Question 99

Two source accounts share an email proxy address and synchronization rejects one of the values. Where should the conflict be fixed?

  1. Source-anchor and identity matching
  2. Cloud Sync provisioning-agent service and connectivity
  3. Verify and configure the required domain suffix in Microsoft Entra ID
  4. Correct duplicate proxyAddresses in the source directory

Explanation

Correct Answer

D:

A proxy address must be unique for supported recipient and identity provisioning. Fixing the duplicate at its authoritative source prevents a synchronization cycle from restoring the invalid value.

Incorrect Answers

A:

That option associates source directory identities with the correct cloud objects, which serves a different purpose. The specified task, removing conflicting synchronized email aliases, calls for functionality that resolves duplicate mail alias attributes in the authoritative directory.

B:

The choice brokers synchronization requests between Cloud Sync and local Active Directory, but it is not enough for removing conflicting synchronized email aliases. The correct type of configuration resolves duplicate mail alias attributes in the authoritative directory.

C:

The feature establishes an accepted sign-in domain namespace in the tenant, a separate task from removing conflicting synchronized email aliases; the appropriate configuration resolves duplicate mail alias attributes in the authoritative directory.

Question 100

A synced employee's surname is correct in on-premises AD but repeatedly reverts after a cloud portal edit. What explains the behavior?

  1. Verify and configure the required domain suffix in Microsoft Entra ID
  2. Federated authentication
  3. The synchronized attribute is mastered in on-premises Active Directory
  4. Correct duplicate proxyAddresses in the source directory

Explanation

Correct Answer

C:

Attributes synchronized from an authoritative on-premises source should generally be updated at that source. Direct cloud edits to managed attributes may be blocked or overwritten on subsequent synchronization.

Incorrect Answers

A:

Although the option establishes an accepted sign-in domain namespace in the tenant, the actual requirement is making persistent changes to synchronized user attributes. The appropriate control keeps selected account attributes under on-premises source authority.

B:

This delegates authentication to an external trusted identity provider, but it does not provide making persistent changes to synchronized user attributes; the necessary control instead keeps selected account attributes under on-premises source authority.

D:

This choice resolves duplicate mail alias attributes in the authoritative directory. The scenario concerns making persistent changes to synchronized user attributes; the relevant function keeps selected account attributes under on-premises source authority.

Microsoft 365 Administrator (MS-102) Practice Tests