Bird
0
0

After enabling Secrets encryption at rest, you run kubectl get secret mysecret -o yaml. What will you see?

medium📝 Command Output Q5 of 15
Kubernetes - RBAC and Security
After enabling Secrets encryption at rest, you run kubectl get secret mysecret -o yaml. What will you see?
AThe command will fail with a permission error.
BThe secret data will be shown as base64-encoded encrypted blobs.
CThe secret data will be shown decrypted in plain text.
DThe secret will not appear in the output.
Step-by-Step Solution
Solution:
  1. Step 1: Understand how kubectl accesses secrets

    kubectl requests secrets from the API server, which decrypts them before sending.
  2. Step 2: Recognize encryption at rest is transparent to users

    Encryption at rest protects data on disk; users see decrypted data via kubectl.
  3. Final Answer:

    The secret data will be shown decrypted in plain text. -> Option C
  4. Quick Check:

    kubectl shows decrypted secrets despite encryption at rest [OK]
Quick Trick: kubectl shows decrypted secrets; encryption is transparent. [OK]
Common Mistakes:
  • Expecting encrypted blobs in kubectl output
  • Thinking kubectl command fails due to encryption
  • Assuming secrets disappear after encryption

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes