Microsoft SC-300 Practice Test 15
Question 140
A tenant migrates its Entra Connect server but wants to avoid two active exporters. What configuration is relevant?
- Inspect Entra Connect Sync connector synchronization status and logs.
- Use the automatically selected Cloud Sync source anchor rather than force an arbitrary attribute.
- Use the documented staging-mode migration procedure.
- Investigate export errors and fix the source attributes or sync rules.
Explanation
Correct Answer
C:Staging mode prevents concurrent active export while a replacement server is validated. This matters here because a tenant migrates its Entra Connect server but wants to avoid two active exporters. What configuration is relevant.
Incorrect Answers
A:Connect Sync is responsible for the configured on-premises AD object export into Entra. Staging mode prevents concurrent active export while a replacement server is validated.
B:Cloud Sync chooses the stable anchor based on documented directory attributes.
D:Repeat exports cannot repair contradictory or unsupported source directory values. This matters here because a tenant migrates its Entra Connect server but wants to avoid two active exporters. What configuration is relevant.
Question 141
A team edited a built-in synchronization rule directly and upgrades are failing. What practice is safer?
- Use the automatically selected Cloud Sync source anchor rather than force an arbitrary attribute.
- Check selected directories, OU filtering and object inclusion conditions.
- Review the documented soft-match or hard-match process and source anchor.
- Use supported custom synchronization rules with explicit precedence.
Explanation
Correct Answer
D:Unsupported changes to built-in rules can be overwritten or destabilize upgrades. This matters here because a team edited a built-in synchronization rule directly and upgrades are failing. What practice is safer.
Incorrect Answers
A:Cloud Sync chooses the stable anchor based on documented directory attributes. This matters here because a team edited a built-in synchronization rule directly and upgrades are failing. What practice is safer.
B:Filters can remove valid source identities even in cases where the synchronization service is healthy.
C:Correct object matching prevents creating a second cloud user for one employee. This matters here because a team edited a built-in synchronization rule directly and upgrades are failing. What practice is safer.
Question 142
A sync engine runs but users do not appear because the domain is filtered out. What should be evaluated?
- Configure Seamless Single Sign-On with supported hybrid prerequisites.
- Investigate export errors and fix the source attributes or sync rules.
- Check selected directories, OU filtering and object inclusion conditions.
- Inspect Entra Connect Sync connector synchronization status and logs.
Explanation
Correct Answer
C:Filters can remove valid source identities even when the synchronization service is healthy. This matters here because a sync engine runs but users do not appear because the domain is filtered out.
Incorrect Answers
A:Seamless SSO enables integrated Windows authentication for eligible environments.
B:Repeat exports cannot repair contradictory or unsupported source directory values. This matters here because a sync engine runs but users do not appear because the domain is filtered out.
D:Connect Sync is responsible for the configured on-premises AD object export into Entra. Filters can remove valid source identities even when the synchronization service is healthy.
Question 143
A company is onboarding a disconnected AD forest with Microsoft Entra Cloud Sync and wants to avoid duplicate cloud users. Which TWO planning requirements matter? (Select TWO.)
- Ensure users are uniquely identifiable across forests before configuring provisioning.
- Allow two independent jobs to create new cloud users without identity matching.
- Choose a documented supported Cloud Sync topology for the disconnected forest.
- Force an arbitrary unsupported sourceAnchor attribute for every user.
- Assume the same user in separate forests is always merged automatically.
Explanation
Correct Answers
A:Cloud Sync does not automatically match duplicate identities across multiple source forests.
C:The source forest and tenant architecture must match Cloud Sync’s supported configurations.
Incorrect Answers
B:Uncoordinated creation increases duplicate principal risk.
D:Cloud Sync chooses its supported source anchor and does not provide free-form anchor selection.
E:Cross-forest matching is not automatically performed by Cloud Sync.
Question 144
A merger brings a disconnected AD forest into one Entra tenant. What topology capability supports it?
- Correlate Entra sign-in evidence with Connect Health and local agent logs.
- Check agent health, local connectivity and provisioning audit logs.
- Choose the synchronization engine based on supported object-count limits and topology.
- Assess Cloud Sync's documented disconnected-forest support.
Explanation
Correct Answer
D:Cloud Sync has supported scenarios for disconnected forests where full Connect Sync topology may differ.
Incorrect Answers
A:Cloud and on-premises telemetry jointly identify whether failures occur at federation, agent or synchronization stages. Cloud Sync has supported scenarios for disconnected forests where full Connect Sync topology may differ.
B:Agent status and credential/connectivity failures can interrupt cloud-managed sync.
C:Microsoft's supported comparison can favor Connect Sync for very large domains. This alternative addresses a large forest contains more than 250,000 objects. What product-selection constraint matters? It does not meet the specified case, which requires assess cloud sync's documented disconnected-forest support: Cloud Sync has supported scenarios for disconnected forests where full Connect Sync topology may differ.
Question 145
A large forest contains more than 250,000 objects. What product-selection constraint matters?
- Use the automatically selected Cloud Sync source anchor rather than force an arbitrary attribute.
- Choose a documented supported topology or redesign before implementation.
- Use Connect Health to investigate but fix sync rules or source data separately.
- Choose the synchronization engine based on supported object-count limits and topology.
Explanation
Correct Answer
D:Microsoft's supported comparison can favor Connect Sync for very large domains.
Incorrect Answers
A:Cloud Sync chooses the stable anchor based on documented directory attributes. This matters here because a large forest contains more than 250,000 objects. What product-selection constraint matters.
B:Unsupported Cloud Sync configurations can create inconsistent directory state without vendor support. This matters here because a large forest contains more than 250,000 objects. What product-selection constraint matters.
C:Monitoring identifies problems but is not a replacement for directory remediation.
Question 146
The same user exists in two forests with overlapping identities. What Cloud Sync limitation should be considered?
- Follow Microsoft's documented mixed Connect Sync and Cloud Sync topology support.
- Microsoft Entra Cloud Sync using supported provisioning agents.
- Do not assume cross-forest object matching is performed automatically by Cloud Sync.
- Validate password hash sync and the object's scoped provisioning inclusion.
Explanation
Correct Answer
C:Cloud Sync requires unique identities across forests and does not itself match duplicates across forests.
Incorrect Answers
A:Both engines can coexist only under supported partitioning and sync configurations. Cloud Sync requires unique identities across forests and does not itself match duplicates across forests.
B:Cloud Sync uses cloud-managed provisioning with lightweight local agents.
D:Identity object synchronization and password hash availability are related but separable checks. Cloud Sync requires unique identities across forests and does not itself match duplicates across forests.
Question 147
An administrator wants to choose a custom Cloud Sync sourceAnchor column. What limitation applies?
- Use the automatically selected Cloud Sync source anchor rather than force an arbitrary attribute.
- Choose a documented supported topology or redesign before implementation.
- Follow Microsoft's documented mixed Connect Sync and Cloud Sync topology support.
- Enable PHS as an additional supported backup authentication method.
Explanation
Correct Answer
A:Cloud Sync chooses the stable anchor based on documented directory attributes. This matters here because an administrator wants to choose a custom Cloud Sync sourceAnchor column. What limitation applies.
Incorrect Answers
B:Unsupported Cloud Sync configurations can create inconsistent directory state without vendor support. This matters here because an administrator wants to choose a custom Cloud Sync sourceAnchor column. What limitation applies.
C:Both engines can coexist only under supported partitioning and sync configurations. This matters here because an administrator wants to choose a custom Cloud Sync sourceAnchor column. What limitation applies.
D:PHS can provide fallback cloud password validation in hybrid sign-in designs.
Question 148
An organization combines an existing Connect Sync forest with a new Cloud Sync forest. What deployment rule matters?
- Check supported Connect Sync topology for large directory or resource-forest scenarios.
- Follow Microsoft's documented mixed Connect Sync and Cloud Sync topology support.
- Enable and test PHS for a scoped staged migration before switching domain sign-in.
- Check agent health, local connectivity and provisioning audit logs.
Explanation
Correct Answer
B:Both engines can coexist only under supported partitioning and sync configurations. This matters here because an organization combines an existing Connect Sync forest with a new Cloud Sync forest. What deployment rule matters.
Incorrect Answers
A:Cloud Sync does not support every configuration that full Connect Sync does. This matters here because an organization combines an existing Connect Sync forest with a new Cloud Sync forest. What deployment rule matters.
C:A tested cloud-authentication path reduces reliance on the federated IdP during cutover. This alternative addresses a company plans to replace federation with cloud authentication. Which preparation reduces disruption? It does not meet the specified case, which requires follow microsoft's documented mixed connect sync and cloud sync topology support: Both engines can coexist only under supported partitioning and sync configurations.
D:Agent status and credential/connectivity failures can interrupt cloud-managed sync. This matters here because an organization combines an existing Connect Sync forest with a new Cloud Sync forest. What deployment rule matters.
Question 149
A Cloud Sync provisioning agent suddenly stops processing after a service-account change. What should be inspected?
- Check agent health, local connectivity and provisioning audit logs.
- Enable password hash synchronization for cloud-side authentication.
- Assess Cloud Sync's documented disconnected-forest support.
- Microsoft Entra Cloud Sync using supported provisioning agents.
Explanation
Correct Answer
A:Agent status and credential/connectivity failures can interrupt cloud-managed sync. This matters here because a Cloud Sync provisioning agent suddenly stops processing after a service-account change.
Incorrect Answers
B:PHS allows cloud sign-in using synchronized password hashes without a live AD domain-controller validation per sign-in. Agent status and credential/connectivity failures can interrupt cloud-managed sync.
C:Cloud Sync has supported scenarios for disconnected forests where full Connect Sync topology may differ. This matters here because a Cloud Sync provisioning agent suddenly stops processing after a service-account change.
D:Cloud Sync uses cloud-managed provisioning with lightweight local agents. This matters here because a Cloud Sync provisioning agent suddenly stops processing after a service-account change.
Question 150
A startup wants an identity sync method for a topology not listed as supported. What decision is safest?
- Choose the synchronization engine based on supported object-count limits and topology.
- Choose a documented supported topology or redesign before implementation.
- Assess Cloud Sync's documented disconnected-forest support.
- Monitor sign-in logs for legacy federation dependence and migration failures.
Explanation
Correct Answer
B:Unsupported Cloud Sync configurations can create inconsistent directory state without vendor support. This matters here because a startup wants an identity sync method for a topology not listed as supported. What decision is safest.
Incorrect Answers
A:Microsoft's supported comparison can favor Connect Sync for very large domains. This matters here because a startup wants an identity sync method for a topology not listed as supported. What decision is safest.
C:Cloud Sync has supported scenarios for disconnected forests where full Connect Sync topology may differ. Unsupported Cloud Sync configurations can create inconsistent directory state without vendor support.
D:Sign-in telemetry shows which client flows still require legacy mechanisms. This matters here because a startup wants an identity sync method for a topology not listed as supported. What decision is safest.