Courseiva
Prepare infrastructure for deviceseasyMultiple ChoiceObjective-mapped

Windows Autopilot: Enable Windows Hello for Business During OOBE

You are planning a Windows Autopilot deployment for your organization. You need to ensure that during the out-of-box experience (OOBE), the user is prompted to set up Windows Hello for Business. What should you configure in the Autopilot profile?

Quick Answer

The answer is to set 'Enable Windows Hello for Business' in the Autopilot profile. This is correct because the Autopilot profile itself contains a dedicated Windows Hello for Business settings section, which directly controls whether the user is prompted to configure biometric or PIN authentication during the out-of-box experience (OOBE). On the MD-102 exam, this question tests your understanding that the Autopilot profile is the single configuration point for Hello enrollment, not the Enrollment Status Page or a separate policy. A common trap is assuming you need a separate Intune policy, but the profile’s built-in toggle is sufficient. Remember: the Autopilot profile is the “front door” for OOBE settings—if you want Hello to appear at setup, flip the switch inside that profile, not elsewhere. Memory tip: “Hello in the profile, not a separate file.”

⚠ Common exam trap

A common mix-up: candidates assume a separate Windows Hello for Business policy (Option B) is required to trigger the OOBE prompt, not realizing that the Autopilot profile itself has a dedicated toggle that directly controls this behavior during the initial setup flow.

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

Set 'Enable Windows Hello for Business' in the Autopilot profile.

The Windows Autopilot profile includes a setting called 'Enable Windows Hello for Business' that, when enabled, automatically configures the device to prompt the user to set up Windows Hello for Business during the out-of-box experience (OOBE). This setting is part of the Autopilot profile itself and does not require a separate policy or additional configuration to trigger the Hello setup prompt.

Answer analysis

Option-by-option breakdown

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

  • Ensure the device is Azure AD joined.

    Why it's wrong here

    Join is required but does not prompt Hello setup.

  • Create a separate Windows Hello for Business policy and assign it to the device group.

    Why it's wrong here

    Can be done within the Autopilot profile.

  • Configure the Enrollment Status Page to show Hello setup.

    Why it's wrong here

    ESP shows progress, not configuration.

  • Set 'Enable Windows Hello for Business' in the Autopilot profile.

    Why this is correct

    The profile includes a setting to enable Hello during OOBE.

Go deeper

Related to this question

About these practice questions

One of 942 original MD-102 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more way this is tested on MD-102

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. Your organization uses Windows Autopilot for user-driven deployments. You need to ensure that during the out-of-box experience (OOBE), users are prompted to set up Windows Hello for Business. Which setting should you configure in the Autopilot profile?

medium
  • A.Skip privacy settings
  • B.Windows Hello for Business
  • C.Device name template
  • D.Language (Region)

Why B: The 'Windows Hello for Business' setting in the Autopilot profile directly controls whether users are prompted to configure biometric or PIN-based authentication during the out-of-box experience (OOBE). When enabled, this setting triggers the Windows Hello for Business enrollment flow immediately after user authentication, ensuring the device is provisioned with strong credential protection before the user reaches the desktop.

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This MD-102 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 MD-102 exam.