CyberArk Object Level Access Control (OLAC) enables administrators to assign permissions to individual objects stored within a Safe rather than relying exclusively on Safe-level authorizations.
This capability is useful when different privileged accounts within the same Safe require distinct access restrictions.
However, enabling OLAC introduces additional authorization-processing requirements.
Without OLAC, the Vault can determine access primarily through Safe-level membership and authorization settings.
When OLAC is enabled, the Vault must also evaluate object-specific permissions for relevant access operations.
As the number of objects, users, groups, and authorization relationships grows, this additional processing can increase administrative overhead and negatively affect Vault performance.
The performance implications are particularly important in large enterprise deployments containing substantial numbers of privileged accounts and frequent credential-access requests.
CyberArk therefore recommends using granular object-level authorization selectively, according to documented business requirements.
An additional limitation is that enabling OLAC for a Safe is not a temporary configuration decision; it cannot subsequently be disabled through the supported configuration mechanism.
Option B identifies a possible operational consequence, but option A represents the specific performance risk emphasized by the source.
Options C and D incorrectly describe PSM functionality and permission inheritance.
[Reference:CyberArk PAM Self-Hosted — Object Level Access Control, Safe Authorization Model, Vault Performance Considerations and OLAC Configuration Limitations.]