CyberArk CyberArk Certifications SECRET-SEN Questions & Answers

• Question 1:

  You start up a Follower and try to connect to it with a REST call using the server certificate, but you get an SSL connection refused error.

  What could be the problem and how should you fix it?

  A. The certificate does not contain the Follower hostname as a Subject Alternative Name (SAN). Generate a new certificate for the Follower.

  B. One of the PostgreSQL ports (5432. 1999) is blocked by the firewall Open those ports.

  C. Port 443 is blocked; open that port.

  D. The certificate is unnecessary. Use the command option to suppress SSL certificate checking.

  Correct Answer: A

  The correct answer is A. The certificate does not contain the Follower hostname as a Subject Alternative Name (SAN). Generate a new certificate for the Follower. A possible explanation is: A Follower is a read-only node that replicates data from the Leader node in a Secrets Manager cluster. A Follower can serve requests from clients and applications that need to retrieve secrets or perform other read-only operations. To connect to a Follower with a REST call, the client or application needs to use the server certificate that was generated for the Follower during the installation process. The server certificate is used to establish a secure and trusted connection between the client or application and the Follower. However, if the server certificate does not contain the Follower hostname as a Subject Alternative Name (SAN), the connection will fail with an SSL connection refused error. This is because the SAN is an extension of the X.509 certificate standard that allows the certificate to specify multiple hostnames or IP addresses that the certificate is valid for. If the Follower hostname is not included in the SAN, the client or application will not be able to verify the identity of the Follower, and will reject the connection. To fix this problem, a new server certificate needs to be generated for the Follower, with the Follower hostname added to the SAN. The new certificate can be generated using the openssl command or another tool that supports the SAN extension. The new certificate also needs to be signed by the same certificate authority (CA) that signed the original certificate, and the CA certificate needs to be trusted by the client or application. The new certificate then needs to be copied to the Follower node and configured in the nginx.conf file. The Follower node also needs to be restarted for the changes to take effect. References: Secrets Manager Cluster Installation; Secrets Manager Cluster Configuration; Subject Alternative Name - Wikipedia

• Question 2:

  How many Windows and Linux servers are required for a minimal Conjur deployment that integrates with an existing CyberArk PAM Vault environment, supports high availability, and is redundant across two geographically disparate regions?

  A. 5 Linux servers, 2 Windows servers

  B. 9 Linux servers, 2 Windows servers

  C. 3 Linux servers, 1 Windows server

  D. 10 Linux servers, 2 Windows server

  Correct Answer: B

  This is the correct answer because a minimal Conjur deployment that integrates with an existing CyberArk PAM Vault environment, supports high availability, and is redundant across two geographically disparate regions requires the following servers: 2 Linux servers for the Conjur master cluster, one in each region. The master cluster consists of a leader and a standby node that can automatically failover in case of a leader failure. The leader node performs read/write operations on the Conjur database and policy engine, while the standby node replicates the leader data and can be promoted to leader if needed. The master cluster also hosts the Conjur UI and API endpoints. 4 Linux servers for the Conjur follower clusters, two in each region. The follower clusters consist of one or more follower nodes that perform read-only operations on the Conjur database and policy engine, such as authentication, authorization, and secret retrieval. The follower clusters are horizontally scalable and can be configured behind a load balancer to handle high volumes of requests from applications and clients. The follower clusters also host the Conjur Synchronizer service, which synchronizes secrets from the CyberArk PAM Vault to the Conjur database. 2 Linux servers for the Conjur seed fetcher service, one in each region. The seed fetcher service is a utility that runs on a separate server and periodically fetches the Conjur seed files from the master cluster and distributes them to the follower clusters. The seed files contain the configuration and encryption keys that are required to join a follower node to the Conjur cluster. The seed fetcher service ensures that the follower clusters are always updated with the latest seed files and can join the Conjur cluster without manual intervention. 2 Windows servers for the CyberArk Central Credential Provider (CCP), one in each region. The CCP is a component that provides secure and centralized credential management for applications and clients that need to access secrets from the CyberArk PAM Vault. The CCP exposes a web service interface that allows applications and clients to request credentials based on their identity and permissions. The CCP integrates with the Conjur Synchronizer service to retrieve the secrets from the Conjur database and cache them locally for faster access. Therefore, the total number of servers required for this deployment is 9 Linux servers and 2 Windows servers. This deployment architecture is based on the Conjur documentation1 and the Conjur training course2.

• Question 3:

  Where can all the self-signed/imported certificates be found in Conjur?

  A. /opt/conjur/etc/ssl from the Conjur containers

  B. /opt/conjur/certificates from the Conjur containers

  C. /opt/cyberark/dap/certs from the Conjur containers

  D. Log in to the Conjur UI > Conjur Cluster > Certificates > view.

  Correct Answer: A

  Conjur uses TLS certificates for authentication between nodes and clients. These certificates are either self-signed by Conjur or imported from a third-party CA. All the certificates are stored in the /opt/conjur/etc/ssl directory from the Conjur

  containers. This directory contains the following files:

  ca.crt: The CA certificate used to verify all Conjur node certificates. This is either the self-signed Conjur CA certificate or the imported third-party CA certificate. server.crt: The server certificate used by the Conjur node for HTTPS and mTLS

  connections. This certificate contains the DNS names of the node and the load balancer in the CN and SAN fields.

  server.key: The private key corresponding to the server certificate. cert.pem: A symbolic link to the server certificate file. key.pem: A symbolic link to the server key file. References: Certificate architecture, Certificate requirements, Rotate

  certificates Learn more:

• Question 4:

  What is a main advantage of using dual accounts in password management?

  A. Since passwords are cached for both rotation accounts, it ensures the password for an application will not be changed, reducing the amount of blackout dates when a password expires.

  B. It ensures passwords are rotated every 90 days, which respects the expected downtime for a system, database, or application

  C. It ensures no delays are incurred when the application needs credentials because a password that is currently used by an application will never be changed

  D. Since there are two active accounts, it doubles the probability that a system, database, or application will successfully authenticate.

  Correct Answer: C

  Dual accounts is a password management method that uses two accounts with identical privileges to access a system, database, or application. One account is active and the other is inactive at any given time. The active account remains untouched during password rotation, while the inactive account has its password changed after a grace period. This way, the application can always use the active account without experiencing any delays or errors due to password expiration or change. The advantage of using dual accounts is that it ensures business continuity and seamless access to the target resource, especially for high load and critical applications. References: Manage Dual Accounts, Configure dual accounts

• Question 5:

  An application is having authentication issues when trying to securely retrieve credential's from the Vault using the CCP webservices RESTAPI. CyberArk Support advised that further debugging should be enabled on the CCP server to output a trace file to review detailed logs to help isolate the problem.

  What best describes how to enable debug for CCP?

  A. Edit web.config. change the "AIMWebServiceTrace" value, restart Windows Web Server (IIS)

  B. In the PVWA, go to the Applications tab, select the Application in question, go to Options > Logging and choose Debug.

  C. From the command line, run appprvmgr.exe update_config logging=debug.

  D. Edit the basic_appprovider.conf, change the "AIMWebServiceTrace" value, and restart the provider.

  Correct Answer: A

  The best way to enable debug for CCP is to edit the web.config file in the AIMWebService folder and change the value of the AIMWebServiceTrace parameter to 4, which is the verbose level. This will generate detailed logs in the AIMWSTrace.log file in the logs folder. The logs folder may need to be created manually and given the appropriate permissions for the IIS_IUSRS group. After changing the web.config file, the Windows Web Server (IIS) service needs to be restarted to apply the changes. This method is recommended by CyberArk Support and documented in the CyberArk Knowledge Base1. Editing the basic_appprovider.conf file and changing the AIMWebServiceTrace value is not a valid option, as this parameter does not exist in this file. The basic_appprovider.conf file is used to configure the basic provider settings, such as the AppProviderVaultParmsFile, the AppProviderPort, and the AppProviderCacheMode. The AIMWebServiceTrace parameter is only found in the web.config file of the AIMWebService. In the PVWA, going to the Applications tab, selecting the Application in question, and going to Options > Logging and choosing Debug is not a valid option, as this will only enable debug for the Application Identity Manager (AIM) component, not the CCP component. The AIM component is used to manage the application identities and their access to the Vault. The CCP component is used to provide secure retrieval of credentials from the Vault using web services. Enabling debug for AIM will generate logs in the APPconsole.log, APPtrace.log, and APPaudit.log files in the ApplicationPasswordProvider\Logs folder, but these logs will not help to troubleshoot the CCP authentication issues. From the command line, running appprvmgr.exe update_config logging=debug is not a valid option, as this will only enable debug for the Application Provider Manager (APM) component, not the CCP component. The APM component is used to manage the configuration and operation of the providers, such as the basic provider, the LDAP provider, and the ENE provider. Running appprvmgr.exe update_config logging=debug will generate logs in the appprvmgr.log file in the ApplicationPasswordProvider\Logs folder, but these logs will not help to troubleshoot the CCP authentication issues. References: Enable Debugging and Gather Logs - Central Credential Provider1

• Question 6:

  You have a PowerShell script that is being used on 1000 workstations. It requires a Windows Domain credential that is currently hard coded in the script.

  What is the simplest solution to remove that credential from the Script?

  A. Modify the script to use the CLI SDK to fetch the secret at runtime using Credential Providers installed on each workstation.

  B. Modify the script to make a SOAP call to retrieve the secret from the Central Credential Provider.

  C. Modify the script to run on WebSphere using the Application Server Credential Provider to retrieve the secret.

  D. Use Conjur Summon to invoke the script and inject the secret at run time.

  Correct Answer: D

  Conjur Summon is an open source utility that can fetch secrets from Conjur and export them as environment variables to a sub-process environment. This way, the secrets are not exposed or stored in the script, but are only available at run time. To use Conjur Summon, you need to install the summon-conjur provider on each workstation, define the secrets in a secrets.yml file, and wrap the PowerShell script in summon. For example, if the secret ID is win/domain/cred, the

  secrets.yml file would look like this:

  DOMAIN_CRED: !var win/domain/cred

  And the summon command would look like this:

  summon --provider summon-conjur powershell script.ps1 This will inject the secret value of win/domain/cred as an environment variable named DOMAIN_CRED to the PowerShell script. The script can then access the secret using the

  $env:DOMAIN_CRED syntax.

  References: Summon-inject secrets, cyberark/summon-conjur

• Question 7:

  When attempting to configure a Follower, you receive the error:

  

  Which port is the problem?

  A. 5432

  B. 1999

  C. 443

  D. 1858

  Correct Answer: A

  The error message "psql: server closed the connection unexpectedly" means that the server terminated abnormally before or while processing the request. This is likely due to the Leader Load Balancer not being available on the port and replication cannot be established. The port that is the problem is 5432, which is the default port for PostgreSQL database connections. The Follower needs to connect to the Leader Load Balancer on this port to receive the replication data from the Leader. If the port is blocked or unreachable, the Follower will fail to sync with the Leader and display the error message. References: [Set up Follower], [Troubleshoot Follower]

• Question 8:

  When loading policy, you receive a 422 Response from Conjur with a message.

  What could cause this issue?

  A. malformed Policy file

  B. incorrect Leader URL

  C. misconfigured Load Balancer health check

  D. incorrect Vault Conjur Synchronizer URL

  Correct Answer: A

  The most likely cause for this issue is A. malformed Policy file. A 422 Response from Conjur indicates that the request was well-formed but was unable to be followed due to semantic errors. A common semantic error when loading policy is having a malformed Policy file, which means that the Policy file does not follow the correct syntax, structure, or logic of the Conjur Policy language. A malformed Policy file can result from typos, missing or extra characters, incorrect indentation, invalid references, or other mistakes that prevent Conjur from parsing and applying the Policy file. The message that accompanies the 422 Response will usually provide more details about the error and the location of the problem in the Policy file. To resolve this issue, you should review the Policy file and check for any errors or inconsistencies. You can use a YAML validator or a text editor with syntax highlighting to help you identify and correct any syntax errors. You can also use the Conjur Policy Simulator to test and debug your Policy file before loading it to Conjur. The Conjur Policy Simulator is a web-based tool that allows you to upload your Policy file and see how it will affect the Conjur data model, without actually loading it to Conjur. You can also use the Conjur Policy Simulator to compare different versions of your Policy file and see the changes and conflicts between them. For more information, refer to the following resources: Policy - CyberArk, Section "Policy" Policy Language - CyberArk, Section "Policy Language" Conjur Policy Simulator - CyberArk, Section "Conjur Policy Simulator"

• Question 9:

  You have a request to protect all the properties around a credential object. When configuring the credential in the Vault, you specified the address, user and password for the credential.

  How do you configure the Vault Conjur Synchronizer to properly sync all properties?

  A. Modify VaultConjurSynchronizer.exe.config, uncomment SYNCALLPROPERTIES and update its value to true.

  B. Modify SynchronizerReplication.config, uncomment SYNCALLPROPERTIES and update its value to true.

  C. Modify Vault.ini, uncomment SYNCALLPROPERTIES and update its value to true.

  D. In the Conjur UI under Cluster > Synchronizer > Config, change SYNCALLPROPERTIES and update its value to true.

  Correct Answer: B

  This is the correct answer because the SynchronizerReplication.config file contains the configuration settings for the Vault Conjur Synchronizer service (Synchronizer) to sync secrets from the CyberArk Vault to the Conjur database. The SYNCALLPROPERTIES parameter specifies whether to sync all the properties of the accounts in the Vault or only the password property. By default, the SYNCALLPROPERTIES parameter is set to false, which means that only the password property is synced. To sync all the properties, such as the address and the user, the SYNCALLPROPERTIES parameter needs to be set to true. This answer is based on the CyberArk Secrets Manager documentation1 and the CyberArk Secrets Manager training course2. The other options are not correct because they do not configure the Synchronizer to properly sync all properties. Modifying VaultConjurSynchronizer.exe.config, uncommenting SYNCALLPROPERTIES and updating its value to true is not a valid option, as this file does not contain the SYNCALLPROPERTIES parameter. The VaultConjurSynchronizer.exe.config file contains the configuration settings for the Synchronizer service, such as the log level, the log path, and the service name. The SYNCALLPROPERTIES parameter is only found in the SynchronizerReplication.config file. Modifying Vault.ini, uncommenting SYNCALLPROPERTIES and updating its value to true is not a valid option, as this file does not contain the SYNCALLPROPERTIES parameter. The Vault.ini file contains the configuration settings for the CyberArk Central Credential Provider (CCP) to connect to the Vault server and provide credentials to the applications. The SYNCALLPROPERTIES parameter is not related to the CCP configuration or functionality. In the Conjur UI under Cluster > Synchronizer > Config, changing SYNCALLPROPERTIES and updating its value to true is not a valid option, as this section does not exist in the Conjur UI. The Conjur UI does not have a Cluster, Synchronizer, or Config section. The Conjur UI has a Cluster Config section under Settings, but this section is used to configure the Conjur cluster settings, such as the master IP address, the follower IP address, and the seed fetcher IP address. The SYNCALLPROPERTIES parameter is not related to the Conjur cluster configuration or functionality.

• Question 10:

  You are setting up the Secrets Provider for Kubernetes to support rotation with Push-to-File mode.

  Which deployment option should be used?

  A. Init container

  B. Application container

  C. Sidecar

  D. Service Broker

  Correct Answer: C

  According to the CyberArk Sentry Secrets Manager documentation, the Secrets Provider for Kubernetes can be deployed as an init container or a sidecar in Push- to-File mode. In Push-to-File mode, the Secrets Provider pushes Conjur secrets to one or more secrets files in a shared volume in the same Pod as the application container. The application container can then consume the secrets files from the shared volume. The deployment option that should be used to support rotation with Push-to-File mode is the sidecar, because the sidecar can run continuously and check for updates to the secrets in Conjur. If changes are detected, the sidecar can update the secrets files in the shared volume. The init container, on the other hand, runs to completion and does not support rotation. The application container and the service broker are not valid deployment options for the Secrets Provider for Kubernetes in Push-to-File mode. References: 1: Secrets Provider - Init container/Sidecar - Push-to-File mode 2: Secrets Provider - init container/sidecar - Push-to-File mode