How is PIM usually run?

Question

Options

• Avia a login script or GPO at the time that the user log on.
• BVia a service that runs transparently, on the user's machine and cannot be stopped
• CVia a network proxy such as a connector
• Dvia setting on IE or Firefox Browser

• A
  88% (23)
• B
  8% (2)
• C
  4% (1)

Explanation

Option A is correct because PIM (Privileged Identity Management/Password Identity Manager in enterprise contexts) typically executes within the user's logon session, requiring it to run via a login script or Group Policy Object (GPO) triggered at logon - this gives it the necessary user context to intercept credentials or enforce identity policies at the right moment.

Why the distractors are wrong:

• B is incorrect because PIM is not a persistent background service that cannot be stopped; it is user-session-dependent, not a system-level daemon.
• C is incorrect because network proxies/connectors are associated with web application gateways or federation services (like Azure AD Application Proxy), not how PIM itself is deployed to end users.
• D is incorrect because browser settings (IE/Firefox) describe how web-based SSO plugins work, not how PIM is run at the OS/session level.

Memory tip: Think "PIM = Policy at Initial Moment" - it kicks in at the moment of login via policy (GPO), just like other enterprise tools (screensavers, drive mappings) that need to act as soon as the user establishes their session.

No community discussion yet for this question.