Kubernetes - SecretsIf encryption is enabled for Secrets, what changes in etcd storage?ASecrets are stored in a separate databaseBSecrets are stored as encrypted data instead of plain textCSecrets are deleted after encryptionDSecrets remain plain text but access is loggedCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand encryption effect on etcdEnabling encryption causes Secrets to be stored encrypted in etcd, protecting data at rest.Step 2: Confirm no deletion or separate storageSecrets remain in etcd; only storage format changes to encrypted.Final Answer:Secrets are stored as encrypted data instead of plain text -> Option BQuick Check:Encryption changes etcd storage to encrypted data [OK]Quick Trick: Encryption secures Secrets in etcd storage [OK]Common Mistakes:Thinking encryption deletes SecretsAssuming separate database is usedBelieving encryption only logs access
Master "Secrets" in Kubernetes9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More Kubernetes Quizzes ConfigMaps - Creating ConfigMaps from files - Quiz 8hard Health Checks and Probes - Liveness probe concept - Quiz 1easy Health Checks and Probes - HTTP probe configuration - Quiz 13medium Health Checks and Probes - Readiness probe concept - Quiz 6medium Ingress - Ingress controllers (Nginx, Traefik) - Quiz 9hard Networking - Pod-to-Pod communication - Quiz 1easy Resource Management - CPU requests and limits - Quiz 2easy Resource Management - Horizontal Pod Autoscaler - Quiz 6medium Resource Management - CPU requests and limits - Quiz 12easy Secrets - External secret management integration - Quiz 12easy