What is the most likely reason a CyberArk Identity admin would turn on the "Provisioning" feature within a Web App connector?

Question

Options

• ATo ensure users are automatically on-boarded and off-boarded in a third-party application
• BTo ensure users are provisioned with the appropriate devices when they start
• CTo ensure the web app appears in the users' CyberArk Identity portal when they first sign in
• DTo create an audit log of every time users sign into the web app

• A
  90% (18)
• B
  5% (1)
• C
  5% (1)

Explanation

Provisioning in a Web App connector refers to the automated lifecycle management of user accounts in a connected third-party application - creating accounts when users are onboarded and disabling/removing them when they leave. Option A is correct because this is precisely what the Provisioning feature does: it syncs user identity events (hire, transfer, termination) from the identity provider into the target app automatically.

Why the distractors are wrong:

• B is wrong because provisioning refers to account/identity provisioning, not physical device provisioning - that's handled by MDM/device management tools, not a Web App connector.
• C describes entitlements or app assignment (making the app visible in the portal), which is a separate configuration from provisioning - it's about access assignment, not account lifecycle.
• D describes audit logging/SIEM integration, which is a separate function unrelated to provisioning.

Memory tip: Think of "provisioning" as provision = supply. You're supplying (and removing) user accounts in the third-party app automatically - it's the "hire-to-fire" automation for app accounts. If provisioning is off, admins must manually create and delete accounts in each connected app.

No community discussion yet for this question.