Practice Exams:

Microsoft SC-900 Dumps

EXAM: Microsoft Security, Compliance, and Identity Fundamentals
Verified By Experts
Premium Bundle
$40.00
$59.97 $99.97

SC-900 Premium Bundle


  • Premium File 259 Questions & Answers
  • Training Course 147 Lectures
  • Study Guide 413 Pages

Microsoft SC-900 Practice Test 37

Question 360

For this case—A security analyst trusts a personally owned laptop as corporate compliant merely because its owner can pass password and SMS authentication.—which implementation and acceptance check are correctly paired?

  1. Action: Target the specified Entra enterprise application and eligible users with a Conditional Access grant control requiring supported MFA. Validation: Sign in to the restricted app with a pilot account and prove an extra required factor appears while an unrelated application follows its configured controls.
  2. Action: Select a supported Conditional Access authentication strength that requires phishing-resistant methods for high-risk administration where appropriate. Validation: Test a privileged user with a registered security key and a less-resistant SMS method and verify only the policy-approved method satisfies the targeted access.
  3. Action: Enable supported Microsoft Authenticator push prompts with number matching and user context to make fraudulent approval attempts harder to accept. Validation: Trigger a controlled sign-in, check the matching number on the authentic request, and verify an unsolicited prompt is explicitly rejected.
  4. Action: Use Conditional Access to require a compliant or appropriately joined device where supported and ensure endpoint management evaluates that compliance independently. Validation: Test a managed compliant device and an unmanaged device against the same application policy, observing different allowed or blocked outcomes.

Explanation

Correct Answer

D:

The situation is that a security analyst trusts a personally owned laptop as corporate compliant merely because its owner can pass password and SMS authentication. Use Conditional Access to require a compliant or appropriately joined device where supported and ensure endpoint management evaluates that compliance independently. Validation: Test a managed compliant device and an unmanaged device against the same application policy, observing different allowed or blocked outcomes. The action and test belong together because conditional Access can consume device compliance results, but it does not replace defining device health rules through the relevant management service.

Incorrect Answers

A:

That action-and-evidence pair concerns “require MFA conditionally for a sensitive cloud application”, not this decision. The appropriate action is to use Conditional Access to require a compliant or appropriately joined device where supported and ensure endpoint management evaluates that compliance independently. To confirm, test a managed compliant device and an unmanaged device against the same application policy, observing different allowed or blocked outcomes.

B:

The proposed pair focuses on “use authentication strengths for phishing-resistant requirements” instead. The appropriate action is to use Conditional Access to require a compliant or appropriately joined device where supported and ensure endpoint management evaluates that compliance independently. To confirm, test a managed compliant device and an unmanaged device against the same application policy, observing different allowed or blocked outcomes.

C:

“use Microsoft authenticator notifications with secure number matching” evaluates a different intervention. The appropriate action is to use Conditional Access to require a compliant or appropriately joined device where supported and ensure endpoint management evaluates that compliance independently. To confirm, test a managed compliant device and an unmanaged device against the same application policy, observing different allowed or blocked outcomes.

Question 361

A banking administrator needs to operate a critical privileged portal and policy requires authentication resistant to phishing proxies. Which implementation or design choice most directly mitigates the stated issue?

  1. Select a supported Conditional Access authentication strength that requires phishing-resistant methods for high-risk administration where appropriate.
  2. Use Conditional Access to require a compliant or appropriately joined device where supported and ensure endpoint management evaluates that compliance independently.
  3. Grant Entra directory administration through Entra roles and Azure subscription or resource access through Azure RBAC, each within its intended management plane.
  4. Use Conditional Access for contextual sign-in decisions and Microsoft Entra PIM for time-bound eligibility and activation of supported privileged directory or Azure roles.

Explanation

Correct Answer

A:

Select a supported Conditional Access authentication strength that requires phishing-resistant methods for high-risk administration where appropriate. An authentication strength constrains which authentication methods satisfy the grant control, instead of treating every second factor as equally resistant to phishing. To verify, test a privileged user with a registered security key and a less-resistant SMS method and verify only the policy-approved method satisfies the targeted access.

Incorrect Answers

B:

“apply device compliance grant requirements correctly” is related to another task, not the failure shown here. An authentication strength constrains which authentication methods satisfy the grant control, instead of treating every second factor as equally resistant to phishing.

C:

This alternative focuses on “separate Microsoft entra directory roles from Azure resource RBAC” instead of the required outcome. An authentication strength constrains which authentication methods satisfy the grant control, instead of treating every second factor as equally resistant to phishing.

D:

That choice concerns “avoid confusing conditional access with privileged identity management”, not the immediate requirement. An authentication strength constrains which authentication methods satisfy the grant control, instead of treating every second factor as equally resistant to phishing.

Question 362

A banking administrator needs to operate a critical privileged portal and policy requires authentication resistant to phishing proxies. Which technical explanation most directly supports the right approach?

  1. A directory role such as User Administrator manages identity operations, while an Azure resource role controls data-plane or management-plane access to Azure resources.
  2. An authentication strength constrains which authentication methods satisfy the grant control, instead of treating every second factor as equally resistant to phishing.
  3. Conditional Access can consume device compliance results, but it does not replace defining device health rules through the relevant management service.
  4. An overly broad access policy can block all administrators, so testing matching sign-ins and maintaining emergency recovery access reduces lockout risk.

Explanation

Correct Answer

B:

An authentication strength constrains which authentication methods satisfy the grant control, instead of treating every second factor as equally resistant to phishing. This supports the decision to select a supported Conditional Access authentication strength that requires phishing-resistant methods for high-risk administration where appropriate.

Incorrect Answers

A:

The principle behind “separate Microsoft entra directory roles from Azure resource RBAC” is not the one being tested. Here, an authentication strength constrains which authentication methods satisfy the grant control, instead of treating every second factor as equally resistant to phishing.

C:

“apply device compliance grant requirements correctly” explains a different mechanism. Here, an authentication strength constrains which authentication methods satisfy the grant control, instead of treating every second factor as equally resistant to phishing.

D:

That statement concerns “validate conditional access rules in report-only mode before enforcement” rather than the cause in this case. Here, an authentication strength constrains which authentication methods satisfy the grant control, instead of treating every second factor as equally resistant to phishing.

Question 363

For this situation—A banking administrator needs to operate a critical privileged portal and policy requires authentication resistant to phishing proxies.—which check provides the strongest verification?

  1. Inspect report-only results for pilot users and service accounts, verify emergency access, then stage controlled enforcement after approval.
  2. Check method-policy eligibility for two synthetic groups, register an approved factor and verify an excluded group cannot enroll a restricted method.
  3. Test a privileged user with a registered security key and a less-resistant SMS method and verify only the policy-approved method satisfies the targeted access.
  4. Test a managed compliant device and an unmanaged device against the same application policy, observing different allowed or blocked outcomes.

Explanation

Correct Answer

C:

Test a privileged user with a registered security key and a less-resistant SMS method and verify only the policy-approved method satisfies the targeted access. It is the relevant test because an authentication strength constrains which authentication methods satisfy the grant control, instead of treating every second factor as equally resistant to phishing.

Incorrect Answers

A:

“validate conditional access rules in report-only mode before enforcement” would verify a different part of the system. To check this result, test a privileged user with a registered security key and a less-resistant SMS method and verify only the policy-approved method satisfies the targeted access.

B:

That test concerns “set authentication method policies for approved factors”, not the requested outcome. To check this result, test a privileged user with a registered security key and a less-resistant SMS method and verify only the policy-approved method satisfies the targeted access.

D:

This evidence addresses “apply device compliance grant requirements correctly” instead of confirming the repair. To check this result, test a privileged user with a registered security key and a less-resistant SMS method and verify only the policy-approved method satisfies the targeted access.

Question 364

A banking administrator needs to operate a critical privileged portal and policy requires authentication resistant to phishing proxies. If the team does the following—"Require any MFA without considering a phishing-resistant requirement and assume an SMS code meets a FIDO2-only access policy."—what could go wrong?

  1. The principal may gain excessive tenant authority while still lacking the resource-specific role required for the requested operation.
  2. Compromise of a support account can permit broad tenant configuration changes and difficult-to-audit privileged activity.
  3. A permanently privileged user may retain role membership continuously even though their sign-ins require an additional factor.
  4. Privileged accounts may remain vulnerable to real-time phishing when weak factors are accepted as equivalent to origin-bound credentials.

Explanation

Correct Answer

D:

Privileged accounts may remain vulnerable to real-time phishing when weak factors are accepted as equivalent to origin-bound credentials. The shortcut is unsafe because an authentication strength constrains which authentication methods satisfy the grant control, instead of treating every second factor as equally resistant to phishing.

Incorrect Answers

A:

That consequence concerns “The principal may gain excessive tenant authority while still lacking the resource-specific role required for the…”, which is a different failure. Here, privileged accounts may remain vulnerable to real-time phishing when weak factors are accepted as equivalent to origin-bound credentials.

B:

“Compromise of a support account can permit broad tenant configuration changes and difficult-to-audit privileged activity” does not describe the result of this shortcut. Here, privileged accounts may remain vulnerable to real-time phishing when weak factors are accepted as equivalent to origin-bound credentials.

C:

The alternative risk relates to “A permanently privileged user may retain role membership continuously even though their sign-ins require an additional…”, not the stated mistake. Here, privileged accounts may remain vulnerable to real-time phishing when weak factors are accepted as equivalent to origin-bound credentials.

Question 365

A banking administrator needs to operate a critical privileged portal and policy requires authentication resistant to phishing proxies. Which action and validation evidence belong together?

  1. Action: Select a supported Conditional Access authentication strength that requires phishing-resistant methods for high-risk administration where appropriate. Validation: Test a privileged user with a registered security key and a less-resistant SMS method and verify only the policy-approved method satisfies the targeted access.
  2. Action: Use Conditional Access for contextual sign-in decisions and Microsoft Entra PIM for time-bound eligibility and activation of supported privileged directory or Azure roles. Validation: Activate a test eligible administrative role through PIM, verify a bounded activation interval and separately inspect the matching Conditional Access decision.
  3. Action: Use Microsoft Entra Conditional Access to assess supported user, application, device, location and risk signals when deciding access requirements. Validation: Test the same app sign-in from a compliant device and an untrusted test context, verifying policy evaluation and resulting grant or block decisions.
  4. Action: Use Conditional Access to require a compliant or appropriately joined device where supported and ensure endpoint management evaluates that compliance independently. Validation: Test a managed compliant device and an unmanaged device against the same application policy, observing different allowed or blocked outcomes.

Explanation

Correct Answer

A:

Select a supported Conditional Access authentication strength that requires phishing-resistant methods for high-risk administration where appropriate. Validation: Test a privileged user with a registered security key and a less-resistant SMS method and verify only the policy-approved method satisfies the targeted access. The action and test belong together because an authentication strength constrains which authentication methods satisfy the grant control, instead of treating every second factor as equally resistant to phishing.

Incorrect Answers

B:

“avoid confusing conditional access with privileged identity management” evaluates a different intervention. The appropriate action is to select a supported Conditional Access authentication strength that requires phishing-resistant methods for high-risk administration where appropriate. To confirm, test a privileged user with a registered security key and a less-resistant SMS method and verify only the policy-approved method satisfies the targeted access.

C:

The linked action and check for “apply conditional access from evaluated identity signals” would not resolve this case. The appropriate action is to select a supported Conditional Access authentication strength that requires phishing-resistant methods for high-risk administration where appropriate. To confirm, test a privileged user with a registered security key and a less-resistant SMS method and verify only the policy-approved method satisfies the targeted access.

D:

That action-and-evidence pair concerns “apply device compliance grant requirements correctly”, not this decision. The appropriate action is to select a supported Conditional Access authentication strength that requires phishing-resistant methods for high-risk administration where appropriate. To confirm, test a privileged user with a registered security key and a less-resistant SMS method and verify only the policy-approved method satisfies the targeted access.

Question 366

An SC-900 learner considers: A developer configures an MFA requirement but forgets the administrator standard specifically excludes one-time SMS approval. What is the most appropriate next decision?

  1. Target the specified Entra enterprise application and eligible users with a Conditional Access grant control requiring supported MFA.
  2. Select a supported Conditional Access authentication strength that requires phishing-resistant methods for high-risk administration where appropriate.
  3. Grant Entra directory administration through Entra roles and Azure subscription or resource access through Azure RBAC, each within its intended management plane.
  4. Use Microsoft Entra Conditional Access to assess supported user, application, device, location and risk signals when deciding access requirements.

Explanation

Correct Answer

B:

The situation is that a developer configures an MFA requirement but forgets the administrator standard specifically excludes one-time SMS approval. Select a supported Conditional Access authentication strength that requires phishing-resistant methods for high-risk administration where appropriate. An authentication strength constrains which authentication methods satisfy the grant control, instead of treating every second factor as equally resistant to phishing. To verify, test a privileged user with a registered security key and a less-resistant SMS method and verify only the policy-approved method satisfies the targeted access.

Incorrect Answers

A:

“require MFA conditionally for a sensitive cloud application” is related to another task, not the failure shown here. An authentication strength constrains which authentication methods satisfy the grant control, instead of treating every second factor as equally resistant to phishing.

C:

That choice concerns “separate Microsoft entra directory roles from Azure resource RBAC”, not the immediate requirement. An authentication strength constrains which authentication methods satisfy the grant control, instead of treating every second factor as equally resistant to phishing.

D:

The proposed action addresses “apply conditional access from evaluated identity signals” rather than the problem described. An authentication strength constrains which authentication methods satisfy the grant control, instead of treating every second factor as equally resistant to phishing.

Question 367

A developer configures an MFA requirement but forgets the administrator standard specifically excludes one-time SMS approval. Why does the recommended approach address this particular concern?

  1. A directory role such as User Administrator manages identity operations, while an Azure resource role controls data-plane or management-plane access to Azure resources.
  2. Different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails.
  3. An authentication strength constrains which authentication methods satisfy the grant control, instead of treating every second factor as equally resistant to phishing.
  4. An overly broad access policy can block all administrators, so testing matching sign-ins and maintaining emergency recovery access reduces lockout risk.

Explanation

Correct Answer

C:

The situation is that a developer configures an MFA requirement but forgets the administrator standard specifically excludes one-time SMS approval. An authentication strength constrains which authentication methods satisfy the grant control, instead of treating every second factor as equally resistant to phishing. This supports the decision to select a supported Conditional Access authentication strength that requires phishing-resistant methods for high-risk administration where appropriate.

Incorrect Answers

A:

“separate Microsoft entra directory roles from Azure resource RBAC” describes another technical distinction. Here, an authentication strength constrains which authentication methods satisfy the grant control, instead of treating every second factor as equally resistant to phishing.

B:

“distinguish cloud-only and hybrid identity sign-in choices” explains a different mechanism. Here, an authentication strength constrains which authentication methods satisfy the grant control, instead of treating every second factor as equally resistant to phishing.

D:

The principle behind “validate conditional access rules in report-only mode before enforcement” is not the one being tested. Here, an authentication strength constrains which authentication methods satisfy the grant control, instead of treating every second factor as equally resistant to phishing.

Question 368

A developer configures an MFA requirement but forgets the administrator standard specifically excludes one-time SMS approval. Which evidence best validates the proposed outcome?

  1. Inspect report-only results for pilot users and service accounts, verify emergency access, then stage controlled enforcement after approval.
  2. Test the same app sign-in from a compliant device and an untrusted test context, verifying policy evaluation and resulting grant or block decisions.
  3. Use a test helpdesk identity to reset an eligible Entra account, then verify it cannot change an unrelated Azure storage account without Azure role assignment.
  4. Test a privileged user with a registered security key and a less-resistant SMS method and verify only the policy-approved method satisfies the targeted access.

Explanation

Correct Answer

D:

The situation is that a developer configures an MFA requirement but forgets the administrator standard specifically excludes one-time SMS approval. Test a privileged user with a registered security key and a less-resistant SMS method and verify only the policy-approved method satisfies the targeted access. It is the relevant test because an authentication strength constrains which authentication methods satisfy the grant control, instead of treating every second factor as equally resistant to phishing.

Incorrect Answers

A:

That test concerns “validate conditional access rules in report-only mode before enforcement”, not the requested outcome. To check this result, test a privileged user with a registered security key and a less-resistant SMS method and verify only the policy-approved method satisfies the targeted access.

B:

The proposed check is relevant to “apply conditional access from evaluated identity signals”, but not sufficient here. To check this result, test a privileged user with a registered security key and a less-resistant SMS method and verify only the policy-approved method satisfies the targeted access.

C:

This evidence addresses “separate Microsoft entra directory roles from Azure resource RBAC” instead of confirming the repair. To check this result, test a privileged user with a registered security key and a less-resistant SMS method and verify only the policy-approved method satisfies the targeted access.

Question 369

Consider this situation: A developer configures an MFA requirement but forgets the administrator standard specifically excludes one-time SMS approval. A team member suggests: "Require any MFA without considering a phishing-resistant requirement and assume an SMS code meets a FIDO2-only access policy." What is the main risk?

  1. Privileged accounts may remain vulnerable to real-time phishing when weak factors are accepted as equivalent to origin-bound credentials.
  2. A permanently privileged user may retain role membership continuously even though their sign-ins require an additional factor.
  3. Administrators and essential services may be locked out of the tenant when an unvalidated policy matches unexpected identities.
  4. An unmanaged or outdated endpoint may access regulated data because device health was never configured or required.

Explanation

Correct Answer

A:

The situation is that a developer configures an MFA requirement but forgets the administrator standard specifically excludes one-time SMS approval. Privileged accounts may remain vulnerable to real-time phishing when weak factors are accepted as equivalent to origin-bound credentials. The shortcut is unsafe because an authentication strength constrains which authentication methods satisfy the grant control, instead of treating every second factor as equally resistant to phishing.

Incorrect Answers

B:

The situation is that a developer configures an MFA requirement but forgets the administrator standard specifically excludes one-time SMS approval. The alternative risk relates to “A permanently privileged user may retain role membership continuously even though their sign-ins require an additional…”, not the stated mistake. Here, privileged accounts may remain vulnerable to real-time phishing when weak factors are accepted as equivalent to origin-bound credentials.

C:

“Administrators and essential services may be locked out of the tenant when an unvalidated policy matches…” can arise elsewhere, but it is not the most direct risk here. Here, privileged accounts may remain vulnerable to real-time phishing when weak factors are accepted as equivalent to origin-bound credentials.

D:

That consequence concerns “An unmanaged or outdated endpoint may access regulated data because device health was never configured or…”, which is a different failure. Here, privileged accounts may remain vulnerable to real-time phishing when weak factors are accepted as equivalent to origin-bound credentials.

Question 370

A security and compliance reviewer considers: A developer configures an MFA requirement but forgets the administrator standard specifically excludes one-time SMS approval. Which response and evidence should be linked?

  1. Action: Grant Entra directory administration through Entra roles and Azure subscription or resource access through Azure RBAC, each within its intended management plane. Validation: Use a test helpdesk identity to reset an eligible Entra account, then verify it cannot change an unrelated Azure storage account without Azure role assignment.
  2. Action: Select a supported Conditional Access authentication strength that requires phishing-resistant methods for high-risk administration where appropriate. Validation: Test a privileged user with a registered security key and a less-resistant SMS method and verify only the policy-approved method satisfies the targeted access.
  3. Action: Deploy a new broad Conditional Access policy to a limited pilot or report-only evaluation and analyze expected impacts and emergency-access exceptions. Validation: Inspect report-only results for pilot users and service accounts, verify emergency access, then stage controlled enforcement after approval.
  4. Action: Enable supported Microsoft Authenticator push prompts with number matching and user context to make fraudulent approval attempts harder to accept. Validation: Trigger a controlled sign-in, check the matching number on the authentic request, and verify an unsolicited prompt is explicitly rejected.

Explanation

Correct Answer

B:

The situation is that a developer configures an MFA requirement but forgets the administrator standard specifically excludes one-time SMS approval. Select a supported Conditional Access authentication strength that requires phishing-resistant methods for high-risk administration where appropriate. Validation: Test a privileged user with a registered security key and a less-resistant SMS method and verify only the policy-approved method satisfies the targeted access. The action and test belong together because an authentication strength constrains which authentication methods satisfy the grant control, instead of treating every second factor as equally resistant to phishing.

Incorrect Answers

A:

“separate Microsoft entra directory roles from Azure resource RBAC” evaluates a different intervention. The appropriate action is to select a supported Conditional Access authentication strength that requires phishing-resistant methods for high-risk administration where appropriate. To confirm, test a privileged user with a registered security key and a less-resistant SMS method and verify only the policy-approved method satisfies the targeted access.

C:

That action-and-evidence pair concerns “validate conditional access rules in report-only mode before enforcement”, not this decision. The appropriate action is to select a supported Conditional Access authentication strength that requires phishing-resistant methods for high-risk administration where appropriate. To confirm, test a privileged user with a registered security key and a less-resistant SMS method and verify only the policy-approved method satisfies the targeted access.

D:

The proposed pair focuses on “use Microsoft authenticator notifications with secure number matching” instead. The appropriate action is to select a supported Conditional Access authentication strength that requires phishing-resistant methods for high-risk administration where appropriate. To confirm, test a privileged user with a registered security key and a less-resistant SMS method and verify only the policy-approved method satisfies the targeted access.

Microsoft Security, Compliance, and Identity Fundamentals (SC-900) Practice Tests