Examtopics

コメント(12)

• 正解だと思う選択肢: A

  This one is tricky. First i was going with B, then i did some search. Option A and B can indeed add more IPs. However, i think the option is A because between those 2 options the option A we will add IPs without changing the any ours VMs configurations that we currently have. If we choose B might need to change our current VMs configuration in order to reflect the new IP range expanded. You guys understand what i mean?

  Link: https://cloud.google.com/vpc/docs/create-modify-vpc-networks#expand-subnet

  "If you expand the primary IPv4 range of a subnet, you might need to modify other configurations that are assuming this IP address range"

  👍 5

  joao_012023/09/22

• A is the Answer (1st) we can use secondary IP range, since we are talking about VMs. You can optionally add secondary IP address ranges to a subnet, which are only used by alias IP ranges. However, you can configure alias IP ranges for instances from the primary or secondary range of a subnet.

  Each primary or secondary IPv4 range for all subnets in a VPC network must be a unique valid CIDR block. (2nd) 10.1.0.0/20 is a valid block and it will not overlap with 10.0.0.0/20 ( The range is 10.0.0-15.0-255).

  Remember the keywords from the question "primary" and "ip add for the VM)

  👍 3

  Tony_Almaeda2023/11/13
• 正解だと思う選択肢: B

  All subnets have a primary CIDR range, which is the range of internal IP addresses that define the subnet. Each VM instance gets its primary internal IP address from this range. You can also allocate alias IP ranges from that primary range, or you can add a secondary range to the subnet and allocate alias IP ranges from the secondary range. Use of alias IP ranges does not require secondary subnet ranges. These secondary subnet ranges merely provide an organizational tool.

  https://cloud.google.com/vpc/docs/alias-ip

  👍 3

  tesix797482023/11/27