PAM-DEF 無料問題集「CyberArk Defender - PAM」

（A）Log in to the system as the logon account, then change roofs password

（B）None of these

（C）Log in to the system as the logon account, run the su command to log in as root, and then change root's password.

（D）Log in to the system as root, then change root's password

（A）Retrieve Accounts

（B）Use Accounts

（C）Authorize Password Requests

（D）Access Safe without Authorization

（A）Manage Users

（B）List Accounts

（C）Read Activity

（D）Audit Users

（E）View Entitlements

（A）Upload Accounts Properties

（B）Rename Accounts

（C）Manage Safe

（D）Update Account Properties

（A）Pause, Terminate, None

（B）Suspend, Terminate, Lock Account

（C）Suspend, Terminate

（D）Suspend, Terminate, None

（A）Cluster Vault Manager

（B）PrivateArk Client

（C）PrivateArk Server Monitor

（D）PVWA > Reports

（E）PARClient

（A）It alerts users of upcoming password changes x number of days before expiration.

（B）It instructs the AIM Provider to 'skip the cache' during the defined time period

（C）It instructs the CPM to initiate the password change process X number of days before expiration.

（D）It determines how far in advance audit data is collected tor reports

（A）FALSE

（B）TRUE

（A）To allow CyberArk to manage unknown or lost credentials

（B）To change the password of an account according to organizationally defined password rules

（C）To test that CyberArk is storing accurate credentials for accounts

（D）To generate a new complex password

（A）Accounts that were discovered by CyberArk that have not yet been onboarded

（B）Accounts that were discovered by CyberArk in the last 30 days

（C）All accounts added to the vault in the last 30 days

（D）All users added to CyberArk in the last 30 days

（A）Shutdown PrivateArk Server on DR Vault > Start replication on DR vault

（B）Replicate data from DR Vault to Primary Vault > Shutdown PrivateArk Server on DR Vault > Start replication on DR vault

（C）Shutdown PrivateArk Server on DR Vault > Replicate data from DR Vault to Primary Vault > Shutdown PrivateArk Server on DR Vault > Start replication on DR vault

（D）Shutdown PrivateArk Server on Primary Vault > Replicate data from DR Vault to Primary Vault > Shutdown PrivateArk Server on DR Vault > Start replication on DR vault

（A）PVConfig.xml

（B）plink.exe

（C）dbparm.ini

（D）UnixPrompts.ini

（A）the Vault Administrator

（B）the PasswordManager user

（C）any user with Auditor membership

（D）an account specified by the user

（E）an account stored in the Vault

（A）3

（B）1

（C）4

（D）2

（A）EPM

（B）PSM

（C）PSM for SSH

（D）PTA

（A）Auditors

（B）Vault Admin

（C）DR Users

（D）Operators

（A）FALSE

（B）TRUE

（A）From the PVWA, navigate to the platforms page, select an 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 an existing platform that is similar to the new target account platform and then click Duplicate; name the new platform.

（C）From PrivateArk, copy/paste the appropriate settings in PVConfiguration.xml; then update the policyName variable.

（D）From PrivateArk, copy/paste the appropriate Policy.ini file; then rename it.

（A）Connect to the Active Directory and ensure the organizational unit exists.

（B）Connect to the PrivateArk Client with the Administrator Account to see if there is a user in the Vault Admin Group.

（C）Connect to Sailpoint (or similar tool) to ensure the organizational unit is correctly named; log in to the PVWA with "Administrator" and confirm authentication succeeds.

（D）Search for members that exist only in the mapping group to grant them safe permissions through the PVWA.