Exam Associate Cloud Engineer topic 1 question 50 discussion

A is correct

Vote A https://cloud.google.com/vpc/docs/using-vpc#subnet-rules Primary and secondary ranges for subnets cannot overlap with any allocated range, any primary or secondary range of another subnet in the same network, or any IP ranges of subnets in peered networks.

B is wrong because is not possible to have two subnets with the same CIDR range within a VPC, as it would cause an IP conflict.

This question and answer doesn't add up to me. Why would you need to have a different CIDR range and a different region? For example, if I had 10.0.1.0/24 in us-central1 region, why can't i just use 10.0.2.0/24? in the same region and "/24" is the same CIDR range. The correct answer does not make logical sense to me.

Wrong question with wrong answer

A is correct If you create more than one subnet in a VPC, the CIDR blocks of the subnets cannot overlap. For example, if you create a VPC with CIDR block 10.0. 0.0/24 , it supports 256 IP addresses. You can break this CIDR block into two subnets, each supporting 128 IP addresses.

For anyone new to the business, prod and test networks should never talk to each other.... The requirement in this question (that both envs can reach each other) is completely against best practice and common sense... There should always be complete network isolation between prod and non-prod environments.

I tried to create a VPC with 2 subnets in same regione and same CIDR I got the following error Operation type [insert] failed with message "Invalid IPCidrRange: 10.0.0.0/28 conflicts with existing subnetwork 'subnet-1' in region 'asia-east1'."

A is correct as it help to make sure they have a diffenret subnets

A is the correct Answer. People voting for B need to improve their networking knowledge.

ANSWER A meets the requirement because it creates a single custom VPC with 2 subnets, with each subnet in a different region and with a different CIDR range. This ensures that the production and test VMs are in separate subnets and that they can communicate with each other over Internal IP without creating additional routes. Since the subnets are in different regions, they will also have different internal routing tables, which can help isolate the traffic between the two subnets. This configuration provides the necessary network isolation and connectivity required by the production and test workloads. ANSWER B suggests creating a single custom VPC with two subnets in the same region and with the same CIDR range. However, the requirement is that production VMs need to be in a different subnet than the test VMs. With the subnets in the same region and with the same CIDR range, it would not be possible to separate the production and test VMs into different subnets. Therefore, ANSWER B does not meet the requirement.

https://www.youtube.com/watch?v=XLaFU1t9pM8 8:15

I feel the Answer is A it has to be in the same VPC to talk to each other but on 2 different subnet but is there any sense to have it different region? It should be fine with different CIDR for same region i feel

A, same VPC network with different CIDR range

A is correct

It has to be A: one VPC, two subnets in different regions and different CIDR range. (It would also be valid to have both subnets in the same region.) What about option B? We know that "each primary or secondary IPv4 range for all subnets in a VPC network must be a unique valid CIDR block" (read here https://cloud.google.com/vpc/docs/subnets#ipv4-ranges ). Thus, prod and test subnets cannot overlap -> option B is not valid. Options C and D are not valid neither, because "all the VMs must be able to reach each other" - this will not happen if we distribute the VMs across two VPC.

Leutenant_Ololo, I test and checked. It is B answer