You save $69.98
SC-300 Premium Bundle
- Premium File 490 Questions & Answers
- Last Update: Nov 2, 2026
- Training Course 43 Lectures
- Study Guide 599 Pages
You save $69.98
The security review requires two independent corrections. Requirement A: An external partner has already satisfied MFA at its home tenant and is repeatedly prompted to redo MFA in the resource tenant. Requirement B: A small enterprise wants to synchronize on-premises AD DS users to Entra ID with a configurable synchronization engine and health monitoring. Which complete two-part plan meets both?
Step 1: Cross-tenant trust can accept supported MFA or device claims from another Microsoft Entra organization when configured. Step 2: Connect Sync synchronizes selected on-premises identities while retaining supported hybrid directory source authority. Both verification checks are required: A test partner completes the trusted home-tenant MFA and satisfies the resource access requirement without an unnecessary second registration; and A sampled on-premises user appears in Entra ID with correct linked identity attributes and sync errors are monitored.
Cross-tenant trust can accept supported MFA or device claims from another Microsoft Entra organization when configured. Connect Sync synchronizes selected on-premises identities while retaining supported hybrid directory source authority. The proposed steps (Configure the Microsoft Entra group creation settings and verify the delegated role exceptions before changing group owners; restrict users allowed to join devices in the Microsoft Entra device settings and validate registration versus join controls separately) address other capabilities instead of this required pair.
Connect Sync synchronizes selected on-premises identities while retaining supported hybrid directory source authority. The other proposed action (Configure the Microsoft Entra group creation settings and verify the delegated role exceptions before changing group owners) does not implement the first control. Cross-tenant trust can accept supported MFA or device claims from another Microsoft Entra organization when configured.
Cross-tenant trust can accept supported MFA or device claims from another Microsoft Entra organization when configured. The other proposed action (restrict users allowed to join devices in the Microsoft Entra device settings and validate registration versus join controls separately) addresses a different operation. Connect Sync synchronizes selected on-premises identities while retaining supported hybrid directory source authority.
A Microsoft Entra rollout has two issues: first, A business wants employee users to create security groups only through a centrally approved process; second, A contractor using a federation identity provider must sign into supported External ID collaboration flows that use SAML or WS-Federation. Which paired implementation meets both acceptance criteria?
Step 1: Tenant group settings govern self-service creation capabilities independently of whether users can be members of existing groups. Step 2: External federation configuration tells the resource tenant which external assertions may represent the invited identity. Both verification checks are required: An ordinary employee cannot create the restricted group type while an authorized administrator can; and A permitted federated contractor completes the expected sign-in flow without creating an internal employee password.
External federation configuration tells the resource tenant which external assertions may represent the invited identity. The other proposed action (Create a supported dynamic membership security group with a validated rule matching employeeType) does not implement the first control. Tenant group settings govern self-service creation capabilities independently of whether users can be members of existing groups.
Tenant group settings govern self-service creation capabilities independently of whether users can be members of existing groups. The other proposed action (update the cloud UPN through supported identity management and validate application mappings that use it) addresses a different operation. External federation configuration tells the resource tenant which external assertions may represent the invited identity.
Tenant group settings govern self-service creation capabilities independently of whether users can be members of existing groups. External federation configuration tells the resource tenant which external assertions may represent the invited identity. The proposed steps (Create a supported dynamic membership security group with a validated rule matching employeeType; update the cloud UPN through supported identity management and validate application mappings that use it) address other capabilities instead of this required pair.
A security engineer has this implementation task: A Conditional Access risk policy is broad enough to affect an emergency account during an incident. Select the best technical action, with this acceptance test: Emergency access remains available under documented containment conditions and standard users remain protected.
Emergency access planning must account for risk-triggered CA and access-block policies to preserve recovery capability. Review risk policy exclusions and provide controlled emergency access coverage under the organization's recovery design. The acceptance check is: Emergency access remains available under documented containment conditions and standard users remain protected.
A policy template supplies a starting configuration, not a validated tenant-specific scope. In the present case, however, the missing capability is: Review risk policy exclusions and provide controlled emergency access coverage under the organization's recovery design.
Identity Protection distinguishes accumulated user compromise risk from individual sign-in risk signals. It does not resolve A Conditional Access risk policy is broad enough to affect an emergency account during an incident.
User risk represents potential compromise of the identity over time, distinct from risk of an individual sign-in. This does not address the actual issue: A Conditional Access risk policy is broad enough to affect an emergency account during an incident.
The organization must fix both requirements before signoff: (1) An administrator assigns the Directory Readers Microsoft Entra role and expects it to grant an app Blob Data Contributor permissions on an Azure storage account; and (2) An approved SaaS service must be monitored for file activity using its native API instead of relying solely on web session proxy traffic. Select the combined implementation.
Step 1: Directory roles and Azure resource RBAC control different permission planes. Step 2: Connected app APIs provide supported activity and content visibility that differs from proxy-based session control. Both verification checks are required: The app can perform the intended storage operation without receiving unrelated tenant directory privileges; and A known file event from the connected app appears in the monitored activity stream.
Both actions target other requirements: A suspicious third-party OAuth app requests broad delegated access to user data and users are approving it without central review; A SaaS integration requires OIDC sign-in and administrators attempt to configure it solely with SAML metadata. Neither completes the stated two-step design.
The plan is partly correct, but Use the provider's supported OpenID Connect integration settings and validate the client configuration is not the missing control. Instead, use: Configure a supported Defender for Cloud Apps connected app or API connector with the required grants.
Connected app APIs provide supported activity and content visibility that differs from proxy-based session control. The other proposed action (Investigate OAuth app permissions and apply appropriate OAuth app governance or policy controls) does not implement the first control. Directory roles and Azure resource RBAC control different permission planes.
The security review requires two independent corrections. Requirement A: Security staff want to increase strong authenticator enrollment without permanently blocking unregistered users from all unrelated apps. Requirement B: Contractor browser sessions must require reauthentication after a defined interval while other policies remain unchanged. Which complete two-part plan meets both?
Step 1: Registration campaigns nudge eligible users to register supported methods while full access enforcement is a separate policy decision. Step 2: Sign-in frequency governs reauthentication behavior and is different from controlling how a password is initially created. Both verification checks are required: Campaign reporting shows users registering the intended method and exempt users are treated as configured; and The test contractor is prompted to reauthenticate after the configured interval without changing unrelated user accounts.
Sign-in frequency governs reauthentication behavior and is different from controlling how a password is initially created. The other proposed action (Use appropriate device filters and Conditional Access conditions validated against registration and compliance properties) does not implement the first control. Registration campaigns nudge eligible users to register supported methods while full access enforcement is a separate policy decision.
Registration campaigns nudge eligible users to register supported methods while full access enforcement is a separate policy decision. Sign-in frequency governs reauthentication behavior and is different from controlling how a password is initially created. The proposed steps (Use appropriate device filters and Conditional Access conditions validated against registration and compliance properties; deploy the supported Global Secure Access client to the targeted managed endpoint population and validate connectivity) address other capabilities instead of this required pair.
Registration campaigns nudge eligible users to register supported methods while full access enforcement is a separate policy decision. The other proposed action (deploy the supported Global Secure Access client to the targeted managed endpoint population and validate connectivity) addresses a different operation. Sign-in frequency governs reauthentication behavior and is different from controlling how a password is initially created.
In the identity platform, the requested outcome is: A guest redeems the invitation and reads the approved resource without acquiring employee-wide access. The current problem is: Partners require access to a shared team site, and administrators intend to create native member accounts for all visitors. What implementation meets the requirement?
B2B collaboration represents external identities in the resource tenant without routinely provisioning them as permanent internal employee accounts. Invite the partners as Microsoft Entra B2B collaboration guests and grant only the required resource access. The acceptance check is: A guest redeems the invitation and reads the approved resource without acquiring employee-wide access.
Microsoft Entra audit events capture relevant administrative unit role and membership changes, unlike sign-in records that only show authentication. This does not address the actual issue: Partners require access to a shared team site, and administrators intend to create native member accounts for all visitors.
External collaboration settings control who may invite B2B users independently of each application's sharing grants. In the present case, however, the missing capability is: Invite the partners as Microsoft Entra B2B collaboration guests and grant only the required resource access.
Outbound cross-tenant access governs a user's ability to collaborate with another organization's resources, not inbound guests. It does not resolve Partners require access to a shared team site, and administrators intend to create native member accounts for all visitors.
A Microsoft Entra administrator needs to fix this condition: A new employee has no existing strong authentication method and must enroll a phishing-resistant passkey without receiving a long-lived temporary password. Which change is most appropriate if success is measured by: The employee uses the valid pass to register a passkey and cannot reuse an expired or revoked pass?
TAP bootstraps passwordless authentication method registration and can be limited to a short validity or one-time use. Enable and issue a scoped time-limited Temporary Access Pass and let the employee enroll the approved passkey. The acceptance check is: The employee uses the valid pass to register a passkey and cannot reuse an expired or revoked pass.
Number matching requires the user to enter the sign-in challenge rather than approving an unrelated push blindly. In the present case, however, the missing capability is: Enable and issue a scoped time-limited Temporary Access Pass and let the employee enroll the approved passkey.
Removing an individual registered authentication method invalidates that credential without deleting every other approved method. It does not resolve A new employee has no existing strong authentication method and must enroll a phishing-resistant passkey without receiving a long-lived temporary password.
Risk-based MFA requires users to have a usable method or bootstrap path, not just a risk threshold. It is useful when: A high-risk sign-in policy demands MFA, but a subset of users have no registered supported authentication method. This question instead calls for: Enable and issue a scoped time-limited Temporary Access Pass and let the employee enroll the approved passkey.
An enterprise requires a narrowly scoped remediation: A public web client receives an invalid redirect URI error after the app team changed its production hostname. What should the team implement to verify: The production login completes with the approved callback and a misspelled callback is rejected?
Microsoft identity platform redirects authorization responses only to registered valid callback URIs. Update and validate the app registration redirect URI for the supported client platform and exact callback URL. The acceptance check is: The production login completes with the approved callback and a misspelled callback is rejected.
Provisioning user objects in a SaaS app does not automatically bypass Microsoft Entra enterprise app assignment controls. It does not resolve A public web client receives an invalid redirect URI error after the app team changed its production hostname.
An app object defines the software registration while a service principal is its tenant-specific security instance. This does not address the actual issue: A public web client receives an invalid redirect URI error after the app team changed its production hostname.
Workload identity federation validates trusted token claims instead of requiring a stored application secret. In the present case, however, the missing capability is: Update and validate the app registration redirect URI for the supported client platform and exact callback URL.
An enterprise requires a narrowly scoped remediation: A compliance requirement calls for validating user passwords against the on-premises AD environment during Microsoft Entra sign-in. What should the team implement to verify: A sign-in is validated through the expected PTA agents and agent interruption is surfaced as a failure?
PTA validates the password through on-premises agents rather than using cloud password-hash validation as its primary sign-in path. Use pass-through authentication with properly deployed authentication agents and high availability. The acceptance check is: A sign-in is validated through the expected PTA agents and agent interruption is surfaced as a failure.
Changing the federated authentication path requires identity and app compatibility validation, not merely stopping AD FS servers. It is useful when: A legacy AD FS deployment must be migrated toward managed Microsoft Entra authentication while business apps continue to work. This question instead calls for: Use pass-through authentication with properly deployed authentication agents and high availability.
Cloud Sync uses provisioning agents and supports selected hybrid scenarios; it is not an exact replacement for every Connect Sync feature. This does not address the actual issue: A compliance requirement calls for validating user passwords against the on-premises AD environment during Microsoft Entra sign-in.
A user principal name change can affect downstream app identifiers even though the object ID remains stable. It does not resolve A compliance requirement calls for validating user passwords against the on-premises AD environment during Microsoft Entra sign-in.
A security engineer has this implementation task: B2B guests remain assigned to an application after a project ends and resource owners need a regular cleanup mechanism. Select the best technical action, with this acceptance test: The expired guest is included in review and denied access is removed after the configured apply step.
Periodic guest access reviews help identify external users whose ongoing access is no longer justified. Configure recurring access reviews targeting guest user access to the enterprise application or group. The acceptance check is: The expired guest is included in review and denied access is removed after the configured apply step.
Removing one reviewed entitlement may not revoke access granted independently through another resource assignment. This does not address the actual issue: B2B guests remain assigned to an application after a project ends and resource owners need a regular cleanup mechanism.
External identity lifecycle controls can remove or block unneeded guests when their last governed access ends. It does not resolve B2B guests remain assigned to an application after a project ends and resource owners need a regular cleanup mechanism.
A review decision and its enforcement can be separate steps, depending on review settings. It is useful when: Reviewers record Deny for some group members but administrators assume review completion immediately changed the actual group membership. This question instead calls for: Configure recurring access reviews targeting guest user access to the enterprise application or group.
In the identity platform, the requested outcome is: The query returns the expected per-application failure counts from controlled sample events. The current problem is: An administrator needs to count failed interactive logins by application from exported Microsoft Entra sign-in logs. What implementation meets the requirement?
Kusto Query Language can aggregate sign-in telemetry after it has been ingested in Log Analytics. Write a KQL query against the supported sign-in log table filtering failures and summarizing by application. The acceptance check is: The query returns the expected per-application failure counts from controlled sample events.
Entra diagnostic settings can stream selected logs to Event Hubs as an alternative to only querying the portal. It does not resolve An administrator needs to count failed interactive logins by application from exported Microsoft Entra sign-in logs.
Privileged role assignment governance differs from an ordinary app-membership review. It is useful when: A company must certify who retains privileged Microsoft Entra role assignments, not only application access. This question instead calls for: Write a KQL query against the supported sign-in log table filtering failures and summarizing by application.
Log Analytics queries cannot analyze events that were not streamed to that workspace. This does not address the actual issue: An administrator needs to count failed interactive logins by application from exported Microsoft Entra sign-in logs.
Please check your mailbox for a message from support@examlabs.com and follow the directions.