How is PIM usually run?

Question

Options

• AVia settings in IE or Firefox browsers
• BVia a network proxy such as Connector
• CVia a service that runs transparently on the user's machine and cannot be stopped
• DVia a login script or GPO at the time that the user logs on

• A
  4% (2)
• B
  2% (1)
• C
  4% (2)
• D
  91% (49)

Explanation

Option D is correct because PIM (Privilege Identity Management) in enterprise environments is deployed and configured through login scripts or Group Policy Objects (GPOs), which execute automatically when a user logs onto a domain-joined machine - making it the standard, scalable method for enforcing privilege controls across an organization.

Why the distractors are wrong:

• A is wrong because browser settings (IE/Firefox) have no role in managing system-level privilege policies; browsers are client applications, not deployment mechanisms.
• B is wrong because network proxies handle traffic filtering/routing, not user privilege management at login time.
• C is wrong because while PIM agents may run as background services, describing it as something that "cannot be stopped" is inaccurate and misrepresents the deployment method - it conflates the runtime behavior with how PIM is run/initiated.

Memory tip: Think "GPO = Gatekeeper at Login." Just like GPOs enforce password policies and drive mappings at logon, PIM piggybacks on the same Windows infrastructure - it's triggered at the moment the user authenticates, before they ever touch a resource.

No community discussion yet for this question.