ExamTopics Logo
Mail Us[email protected]
Menu
Google Discussions
exam questions

Exam Professional Cloud Developer All Questions

View all questions & answers for the Professional Cloud Developer exam
Go to Exam

Exam Professional Cloud Developer topic 1 question 209 discussion

Actual exam question from Google's Professional Cloud Developer
Question #: 209
Topic #: 1
[All Professional Cloud Developer Questions]

You are trying to connect to your Google Kubernetes Engine (GKE) cluster using kubectl from Cloud Shell. You have deployed your GKE cluster with a public endpoint. From Cloud Shell, you run the following command:



You notice that the kubectl commands time out without returning an error message. What is the most likely cause of this issue?

  • A. Your user account does not have privileges to interact with the cluster using kubectl.
  • B. Your Cloud Shell external IP address is not part of the authorized networks of the cluster.
  • C. The Cloud Shell is not part of the same VPC as the GKE cluster.
  • D. A VPC firewall is blocking access to the cluster’s endpoint.
Show Suggested Answer Hide Answer
Suggested Answer: B 🗳️
by zellck at Dec. 13, 2022, 12:43 p.m.

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Submit Cancel
alpha_canary
9 months ago
Selected Answer: B
https://cloud.google.com/kubernetes-engine/docs/troubleshooting#kubectl-times-out "If the cluster is a private GKE cluster, then ensure that the outgoing IP of the machine you are attempting to connect from is included in the list of existing authorized networks."
upvoted 1 times
...
__rajan__
1 year, 3 months ago
Selected Answer: B
B is correct.
upvoted 1 times
...
purushi
1 year, 5 months ago
Selected Answer: B
Cloud shells public IP is not present in the authorized networks/IP list of the GKE cluster.
upvoted 1 times
...
mrvergara
1 year, 11 months ago
Selected Answer: D
Where is the info that this is a private cluster?
upvoted 1 times
mrvergara
1 year, 11 months ago
Ok, it is B
upvoted 2 times
...
...
TNT87
2 years ago
https://cloud.google.com/kubernetes-engine/docs/troubleshooting#connection_refused
upvoted 2 times
...
TNT87
2 years ago
Answer B https://cloud.google.com/kubernetes-engine/docs/how-to/private-clusters#cloud_shell
upvoted 1 times
...
zellck
2 years ago
Selected Answer: B
B is the answer. https://cloud.google.com/kubernetes-engine/docs/how-to/private-clusters#cloud_shell If you want to use Cloud Shell to access the cluster, you must add the public IP address of your Cloud Shell to the cluster's list of authorized networks.
upvoted 2 times
...
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.

SaveCancel