[Solved] Which of the following is the correct way to create a Secret in Kubernetes using a literal value? — Ans: kubectl create secret generic mysecret --from-literal=password=12345 | Microservices

Microservices - Orchestration with Kubernetes

Which of the following is the correct way to create a Secret in Kubernetes using a literal value?

Akubectl create secret generic mysecret --from-literal=password=12345

Bkubectl create configmap mysecret --from-literal=password=12345

Ckubectl secret create mysecret --from-file=password.txt

Dkubectl create secret mysecret --password=12345

Step-by-Step Solution

Solution:

Step 1: Recall Kubernetes Secret creation syntax
The correct command uses kubectl create secret generic with --from-literal to create a secret from a literal key-value pair.
Step 2: Eliminate incorrect options
kubectl create configmap mysecret --from-literal=password=12345 uses configmap instead of secret, kubectl secret create mysecret --from-file=password.txt uses wrong command syntax, kubectl create secret mysecret --password=12345 uses invalid flag.
Final Answer:
kubectl create secret generic mysecret --from-literal=password=12345 -> Option A
Quick Check:
Secret creation uses 'kubectl create secret generic' [OK]

Quick Trick: Secret creation uses 'kubectl create secret generic' [OK]

Common Mistakes:

MISTAKES

Master "Orchestration with Kubernetes" in Microservices

9 interactive learning modes - each teaches the same concept differently

More Microservices Quizzes

Which of the following is the correct way to create a Secret in Kubernetes using a literal value?