CKA Practice Question: Cluster Architecture, Installation & Configuration
This CKA practice question tests your understanding of cluster architecture, installation & configuration. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Exhibit
```
$ kubectl get pods -n kube-system | grep etcd
etcd-master 1/1 Running 0 10d
$ kubectl logs -n kube-system etcd-master | tail -5
2024-01-01 12:00:00.000000 I | embed: rejected connection from "192.168.1.102:45678" (error "tls: first record does not look like a TLS handshake", ServerName "")
2024-01-01 12:00:01.000000 I | embed: rejected connection from "192.168.1.103:45678" (error "tls: first record does not look like a TLS handshake", ServerName "")
2024-01-01 12:00:02.000000 I | embed: rejected connection from "192.168.1.102:45679" (error "tls: first record does not look like a TLS handshake", ServerName "")
$ kubectl get nodes -o wide
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP
master Ready control-plane,master 10d v1.28.0 192.168.1.100 <none>
node1 Ready <none> 10d v1.28.0 192.168.1.101 <none>
node2 Ready <none> 10d v1.28.0 192.168.1.102 <none>
node3 Ready <none> 10d v1.28.0 192.168.1.103 <none>
```
Refer to the exhibit. An etcd pod on the master node shows repeated rejected connections from node2 (192.168.1.102) and node3 (192.168.1.103). The error indicates non-TLS traffic. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
```
$ kubectl get pods -n kube-system | grep etcd
etcd-master 1/1 Running 0 10d
$ kubectl logs -n kube-system etcd-master | tail -5
2024-01-01 12:00:00.000000 I | embed: rejected connection from "192.168.1.102:45678" (error "tls: first record does not look like a TLS handshake", ServerName "")
2024-01-01 12:00:01.000000 I | embed: rejected connection from "192.168.1.103:45678" (error "tls: first record does not look like a TLS handshake", ServerName "")
2024-01-01 12:00:02.000000 I | embed: rejected connection from "192.168.1.102:45679" (error "tls: first record does not look like a TLS handshake", ServerName "")
$ kubectl get nodes -o wide
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP
master Ready control-plane,master 10d v1.28.0 192.168.1.100 <none>
node1 Ready <none> 10d v1.28.0 192.168.1.101 <none>
node2 Ready <none> 10d v1.28.0 192.168.1.102 <none>
node3 Ready <none> 10d v1.28.0 192.168.1.103 <none>
```
A
The API server is using an incorrect etcd endpoint.
Why wrong: Incorrect. The API server typically connects correctly; the errors originate from worker nodes, not the API server.
B
The etcd cluster is not configured for TLS, but clients are using TLS.
Why wrong: Incorrect. The error indicates the opposite: etcd expects TLS but receives non-TLS traffic.
C
The etcd pod is not using the correct certificate authority.
Why wrong: Incorrect. If etcd had a CA issue, TLS handshake would fail differently, not with 'does not look like a TLS handshake'.
D
Kube-proxy on node2 and node3 is incorrectly configured to connect directly to etcd using HTTP instead of HTTPS.
Correct. The error from nodes 2 and 3 suggests they are trying to connect to etcd without TLS. Since they are worker nodes, likely kube-proxy or kubelet is misconfigured to reach etcd directly.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Kube-proxy on node2 and node3 is incorrectly configured to connect directly to etcd using HTTP instead of HTTPS.
The error 'first record does not look like a TLS handshake' means that non-TLS traffic is being sent to etcd's TLS-enabled port. In Kubernetes, components like kube-apiserver communicate with etcd over TLS. But kube-proxy or other components might be sending plain HTTP to the etcd client port. The fact that node2 and node3 are worker nodes (no control-plane role) suggests that kube-proxy or kubelet is misconfigured to connect to etcd directly instead of via the API server.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
The API server is using an incorrect etcd endpoint.
Why it's wrong here
Incorrect. The API server typically connects correctly; the errors originate from worker nodes, not the API server.
✗
The etcd cluster is not configured for TLS, but clients are using TLS.
Why it's wrong here
Incorrect. The error indicates the opposite: etcd expects TLS but receives non-TLS traffic.
✗
The etcd pod is not using the correct certificate authority.
Why it's wrong here
Incorrect. If etcd had a CA issue, TLS handshake would fail differently, not with 'does not look like a TLS handshake'.
✓
Kube-proxy on node2 and node3 is incorrectly configured to connect directly to etcd using HTTP instead of HTTPS.
Why this is correct
Correct. The error from nodes 2 and 3 suggests they are trying to connect to etcd without TLS. Since they are worker nodes, likely kube-proxy or kubelet is misconfigured to reach etcd directly.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.
Detailed technical explanation
How to think about this question
This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
Use explanations to understand the rule behind the answer.
TExam Day Tips
→Underline the problem statement mentally.
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the CKA exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this CKA question in full detail.
Identify which CKA exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
Cluster Architecture, Installation & Configuration — This question tests Cluster Architecture, Installation & Configuration — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Kube-proxy on node2 and node3 is incorrectly configured to connect directly to etcd using HTTP instead of HTTPS. — The error 'first record does not look like a TLS handshake' means that non-TLS traffic is being sent to etcd's TLS-enabled port. In Kubernetes, components like kube-apiserver communicate with etcd over TLS. But kube-proxy or other components might be sending plain HTTP to the etcd client port. The fact that node2 and node3 are worker nodes (no control-plane role) suggests that kube-proxy or kubelet is misconfigured to connect to etcd directly instead of via the API server.
What should I do if I get this CKA question wrong?
Identify which CKA exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This CKA practice question is part of Courseiva's free CNCF certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CKA exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.