CyberArk PAM-DEF Practice Exams
Last updated on Oct 22,2026- Exam Code: PAM-DEF
- Exam Name: CyberArk Defender – PAM
- Certification Provider: CyberArk
- Latest update: Oct 22,2026
What does the Export Vault Data (EVD) utility do?
- A . exports data from the Vault to TXT or CSV files, or to MSSQL databases
- B . generates a backup file that can be used as a cold backup
- C . exports all passwords and imports them into another instance of CyberArk
- D . keeps two active vaults in sync
A
Explanation:
The Export Vault Data (EVD) utility is used to export data from the CyberArk Vault to TXT or CSV files, or to MSSQL databases. This utility enables the creation of reports such as a list of Safes or incoming requests by exporting data from the Vault. Each report is saved in a separate file, which can then be imported into third-party applications or databases for further analysis or reporting purposes12.
Reference: CyberArk Docs – Export Vault Data (EVD) utility1
CyberArk Docs – Export data to files
Users can be resulted to using certain CyberArk interfaces (e.g.PVWA or PACLI).
- A . TRUE
- B . FALSE
A
Explanation:
Users can be restricted to using certain CyberArk interfaces (e.g. PVWA or PACLI) by using the User Type property. The User Type property is a parameter that can be configured in the User Management settings for each user. The User Type property defines which interfaces the user can access the Vault through, such as PVWA, PrivateArk Client, PACLI, PSM, etc. The User Type property is determined by the CyberArk license and can be assigned to users when they are added to the Vault or when their properties are updated. For example, if a user is assigned the User Type of EPVUser, they can access the Vault through PVWA, PrivateArk Client, PrivateArk Webclient, PACLI, and PIMSU. However, if a user is assigned the User Type of BizUser, they can only access the Vault through PVWA1. Therefore, by using the User Type property, administrators can control and restrict which CyberArk interfaces the users can use.
Reference: 1: Manage users, Types of users subsection
Can the ‘Connect’ button be used to initiate an SSH connection, as root, to a Unix system when SSH access for root is denied?
- A . Yes, when using the connect button, CyberArk uses the PMTerminal.exe process which bypasses the root SSH restriction.
- B . Yes, only if a logon account is associated with the root account and the user connects through the PSM-SSH connection component.
- C . Yes, if a logon account is associated with the root account.
- D . No, it is not possible.
B
Explanation:
The ‘Connect’ button is a feature of the PVWA that allows users to initiate a privileged session to a target system through PSM without revealing the account credentials. The ‘Connect’ button can be used to initiate an SSH connection, as root, to a Unix system when SSH access for root is denied, but only if a logon account is associated with the root account and the user connects through the PSM-SSH connection component. A logon account is a linked account that contains the password required to log on to a remote machine in order to perform a task using the regular account. A common use case for using a logon account is managing root accounts on a Unix system. The best practice for Unix systems is to disallow the root user from logging in using SSH. However, SSH is what the PSM uses to sign in to a system to manage the password. To manage the root password without violating this practice, the PSM establishes the session with a non-root account and then SUs to root (the target account). This is done using a linked account called a logon account. The PSM-SSH connection component is a predefined connection component that enables users to connect to Unix systems through PSM using SSH. The PSM-SSH connection component supports the use of logon accounts to access root accounts on Unix systems1.
The other options are not correct, because:
Which file must be edited on the Vault to configure it to send data to PTA?
- A . dbparm.ini
- B . PARAgent.ini
- C . my.ini
- D . padr.ini
A
Explanation:
To configure the CyberArk Vault to send data to Privileged Threat Analytics (PTA), you must edit the dbparm.ini file on the Vault. This file contains parameters that specify how the Vault should forward syslog events to PTA, ensuring that the Vault can send secured syslog data to PTA for analysis and threat detection1.
Reference: CyberArk Docs: Configure Vault Trusted Connection to PTA2
Netenrich: CyberArk Vault via Syslog1
Which Vault authorization does a user need to have assigned to able to generate the "Entitlement Report" from the reports page in PVWA? (Choose two.)
- A . Manage Users
- B . Audit Users
- C . Read Activity
- D . View Entitlements
- E . List Accounts
D, B
Explanation:
D. View Entitlements: This authorization allows the user to view the entitlements, which is essential for generating reports that include access control and authorization levels on accounts.
B. Audit Users: Having ‘Audit Users’ permission is crucial as it enables the user to perform audit-related activities, which are typically part of generating entitlement reports12.
These authorizations ensure that the user has the necessary permissions to access and compile the data required for the Entitlement Report within the CyberArk PVWA.
Which CyberArk group does a user need to be part of to view recordings or live monitor sessions?
- A . Auditors
- B . Vault Admin
- C . DR Users
- D . Operators
A
Explanation:
To view recordings or live monitor sessions, users must be part of the Auditors group or have the appropriate permissions in the relevant Account Safes and Recording Safes12. The other groups do not have the necessary permissions to access the recordings or monitor the sessions by default.
Reference: Monitor Active Sessions, Active Session Monitoring
When a group is granted the ‘Authorize Account Requests’ permission on a safe Dual Control requests must be approved by
- A . Any one person from that group
- B . Every person from that group
- C . The number of persons specified by the Master Policy
- D . That access cannot be granted to groups
C
Explanation:
When a group is granted the ‘Authorize Account Requests’ permission on a safe, dual control requests must be approved by the number of persons specified by the Master Policy. This means that the request will be sent to all the members of the group, but only a certain number of them need to confirm it for the request to be authorized. The Master Policy defines the number of required approvers for each level of confirmation, as well as the number of levels. For example, if the Master Policy requires two approvers at the first level and one approver at the second level, then the request will be sent to the group and two members of the group must confirm it before it is sent to the second level of confirmation, where one more approver is needed.
Reference: Request access
Safe Members
CyberArk Defender – PAM Exam Practice Test
You need to enable the PSM for all platforms.
Where do you perform this task?
- A . Platform Management > (Platform) > UI & Workflows
- B . Master Policy > Session Management
- C . Master Policy > Privileged Access Workflows
- D . Administration > Options > Connection Components
A
Explanation:
To enable PSM for specific platforms, you need to go to Platform Management, select the platform you want to configure, click Edit, expand UI & Workflows, and select Privileged Session Management. There you can customize the PSM settings for that platform, such as the PSM server ID, the connection components, the PSM connection method, and the PSM recording options. You can also disable dual control for PSM connections if needed.
Reference: Configure PSM for Specific Platforms
Select the best practice for storing the Master CD.
- A . Copy the files to the Vault server and discard the CD
- B . Copy the contents of the CD to a Hardware Security Module (HSM) and discard the CD
- C . Store the CD in a secure location, such as a physical safe
- D . Store the CD in a secure location, such as a physical safe, and copy the contents of the CD to a folder secured with NTFS permissions on the Vault
C
Explanation:
The best practice for storing the Master CD is to store it in a secure location, such as a physical safe. The Master CD contains the server key, the public recovery key, and the private recovery key, which are essential for starting, operating, and recovering the Vault. These keys are sensitive and should be protected from unauthorized access, loss, or damage. Therefore, storing the CD in a physical safe ensures that the keys are kept in a secure location when not in use, and that they are available when needed. This is the recommended option by CyberArk1.
The other options are not best practices and should be avoided, as they expose the keys to potential risks, such as theft, corruption, or deletion. Copying the files to the Vault server and discarding the CD is not secure, as it makes the keys accessible to anyone who can access the Vault server or compromise its security. Copying the contents of the CD to a Hardware Security Module (HSM) and discarding the CD is not feasible, as the HSM can only store the server key, not the recovery keys2. Storing the CD in a secure location, such as a physical safe, and copying the contents of the CD to a folder secured with NTFS permissions on the Vault is not necessary, as it creates redundant copies of the keys that may not be synchronized or updated. Moreover, NTFS permissions are not sufficient to protect the keys from malicious or accidental actions.
Reference: Server Keys – CyberArk, section “Server Keys”
Store the Server Key in an HSM – CyberArk, section “Store the Server Key in an HSM”
An auditor needs to login to the PSM in order to live monitor an active session.
Which user ID is used to establish the RDP connection to the PSM server?
- A . PSMConnect
- B . PSMMaster
- C . PSMGwUser
- D . PSMAdminConnect
A
Explanation:
The PSMConnect user is a local user on the PSM server that is used to establish RDP connections to the PSM server. The PSMConnect user has the following permissions: Log on locally, Log on as a batch job, and Allow log on through Remote Desktop Services. The PSMConnect user is also a member of the local group PSMUsers, which has access to the PSM web console. The other user IDs are not used for RDP connections to the PSM server. The PSMMaster user is a local user on the PSM server that is used to run the PSM services. The PSMGwUser user is a local user on the PSM server that is used to run the PSM Gateway service. The PSMAdminConnect user is a local user on the PSM server that is used to connect to the PSM web console as an administrator.
Reference: Privileged Session Manager, Defender – PAM, PSM for Web Console, Connect through PSM for SSH