Secret-Sen by CyberArk Actual Free Exam Questions And Answers

Question 1

When attempting to retrieve a credential managed by the Synchronizer, you receive this error:

What is the cause of the issue?

A. The host does not have access to the credential.

B. The Vault Conjur Synchronizer has crashed and needs to be restarted.

C. The Conjur Leader has lost upstream connectivity to the Vault Conjur Synchronizer.

D. The path to the credential was not properly encoded.

Discussion 0

Correct Answer: A Vote an answer

Explanation: Only visible for Fast2test members. You can sign-up / login (it's free).

Question 2

When an application is retrieving a credential from Conjur, the application authenticates to Follower A.
Follower B receives the next request to retrieve the credential.
What happens next?

A. The Coniur Token is stateful and Follower B redirects the request to Follower A to satisfy the request.

B. The Coniur Token is stateless and Follower B is able to validate the Token and satisfy the request.

C. The Coniur Token is stateful and Follower B is unable to validate the Token promptinq the application to re-authenticate.

D. The Coryur Token is stateless and Follower B redirects the request to Follower A to satisfy the request.

Discussion 0

Correct Answer: B Vote an answer

Explanation: Only visible for Fast2test members. You can sign-up / login (it's free).

Question 3

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 make a SOAP call to retrieve the secret from the Central Credential Provider.

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

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

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

Discussion 0

Correct Answer: B Vote an answer

Explanation: Only visible for Fast2test members. You can sign-up / login (it's free).

Question 4

Arrange the steps to configure authenticators in the correct the sequence.

Discussion 0

Correct Answer:

Explanation

Create an authenticator policy for each authenticator and then load the policy to Conjur.
Add each authenticator to conjur.yml using this format: <authenticator type> <SERVICE_ID>.
Execute evoke configuration apply.
Comprehensive Explanation: Authenticators are plugins that enable Conjur to authenticate requests from different types of clients, such as Kubernetes, Azure, or LDAP. To configure authenticators, you need to follow these steps:
Create an authenticator policy for each authenticator and then load the policy to Conjur. This step defines the authenticator as a resource in Conjur and grants permissions to the users or hosts that can use it. You can use the policy templates provided by Conjur for each authenticator type, or create your own custom policy. For more information, see Define Authenticator Policy.
Add each authenticator to conjur.yml using this format: <authenticator type> <SERVICE_ID>. This step enables the authenticator service on the Conjur server and specifies the service ID that identifies the authenticator instance. The service ID must match the one used in the policy. For more information, see Enable Authenticators.
Execute evoke configuration apply. This step applies the changes made to the conjur.yml file and restarts the Conjur service. This is necessary for the authenticator configuration to take effect. For more information, see Apply Configuration Changes.
References: The steps to configure authenticators are explained in detail in the Configure Authenticators section of the CyberArk Conjur Enterprise documentation. The image in the question is taken from the same source.

Question 5

Match each scenario to the appropriate Secrets Manager solution.

Discussion 0

Correct Answer:

Explanation
The appropriate Secrets Manager solution for each scenario is as follows:
token based retrieval of secrets, such as OIDC or JWT: Conjur
workloads requiring the fastest secrets delivery performance possible: ASCP agentless workload authentication that relies on OS User: CCP These solutions are described in the Secrets Management Tools page of the CyberArk website

Question 6

When working with Summon, what is the purpose of the secrets.yml file?

A. It is where you store the Conjur URL and host API key.

B. It is where you define which secrets to retrieve.

C. It is where Summon outputs the secret value after retrieval.

D. It is the log file for Summon.

Discussion 0

Correct Answer: B Vote an answer

Explanation: Only visible for Fast2test members. You can sign-up / login (it's free).

Question 7

Match each cloud platform to the correct Conjur authenticator.

Discussion 0

Correct Answer:

Explanation

AWS -> authn-iam
Azure -> authn-azure
GCP -> authn-gcp
JWT Provider -> authn-jwt
Explanation: Conjur supports different authenticators for different cloud platforms. Each authenticator allows a resource or service running on the cloud platform to authenticate to Conjur using a unique identity token signed by the cloud provider. The following are the descriptions of each authenticator:
authn-iam: Enables an AWS resource to use its AWS IAM role to authenticate with Conjur. The resource sends a request to the AWS Security Token Service (STS) to get a signed AWS access token, and then sends the token to Conjur for verification.
authn-azure: Enables an Azure resource to authenticate with Conjur. The resource sends a request to the Azure Instance Metadata Service (IMDS) to get a signed Azure access token, and then sends the token to Conjur for verification.
authn-gcp: Enables a Google Cloud Platform resource to authenticate with Conjur. The resource sends a request to the Google Cloud Identity and Access Management (IAM) service to get a signed Google identity token, and then sends the token to Conjur for verification.
authn-jwt: Enables an application to authenticate to Conjur using a JWT from a JWT Provider. The application obtains a JWT from the JWT Provider, and then sends the JWT to Conjur for verification.
References: You can find more information about the Conjur authenticators in the following resources:
Supported Conjur Cloud authenticators
Configure Conjur Cloud authenticators
GCP Authenticator

CyberArk Sentry - Secrets Manager - Secret-Sen Exam Practice Test

Contact Us

Useful Links

Latest Updated