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

Exam Professional Cloud Network Engineer All Questions

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

Exam Professional Cloud Network Engineer topic 1 question 33 discussion

Actual exam question from Google's Professional Cloud Network Engineer
Question #: 33
Topic #: 1
[All Professional Cloud Network Engineer Questions]

You are designing a Google Kubernetes Engine (GKE) cluster for your organization. The current cluster size is expected to host 10 nodes, with 20 Pods per node and 150 services. Because of the migration of new services over the next 2 years, there is a planned growth for 100 nodes, 200 Pods per node, and 1500 services. You want to use VPC-native clusters with alias IP ranges, while minimizing address consumption.
How should you design this topology?

  • A. Create a subnet of size/25 with 2 secondary ranges of: /17 for Pods and /21 for Services. Create a VPC-native cluster and specify those ranges.
  • B. Create a subnet of size/28 with 2 secondary ranges of: /24 for Pods and /24 for Services. Create a VPC-native cluster and specify those ranges. When the services are ready to be deployed, resize the subnets.
  • C. Use gcloud container clusters create [CLUSTER NAME]--enable-ip-alias to create a VPC-native cluster.
  • D. Use gcloud container clusters create [CLUSTER NAME] to create a VPC-native cluster.
Show Suggested Answer Hide Answer
Suggested Answer: A 🗳️
by ESP_SAP at Nov. 2, 2020, 4:31 a.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
ESP_SAP
Highly Voted 4 years, 6 months ago
Correct Answer is (A): The service range setting is permanent and cannot be changed. Please see https://stackoverflow.com/questions/60957040/how-to-increase-the-service-address-range-of-a-gke-cluster I think the correc tanswer is A since: Grow is expected to up to 100 nodes (that would be /25), then up to 200 pods per node (100 times 200 = 20000 so /17 is 32768), then 1500 services in a /21 (up to 2048)
upvoted 31 times
AzureDP900
2 years, 5 months ago
yes, you are right
upvoted 2 times
...
walkwolf3
3 years, 4 months ago
Agreed A. When you create a VPC-native cluster, you specify a subnet in a VPC network. The cluster uses three unique subnet IP address ranges: It uses the subnet's primary IP address range for all node IP addresses. It uses one secondary IP address range for all Pod IP addresses. It uses another secondary IP address range for all Service (cluster IP) addresses. https://cloud.google.com/kubernetes-engine/docs/concepts/alias-ips#cluster_sizing
upvoted 3 times
...
...
Hybrid_Cloud_boy
Highly Voted 4 years, 4 months ago
isn’t max pods per node 110 in VPC native? I don’t understand how the scenario painted by the question is even possible when taking that into consideration.
upvoted 9 times
ThisisJohn
3 years, 5 months ago
Agree with you. "This table assumes the maximum number of Pods per node is 110 (the default and largest possible Pod density)." Ref. https://cloud.google.com/kubernetes-engine/docs/concepts/alias-ips#cluster_sizing_secondary_range_pods
upvoted 2 times
...
...
saraali
Most Recent 2 months, 2 weeks ago
Selected Answer: A
The correct answer is A. Option A allows for optimal address allocation by creating a /25 subnet with secondary ranges of /17 for Pods and /21 for Services. This ensures that even with future growth (100 nodes, 200 Pods per node, and 1500 services), the IP space will be sufficient. By specifying the ranges in a VPC-native cluster with alias IPs, it minimizes address consumption while allowing for scalable growth. This setup meets both the current and future scaling requirements.
upvoted 1 times
...
e865ea8
8 months, 3 weeks ago
A - service should be 1500 and /24 for service will not be sufficient.
upvoted 1 times
...
BenMS
1 year, 4 months ago
Selected Answer: A
I sometimes struggle to work out CIDR ranges, but in this case I think the answer is pretty clear: - Answers C & D do not offer network topologies at all, so can be immediately dismissed - Answer B suggests pods and service subnets should be the same size, which is never recommended in a GKE cluster, therefore it cannot be a correct answer - This leaves A, which is the only feasible choice
upvoted 1 times
...
ananta93
1 year, 8 months ago
Selected Answer: A
Correct Answer A. Please read the question carefully. Expected number of services=1500. So, only a /22 can fulfil that requirement.
upvoted 1 times
...
Komal697
2 years, 1 month ago
Selected Answer: A
Option A is the recommended design topology for this scenario. It suggests creating a subnet of size /25 with two secondary ranges of /17 for Pods and /21 for Services. This allows for efficient use of IP addresses, with enough address space for the expected growth. The VPC-native cluster should be created with these ranges specified. This approach is preferable because it allows for efficient utilization of IP addresses while providing enough address space for future growth.
upvoted 1 times
...
Ben756
2 years, 1 month ago
Selected Answer: A
The correct option is A. Option A proposes to create a subnet of size/25 with 2 secondary ranges of: /17 for Pods and /21 for Services. This design will allow for 8 subnets, with a maximum of 512 Pods each and 2048 services each. The /17 range for Pods will provide up to 512 IPs per node, enough to accommodate the expected growth of 200 Pods per node. The /21 range for Services will provide up to 2048 IPs, enough to accommodate the expected growth of 1500 services.
upvoted 1 times
...
subhala
2 years, 1 month ago
However since 110 pods/node is max, how can we proceed? If we ignore the limit, then A is correct.
upvoted 1 times
...
pk349
2 years, 3 months ago
A: /17 32,768 addresses 128 nodes 14,080 Pods Since growth is expected: up to 100 nodes which would be /25(=128) up to 200 pods per node i.e.,100*200 = 20000 which would be /17(=32768) up to 1500 services which would be /21 (=2048)
upvoted 1 times
...
GCP72
2 years, 8 months ago
Selected Answer: A
Correct Answer is "A"
upvoted 1 times
...
demomailinator
2 years, 8 months ago
Selected Answer: A
Answer is A
upvoted 1 times
...
svsilence
2 years, 9 months ago
A is correct
upvoted 1 times
...
zaxxon
3 years, 1 month ago
Why not C: as the in the question it is stated: using IP alias?
upvoted 1 times
...
lxs
3 years, 2 months ago
Key aspect is GKE requires double room for pods and services. 100x2=200, so 254 which is /24.
upvoted 1 times
...
kumarp6
3 years, 3 months ago
Answer is : A
upvoted 2 times
...
ThisisJohn
3 years, 6 months ago
I don't think it can be A because Google recommends a subnet not smaller than /21 for pods. My vote goes for B If you specify a Pod address range smaller than a /21 range, you risk running out of Pod IP addresses as your cluster grow https://cloud.google.com/kubernetes-engine/docs/concepts/alias-ips#cluster_sizing
upvoted 1 times
ThisisJohn
3 years, 5 months ago
Let me correct myself. A /24 subnet cannot host 1500 services, so answer should be A
upvoted 1 times
...
...
Load full discussion...
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
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago