Question 618 of 991
Manage applicationshardMultiple ChoiceObjective-mapped

Quick Answer

The correct choice is User context because it satisfies both requirements: administrative privileges and user interaction during installation. In Intune Win32 app deployment, installation behavior determines the security token under which the installer runs. System context executes as the local SYSTEM account, which has high privileges but cannot display a user interface, making it unsuitable for apps requiring interactive input. User context, by contrast, runs the installer under the logged-on user’s token, which can elevate to admin rights via UAC when needed, while still allowing the user to see and interact with the installation wizard. On the MD-102 exam, this question tests your understanding of how installation behavior settings map to real-world deployment constraints—a common trap is assuming System context is always better for admin privileges, forgetting it blocks UI. Remember the memory tip: “User for UI, System for silent.”

MD-102 Manage applications Practice Question

This MD-102 practice question tests your understanding of manage applications. 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. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. 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 Intune to manage Windows 11 devices. They want to deploy a Win32 app that requires user interaction during installation. The app must be installed with administrative privileges. Which installation behavior setting should you configure?

Question 1hardmultiple 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

User context (user)

System context runs the installer as SYSTEM with no user interaction; User context runs as the logged-on user. The requirement is admin privileges and user interaction, so User context is correct because it allows the installer to run with the user's token, which can elevate if needed. System context prevents UI. Choose behavior 'User' handles both.

Key principle: Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.

Answer analysis

Option-by-option breakdown

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

  • Installation time (64-bit vs 32-bit)

    Why it's wrong here

    Architecture preference, not context.

  • System context (device)

    Why it's wrong here

    Runs in system context without user interaction.

  • Device restart behavior

    Why it's wrong here

    Controls restart, not installation context.

  • User context (user)

    Why this is correct

    Runs as the logged-on user, allowing interaction and elevation.

    Related concept

    Authentication checks who the user is.

Common exam traps

Common exam trap: authentication is not authorization

Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.

Detailed technical explanation

How to think about this question

This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.

KKey Concepts to Remember

  • Authentication checks who the user is.
  • Authorization controls what the user is allowed to do after login.
  • Privilege levels affect access to EXEC and configuration commands.
  • AAA, TACACS+ and RADIUS can separate login success from command access.

TExam Day Tips

  • Do not assume successful login means full administrative access.
  • Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
  • Separate login problems from permission problems before choosing the answer.

Key takeaway

Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.

Real-world example

How this comes up in practice

A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.

What to study next

Got this wrong? Here's your next step.

Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related MD-102 questions on access control and AAA configuration.

Related practice questions

Related MD-102 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 MD-102 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 MD-102 question test?

Manage applications — This question tests Manage applications — Authentication checks who the user is..

What is the correct answer to this question?

The correct answer is: User context (user) — System context runs the installer as SYSTEM with no user interaction; User context runs as the logged-on user. The requirement is admin privileges and user interaction, so User context is correct because it allows the installer to run with the user's token, which can elevate if needed. System context prevents UI. Choose behavior 'User' handles both.

What should I do if I get this MD-102 question wrong?

Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related MD-102 questions on access control and AAA configuration.

What is the key concept behind this question?

Authentication checks who the user is.

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 21, 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 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.