Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
An organization operates an existing auto mode Virtual Private Cloud (VPC) network. A cloud engineer needs to manually add a new subnet to this network in the us-central1 region to host a dedicated internal testing service.
The engineer must select a valid primary IPv4 CIDR range that does not overlap with any existing subnets or the predefined IP block allocated for auto mode networks.
Which CIDR range should the engineer assign to the new subnet?
169.254.10.0/24 is a sub-block of 169.254.0.0/16, which is designated by RFC 3927 as link-local address space for non-routable host auto-configuration.
169.254.0.0/16 range or any subnet thereof.169.254.0.0/16 internally to host virtual metadata servers (e.g., 169.254.169.254) and to establish BGP peering sessions over Cloud Router interfaces.169.254.0.0/16.0.0.0.0/8, 127.0.0.0/8, 224.0.0.0/4 (multicast), and 255.255.255.255/32.You were configuring link-local IP addresses on a Cloud Router BGP interface to establish dynamic routing with an on-premises VPN or Cloud Interconnect peer.
Students sometimes confuse link-local IP ranges with RFC 1918 private IP ranges. Only RFC 1918 blocks (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) and valid privately used public IP ranges can be used for VPC subnets.
10.10.0.0/24 is a standard private IPv4 CIDR range within the RFC 1918 10.0.0.0/8 private address space. In Google Cloud, it provides 256 total IPv4 addresses, with 252 usable host addresses after subtracting the four reserved IP addresses required to operate the subnet.
10.128.0.0/9 address block. Because 10.10.0.0/24 is part of 10.0.0.0/9 (10.0.0.0 through 10.127.255.255), it sits completely outside 10.128.0.0/9 (10.128.0.0 through 10.255.255.255)./24 prefix mask is within Google Cloud's allowed subnet mask range (from /8 to /29).
10.128.0.0/9.10.128.0.0/9, using 10.10.0.0/24 guarantees that future Google Cloud regions will not create an IP collision.When working with auto mode VPC networks, any manually added subnet must strictly avoid the 10.128.0.0/9 reservation block. Selecting an RFC 1918 range such as 10.10.0.0/24 satisfies all validation criteria, avoids route conflicts, and permits successful creation of the new subnet.
10.170.0.0/24 is a /24 subnet block located inside 10.128.0.0/9. In auto mode VPC networks, 10.170.0.0/20 is the predetermined CIDR range assigned to automatically created subnets in the asia-east2 region.
10.128.0.0/9 block is reserved for automatically created subnets. Manually created subnets in an auto mode network cannot use addresses inside 10.128.0.0/9.10.170.0.0/24 is a subset of 10.170.0.0/20. Google Cloud does not allow creating a subnet that matches, nests inside, or overlaps any existing subnet CIDR block within the same VPC.10.128.0.0/9, which Google Cloud reserves for current and future auto mode subnets.asia-east2.The network was originally converted from auto mode to custom mode, the automatically created asia-east2 subnet was deleted, and no other resources or routes referenced the 10.170.0.0/24 range.
A common misconception is that a narrower subnet mask (such as /24) can be carved out of a larger unused subnet (such as /20). In Google Cloud VPC networking, any overlap with an existing primary or secondary subnet CIDR is strictly prohibited.
10.128.0.0/20 is the specific predefined IPv4 primary range automatically allocated to the default subnet in the us-central1 region whenever an auto mode VPC network is created.
10.128.0.0/20 already exists in us-central1. Attempting to allocate this range for another subnet causes an immediate conflict error.us-central1 during auto mode network creation.10.128.0.0 through 10.128.15.255, providing 4,092 usable host IP addresses.10.128.0.1 as the virtual default gateway address.The network were a custom mode VPC network where no subnets had yet been provisioned in us-central1, and an administrator chose to manually assign 10.128.0.0/20 to the first custom subnet.
In auto mode networks, each region is automatically populated with a /20 subnet drawn from 10.128.0.0/9. Subnet IP collisions frequently occur when administrators try to reuse these well-known default ranges manually.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated