QUESTION: 17

What is the correct command to import the root CA certificate into Conjur?

docker exec <ContainerName> evoke ca import no-restart root <rootCcer>
docker exec <ContainerName> evoke import no-restart root <rootCA.cer>
docker exec <ContainerName> evoke ca import no-restart <rootCA.cer>
docker exec <ContainerName> ca import <rootCA.cer>

Answer(s): C

QUESTION: 18

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?

The certificate does not contain the Follower hostname as a Subject Alternative Name (SAN).
Generate a new certificate for the Follower.
One of the PostgreSQL ports (5432. 1999) is blocked by the firewall Open those ports.
Port 443 is blocked; open that port.
The certificate is unnecessary. Use the command option to suppress SSL certificate checking.

Answer(s): A

Reveal Solution Next Question

QUESTION: 19

When loading policy, you receive a 422 Response from Conjur with a message.
What could cause this issue?

malformed Policy file
incorrect Leader URL
misconfigured Load Balancer health check
incorrect Vault Conjur Synchronizer URL

Answer(s): A

Reveal Solution Next Question

QUESTION: 20

After manually failing over to your disaster recovery site (Site B) for testing purposes, you need to failback to your primary site (Site A).
Which step is required?

Contact CyberArk for a new license file.
Reconfigure the Vault Conjur Synchronizer to point to the new Conjur Leader.
Generate a seed for the new Leader to be deployed in Site A.
Trigger autofailover to promote the Standby in Site A to Leader.

Answer(s): C

Reveal Solution Next Question

Free SECRET-SEN Exam Braindumps (page: 5)

QUESTION: 17

QUESTION: 18

QUESTION: 19

QUESTION: 20