Microsoft SC-300 Practice Test 13
Question 120
A security lead assumes Microsoft Entra B2B direct connect is enabled by default for all tenants. What must be clarified?
- Reset or resend the invitation using a supported redemption update.
- B2B direct connect starts denied and requires explicit mutual configuration.
- Allow scoped inbound B2B collaboration while blocking the corresponding outbound access.
- Align inbound user and application targeting so both permit the intended flow.
Explanation
Correct Answer
B:Direct-connect authorization is not inferred from default B2B collaboration behavior. This matters here because a security lead assumes Microsoft Entra B2B direct connect is enabled by default for all tenants.
Incorrect Answers
A:Guest redemption and email changes must be reconciled rather than creating uncontrolled duplicate identities. This matters here because a security lead assumes Microsoft Entra B2B direct connect is enabled by default for all tenants.
C:Inbound and outbound cross-tenant settings govern opposite access directions. This matters here because a security lead assumes Microsoft Entra B2B direct connect is enabled by default for all tenants.
D:User/group and application conditions must be logically compatible. This matters here because a security lead assumes Microsoft Entra B2B direct connect is enabled by default for all tenants.
Question 121
A multi-tenant enterprise needs employees provisioned automatically as external users in a sister tenant. Which feature fits?
- Configure Microsoft Entra cross-tenant synchronization from source to target.
- Set the cross-tenant sync provisioning assignment scope to the approved users or groups.
- Configure an approved SAML/WS-Federation external identity provider.
- Review provisioning logs and deprovisioning mappings.
Explanation
Correct Answer
A:Cross-tenant synchronization provisions B2B collaboration identities under defined sync scope. This matters here because a multi-tenant enterprise needs employees provisioned automatically as external users in a sister tenant. Which….
Incorrect Answers
B:Scoping filters control which source identities become target identities. This matters here because a multi-tenant enterprise needs employees provisioned automatically as external users in a sister tenant. Which….
C:External federation can validate the partner's existing IdP assertions for guest sign-in. This matters here because a multi-tenant enterprise needs employees provisioned automatically as external users in a sister tenant. Which….
D:Cross-tenant lifecycle depends on provisioning rules and target account state.
Question 122
Cross-tenant sync is configured in the source but creates no users in the target. Which target-tenant permission matters?
- Enable cross-tenant synchronization only for approved source organizations.
- Align issuer metadata and federation configuration with the trusted provider.
- Enable inbound user synchronization for that source organization.
- Inspect cross-tenant attribute mappings for the target field.
Explanation
Correct Answer
C:The target tenant must permit the source to provision its users.
Incorrect Answers
A:Organization-specific inbound sync permissions limit who can provision accounts into the tenant.
B:SAML token validation depends on issuer and trust metadata consistency. This matters here because cross-tenant sync is configured in the source but creates no users in the target. Which target-tenant permission matters.
D:Only mapped and permitted attributes propagate through the provisioning connection. This alternative addresses a new user's department is missing in the target tenant. What provisioning setting needs review? It does not meet the specified case, which requires enable inbound user synchronization for that source organization: The target tenant must permit the source to provision its users.
Question 123
An owner says cross-tenant sync settings are bidirectional by default. What direction should be configured?
- Have the invited user redeem the invitation through its supported identity provider.
- Align inbound user and application targeting so both permit the intended flow.
- Configure Microsoft Entra cross-tenant synchronization from source to target.
- Create separate source-to-target provisioning configurations for each desired direction.
Explanation
Correct Answer
D:Cross-tenant synchronization is directional; reverse synchronization is not implicit.
Incorrect Answers
A:Sending an invitation does not itself complete the guest's redemption state. This matters here because an owner says cross-tenant sync settings are bidirectional by default. What direction should be configured.
B:User/group and application conditions must be logically compatible. This matters here because an owner says cross-tenant sync settings are bidirectional by default. What direction should be configured.
C:Cross-tenant synchronization provisions B2B collaboration identities under defined sync scope. This matters here because an owner says cross-tenant sync settings are bidirectional by default. What direction should be configured.
Question 124
A new user's department is missing in the target tenant. What provisioning setting needs review?
- Enable inbound user synchronization for that source organization.
- Inspect cross-tenant attribute mappings for the target field.
- Create separate source-to-target provisioning configurations for each desired direction.
- Configure an external collaboration allowlist of supported domains.
Explanation
Correct Answer
B:Only mapped and permitted attributes propagate through the provisioning connection.
Incorrect Answers
A:The target tenant must permit the source to provision its users. This matters here because a new user's department is missing in the target tenant. What provisioning setting needs review.
C:Cross-tenant synchronization is directional; reverse synchronization is not implicit. This matters here because a new user's department is missing in the target tenant. What provisioning setting needs review.
D:Allowlisting narrows invited domains to an approved set. This matters here because a new user's department is missing in the target tenant. What provisioning setting needs review.
Question 125
An operator needs to sync only a security group of merger employees. Which source scope applies?
- Create separate source-to-target provisioning configurations for each desired direction.
- Set the cross-tenant sync provisioning assignment scope to the approved users or groups.
- Configure an external collaboration blocklist of the specified domains.
- Inspect cross-tenant attribute mappings for the target field.
Explanation
Correct Answer
B:Scoping filters control which source identities become target identities. This matters here because an operator needs to sync only a security group of merger employees. Which source scope applies.
Incorrect Answers
A:Cross-tenant synchronization is directional; reverse synchronization is not implicit. This matters here because an operator needs to sync only a security group of merger employees. Which source scope applies.
C:Domain restrictions filter invitations to prohibited email suffixes. This matters here because an operator needs to sync only a security group of merger employees. Which source scope applies.
D:Only mapped and permitted attributes propagate through the provisioning connection. This matters here because an operator needs to sync only a security group of merger employees. Which source scope applies.
Question 126
A partner tenant must accept synchronized users without manual invitation redemption each time. What should be reviewed?
- Inspect cross-tenant attribute mappings for the target field.
- Configure automatic redemption settings for permitted cross-tenant synchronization.
- Review external identity provider redemption order and allowed fallback methods.
- Configure inbound device-claim trust for the approved external organization.
Explanation
Correct Answer
B:Automatic redemption streamlines B2B onboarding when supported and explicitly allowed.
Incorrect Answers
A:Only mapped and permitted attributes propagate through the provisioning connection. This matters here because a partner tenant must accept synchronized users without manual invitation redemption each time.
C:Invitation redemption behavior depends on supported identity providers and configured policy. This matters here because a partner tenant must accept synchronized users without manual invitation redemption each time.
D:Cross-tenant trust may accept compliant or hybrid joined device claims from verified partners. This matters here because a partner tenant must accept synchronized users without manual invitation redemption each time.
Question 127
Cross-tenant sync pauses after an account is disabled in the source tenant. What evidence should be inspected?
- Review provisioning logs and deprovisioning mappings.
- Review the partner-specific inbound cross-tenant access policy.
- Configure automatic redemption settings for permitted cross-tenant synchronization.
- Align inbound user and application targeting so both permit the intended flow.
Explanation
Correct Answer
A:Cross-tenant lifecycle depends on provisioning rules and target account state. This matters here because cross-tenant sync pauses after an account is disabled in the source tenant. What evidence should be inspected.
Incorrect Answers
B:Collaboration allowlists and cross-tenant authorization are independent checks. This matters here because cross-tenant sync pauses after an account is disabled in the source tenant. What evidence should be inspected.
C:Automatic redemption streamlines B2B onboarding when supported and explicitly allowed. This matters here because cross-tenant sync pauses after an account is disabled in the source tenant. What evidence should be inspected.
D:User/group and application conditions must be logically compatible. This matters here because cross-tenant sync pauses after an account is disabled in the source tenant. What evidence should be inspected.
Question 128
A target tenant must not permit synchronization from every outside organization. What control should be set?
- Review B2B identity redemption order and email one-time passcode fallback.
- Inspect cross-tenant attribute mappings for the target field.
- Enable cross-tenant synchronization only for approved source organizations.
- Revoke the guest's resource assignments and coordinate identity lifecycle with the partner.
Explanation
Correct Answer
C:Organization-particular inbound sync permissions limit who can provision accounts into the tenant.
Incorrect Answers
A:Fallback redemption behavior is controlled by the external identity provider settings. This matters here because a target tenant must not permit synchronization from every outside organization. What control should be set.
B:Only mapped and permitted attributes propagate through the provisioning connection. This matters here because a target tenant must not permit synchronization from every outside organization. What control should be set.
D:An external home-tenant change does not guarantee all resource-tenant assignments were removed. This matters here because a target tenant must not permit synchronization from every outside organization. What control should be set.
Question 129
An enterprise wants guests to authenticate through a partner's SAML identity provider. What external identity integration fits?
- Review B2B identity redemption order and email one-time passcode fallback.
- Configure an approved SAML/WS-Federation external identity provider.
- Review provisioning logs and deprovisioning mappings.
- Update trusted federation signing metadata or certificate.
Explanation
Correct Answer
B:External federation can validate the partner's existing IdP assertions for guest sign-in. This matters here because an enterprise wants guests to authenticate through a partner's SAML identity provider. What external identity….
Incorrect Answers
A:Fallback redemption behavior is controlled by the external identity provider settings. This matters here because an enterprise wants guests to authenticate through a partner's SAML identity provider. What external identity….
C:Cross-tenant lifecycle depends on provisioning rules and target account state. This matters here because an enterprise wants guests to authenticate through a partner's SAML identity provider. What external identity….
D:Signature verification fails when the resource tenant trusts obsolete signing keys.
Question 130
A partner federation fails because the assertion issuer does not match the configured IdP. What must be corrected?
- Configure an approved SAML/WS-Federation external identity provider.
- Use the appropriate external identity provider federation rather than creating privileged workforce users.
- Remove application access and guest identity according to the offboarding policy.
- Align issuer metadata and federation configuration with the trusted provider.
Explanation
Correct Answer
D:SAML token validation depends on issuer and trust metadata consistency. This matters here because a partner federation fails because the assertion issuer does not match the configured IdP.
Incorrect Answers
A:External federation can validate the partner's existing IdP assertions for guest sign-in. This matters here because a partner federation fails because the assertion issuer does not match the configured IdP.
B:External federation establishes authentication without conferring tenant administrative roles. This matters here because a partner federation fails because the assertion issuer does not match the configured IdP.
C:External account lifecycle needs explicit end-of-contract termination. This matters here because a partner federation fails because the assertion issuer does not match the configured IdP.