ConfigMap keys have been mapped to different file names using the volumes.configMap.items field. What is the result if a wrong ConfigMap key is specified?
I go for "A"
Tried creating the ConfigMap and Pod on Kubernetes. Pod and Volume were not created with the error below:
root@controlplane:~# k describe pod configmap-demo-pod
(snip)
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 57s default-scheduler Successfully assigned default/configmap-demo-pod to controlplane
Warning FailedMount 25s (x7 over 57s) kubelet MountVolume.SetUp failed for volume "config" : configmap references non-existent config key: different.filename
root@controlplane:~#
This section is not available anymore. Please use the main Exam Page.300-910 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
SSSSSS
8 months, 2 weeks agoSSSSSS
8 months, 2 weeks ago