Secret-Sen試験無料問題集「CyberArk Sentry - Secrets Manager 認定」

When using the Seed Fetcher to deploy Kubernetes Followers, an error occurs in the Seed Fetcher container.
You check the logs and discover that although the Seed Fetcher was able to authenticate, it shows a 500 error in the log and does not successfully retrieve a seed file. What is the cause?

解説: (GoShiken メンバーにのみ表示されます)
A customer requires high availability in its AWS cloud infrastructure.
What is the minimally viable Conjur deployment architecture to achieve this?

解説: (GoShiken メンバーにのみ表示されます)
Match each cloud platform to the correct Conjur authenticator.
正解:

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
When attempting to retrieve a credential managed by the Synchronizer, you receive this error:

What is the cause of the issue?

解説: (GoShiken メンバーにのみ表示されます)
You are configuring the Conjur Cluster with 3rd-party certificates.
Arrange the steps to accomplish this in the correct sequence.
正解:

Explanation
The correct sequence of steps to configure the Conjur Cluster with 3rd-party certificates is as follows:
Import 3rd-party certificates to the Leader using the command: docker exec mycontainer evoke ca import --force --root <path-to-root-certificate> --chain <path-to-chain-certificate>1 Configure the Leader using the command: docker exec mycontainer evoke configure master
--accept-eula --hostname <load-balancer-dns> --admin-password <password> <account-name>1 Verify the Conjur Leader configuration using the command: docker exec mycontainer evoke role1 Configure the Standbys using the command: docker exec mycontainer evoke configure standby
--master-address <leader-ip-address> --master-fingerprint <leader-fingerprint>1 References: 1: Certificate requirements
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?

解説: (GoShiken メンバーにのみ表示されます)