312-97: EC-Council Certified DevSecOps Engineer (ECDE)Demo

By ECCouncil · Question Mode

QuestionQ90

DevSecOps Pipeline-Plan Stage

Cheryl Hines has worked as a senior DevSecOps engineer at an IT company for the past 5 years. Because the Keywhiz secret-management tool provides robust features, including compatibility with all software, untraceable secrets, and no impact from a power cut or server outage, Cheryl’s organization uses it to manage and distribute secrets.

To add a secret by using the Keywhiz CLI, which command should Cheryl use?

  • A $ keywhiz.cli --DevSecTrustStore --user keywhizAdmin login $ keywhiz.cli add secret --name mySecretName < mySecretFile
  • B $ keywhiz.cli --devTrustStore --admin keywhizAdmin login $ keywhiz.cli add secret --name mySecretName < mySecretFile
  • C $ keywhiz.cli --devTrustStore --user keywhizAdmin login $ keywhiz.cli add secret --name mySecretName < mySecretFile
  • D $ keywhiz.cli --devsecTrustStore --admin keywhizAdmin login $ keywhiz.cli add secret --name mySecretName < mySecretFile
Explanation

The Keywhiz CLI development trust-store option is --devTrustStore, and a human account is supplied with --user during login. A secret can then be created with add secret --name mySecretName, with the secret file redirected to standard input. Keywhiz’s official repository documents --devTrustStore as the development/testing trust-store flag.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!