Question 272 of 1,411
Describe the capabilities of Microsoft EntramediumMultiple ChoiceObjective-mapped

SC-900 Describe the capabilities of Microsoft Entra Practice Question

This SC-900 practice question tests your understanding of describe the capabilities of microsoft entra. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. A key principle to apply: sign-in frequency defines how often users must re-authenticate.. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

A company uses Microsoft Entra ID. They want to require users to perform multifactor authentication (MFA) every 30 days on devices that are marked as compliant, but require MFA for every sign-in attempt on non-compliant devices. Which Conditional Access control should they configure to meet this requirement?

Question 1mediummultiple choice
Full question →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Session control: Sign-in frequency

The requirement specifies different MFA frequency based on device compliance: every 30 days for compliant devices and every sign-in for non-compliant devices. This is achieved by configuring a Session control called 'Sign-in frequency' in a Conditional Access policy, which allows administrators to set the reauthentication interval (e.g., 30 days) and can be scoped to specific conditions like device state (compliant vs. non-compliant). Grant controls like 'Require MFA' enforce MFA but do not control the frequency of re-prompting.

Key principle: Sign-in frequency defines how often users must re-authenticate.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Grant control: Require MFA

    Why it's wrong here

    The 'Require MFA' grant control forces MFA for every sign-in that matches the policy conditions. It does not allow periodic re-authentication; it always requires MFA.

  • Session control: Sign-in frequency

    Why this is correct

    Sign-in frequency session control allows the administrator to specify how often a user must re-authenticate. This can be set to every 30 days for compliant devices and to 0 (every time) for non-compliant devices to achieve the goal.

    Related concept

    Sign-in frequency defines how often users must re-authenticate.

  • Conditions: Device state

    Why it's wrong here

    The device state condition is used to include or exclude devices based on compliance status, but it does not control the frequency of authentication. It identifies which devices the policy applies to.

  • Session control: Application restrictions

    Why it's wrong here

    Application restrictions session control is used to enforce application-level policies, such as blocking downloads or limiting access to certain apps. It does not affect authentication frequency.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates confuse 'Grant controls' (which enforce MFA) with 'Session controls' (which manage sign-in frequency), leading them to pick 'Require MFA' instead of 'Sign-in frequency' when the question specifically asks about controlling the frequency of MFA prompts.

Detailed technical explanation

How to think about this question

Under the hood, the 'Sign-in frequency' session control uses the 'Keep me signed in' (KMSI) token lifetime and the 'Session Token Lifetime' policy to enforce reauthentication. When set to 30 days for compliant devices, the session token is valid for 30 days, but for non-compliant devices, a separate policy with 'Sign-in frequency' set to 'Every time' forces token reissuance on each sign-in. This leverages the 'device compliance' condition, which checks the device's compliance status via Microsoft Intune or MDM, and the session control overrides the default token lifetime.

KKey Concepts to Remember

  • Sign-in frequency defines how often users must re-authenticate.
  • It can be configured in days, hours, or 'every time'.
  • Sign-in frequency works in conjunction with grant controls like 'Require MFA'.
  • It helps balance security and user experience by allowing periodic re-authentication.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Sign-in frequency defines how often users must re-authenticate.

Real-world example

How this comes up in practice

A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.

What to study next

Got this wrong? Here's your next step.

Review sign-in frequency defines how often users must re-authenticate., then practise related SC-900 questions on the same topic to reinforce the concept.

Related practice questions

Related SC-900 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free SC-900 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this SC-900 question test?

Describe the capabilities of Microsoft Entra — This question tests Describe the capabilities of Microsoft Entra — Sign-in frequency defines how often users must re-authenticate..

What is the correct answer to this question?

The correct answer is: Session control: Sign-in frequency — The requirement specifies different MFA frequency based on device compliance: every 30 days for compliant devices and every sign-in for non-compliant devices. This is achieved by configuring a Session control called 'Sign-in frequency' in a Conditional Access policy, which allows administrators to set the reauthentication interval (e.g., 30 days) and can be scoped to specific conditions like device state (compliant vs. non-compliant). Grant controls like 'Require MFA' enforce MFA but do not control the frequency of re-prompting.

What should I do if I get this SC-900 question wrong?

Review sign-in frequency defines how often users must re-authenticate., then practise related SC-900 questions on the same topic to reinforce the concept.

What is the key concept behind this question?

Sign-in frequency defines how often users must re-authenticate.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 11, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This SC-900 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SC-900 exam.