An administrator would like to track these details for all Windows desktops managed by Workspace ONE UEM: - Driver details for a mouse driver - Warranty information for OS - Registry value of internal

Question

Options

• ACreate LGPO and assign to Windows devices.
• BCreate Application Control profile and assign to Windows devices.
• CCreate an OEM update profile and assign to Windows devices.
• DCreate sensors and assign to Windows devices.

• A
  6% (2)
• B
  16% (5)
• C
  3% (1)
• D
  74% (23)

Explanation

Sensors (option D) are the correct Workspace ONE UEM utility because they are purpose-built to query and report on specific device data points - including registry values, WMI queries, and PowerShell script output - making them ideal for tracking custom details like mouse driver info, warranty data, and internal app registry values.

Why the distractors are wrong:

• A (LGPO) applies Local Group Policy Objects to enforce security/configuration settings - it controls behavior, not data collection.
• B (Application Control) manages which applications are allowed or blocked; it doesn't gather inventory or custom device data.
• C (OEM Update profile) handles firmware and OEM software updates, not querying device-specific metadata.

Memory tip: Think of Sensors like diagnostic probes - just as a doctor uses sensors/instruments to read vital signs, Workspace ONE Sensors "read" and report specific data points from a device back to the UEM console. If the goal is to collect and report custom info, sensors are the answer.

No community discussion yet for this question.