In the screenshot displayed, you just configured the usage in CyberArk and want to update its password. What is the least intrusive way to accomplish this?
Correct Answer: C
Explanation A usage is a configuration that allows CyberArk to manage passwords for files, such as XML or INI files, that are stored on remote machines. A usage is associated with a parent account, which is the account that has access to the file. To update the password of a usage, the least intrusive way is to use the "sync" button on the usage's details page. This will synchronize the password value between the Vault and the file, without changing the actual password. The "change" button will initiate a password change process by the CPM, which will generate a new random password for the usage and the file. The "reconcile" button will initiate a password reconcile process by the CPM, which will use a reconcile account to reset the password of the usage and the file to the value stored in the Vault. References: Usages, Manage passwords for usages
Question 117
Which file must be edited on the Vault to configure it to send data to PTA?
Correct Answer: C
Question 118
Which utilities could you use to change debugging levels on the vault without having to restart the vault. Select all that apply.
Correct Answer: A,D
Question 119
You want to give a newly-created group rights to review security events under the Security pane. You also want to be able to update the status of these events. Where must you update the group to allow this?
Correct Answer: A
Question 120
To enable the Automatic response "Add to Pending" within PTA when unmanaged credentials are found, what are the minimum permissions required by PTAUser for the PasswordManager_pending safe?
Correct Answer: A
Explanation To enable the automatic response "Add to Pending" within PTA when unmanaged credentials are found, the PTAUser needs to have the minimum permissions for the PasswordManager_pending safe as follows: * List Accounts: This permission allows the PTAUser to view the accounts in the safe and their properties. * View Safe members: This permission allows the PTAUser to view the members of the safe and their authorizations. * Add accounts (includes update properties): This permission allows the PTAUser to add new accounts to the safe and update their properties, such as name, address, platform, and policy. * Update Account content: This permission allows the PTAUser to update the password of the accounts in the safe. * Update Account properties: This permission allows the PTAUser to update the properties of the existing accounts in the safe, such as name, address, platform, and policy. These permissions are required for the PTAUser to be able to detect unmanaged privileged accounts and add them to the pending accounts queue in the PasswordManager_pending safe. The PTAUser also needs to have the same permissions for the PasswordManager_reconcile safe to enable the automatic response "Reconcile credentials" for suspicious password change events. References: Configure PTA Remediations, Safe Member Authorizations
