A.From the PVWA, navigate to the platforms page, select existing platform that is similar to the new target account platform, manually update the platform settings and click "Save as" instead of save to duplicate and rename the platform.

B.from the PVWA, navigate to the platforms page, select the existing platform that is similar to the new target account platform and click Duplicate, name the new platform.

C.From PrivateArk, copy/paste the appropriate Policy.ini file: then rename it.

D.From PrivateArk, cop/paste the appropriate setting in the PVConfiguration.xml then update the policName variable.

A.FALS

B.TRUE

A.Safe owners should determine the safe name to enable them to easily remember it.

B.The use of these characters V:*<>".| is not allowed.

C.Ensure your naming convention is no longer than 20 characters.

D.Combine environments, owners and platforms to minimize the total number of safes created.

A.Yes, only if a logon account is associated with the root account and the user connects through the PSM-SSH connection component.

B.Yes, when using the connect button, CyberArk uses the PMTerminal.exe process which bypasses the root SSH restriction.

C.Yes, if a logon account is associated with the root account.

D.No, it is not possible.