1V0-61.21 · Question #42
Which tab would an administrator select m the VMware-Dynamic Environment Manager console to define the settings to capture for a specific application?
The correct answer is B. Personalization. Personalization is correct because the VMware Dynamic Environment Manager (DEM) console's Personalization tab is specifically where administrators configure the Application Profiler - defining which registry keys, files, and folders should be captured and restored for each…
Question
Which tab would an administrator select m the VMware-Dynamic Environment Manager console to define the settings to capture for a specific application?
Options
- ACondition Sets
- BPersonalization
- CApplications
- DUser Environment
How the community answered
(23 responses)- A4% (1)
- B91% (21)
- D4% (1)
Explanation
Personalization is correct because the VMware Dynamic Environment Manager (DEM) console's Personalization tab is specifically where administrators configure the Application Profiler - defining which registry keys, files, and folders should be captured and restored for each application. This is the core mechanism DEM uses to roam user-specific application settings across sessions and devices.
Why the distractors are wrong:
- A. Condition Sets - used to define conditional rules (e.g., by OS, IP range, or group membership) that control when policies apply, not what to capture.
- C. Applications - relates to managing application configurations and policies at a higher level, not the granular capture definitions.
- D. User Environment - covers broader environment settings like drive mappings, shortcuts, printers, and environment variables - not application-specific setting capture.
Memory tip: Think "Personalization = personal app settings." Just as Windows Personalization controls how your desktop looks to you, DEM's Personalization tab controls what application data is saved for you - making it the natural home for defining per-app capture settings.
Topics
Community Discussion
5The answer is B, Personalization, and this trips people up because the Applications tab sounds like the obvious place to go. In the DEM console, Applications is where you register or discover the app itself, but once you are inside that app entry, you navigate to the Personalization tab to define exactly which settings, registry keys, and file paths DEM should capture and restore for that application at logon. That distinction matters operationally because if you misconfigure what gets captured there, you see bloated profile archives and slower logon times across your pools, which is the first thing users will complain about. Always think of Personalization as the place where you tell DEM what the profile payload looks like for each app, and the other tabs as supporting context for when and how that payload gets applied.
Solid breakdown, and the one thing worth adding is that before you finalize those capture paths you should run a differential trace to confirm you are not inadvertently scooping up temp or cache directories that inflate the archive and defeat the whole point of per-app granularity.
The distractor here is C, Applications, and I get why people pick it, you hear "settings for a specific application" and your brain goes straight there. But Applications in the DEM console is where you manage your application configs at a higher level, not where you actually define what gets captured. The Personalization tab is where you go to set up the Application Profiler and specify exactly which registry keys, files, and folders DEM should capture and restore for a given app. Think of it this way, Personalization is the action tab, Applications is more of the inventory. Answer is B, do not second-guess it on exam day.
Solid breakdown, though worth adding that without a valid UEM integration configured first, the Personalization tab will let you define all the capture rules you want and none of them will actually apply to a user session.
B is right. The Personalization tab is where you define which registry keys, files, and folders DEM captures per application, which is the whole point of setting up an application profile before you ever think about conditions or user environment mappings.