AWS VPC Peering Configuration Language Collocations
Practise the standard verbs for configuring AWS VPC peering connections.
0 / 5 completed
1 / 5
Fill in: 'We ___ a peering connection between two VPCs so resources in each can communicate over private IPs without traversing the internet.'
We 'establish a connection' — the standard, established AWS collocation for setting up VPC peering. The other options aren't the recognised term here.
2 / 5
Fill in: 'Overlapping CIDR blocks between two VPCs can ___ the peering request rejected outright before any traffic can flow.'
We say overlapping ranges will 'leave' the request rejected — the standard, natural collocation for the resulting failure. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ route table entries in both VPCs pointing at the peering connection so traffic actually knows how to reach the other side.'
We 'add an entry' — the standard, simple collocation for inserting a new route into a table. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ security group rules on both sides so peering alone doesn't implicitly grant broader access than each VPC actually intends.'
We 'tighten rules' — the standard, established collocation for restricting security group access to only what's needed. The other options aren't the recognised term here.
5 / 5
Fill in: 'We ___ connectivity across the peering link with a simple ping test right after setup, before relying on it for real traffic.'
We 'verify connectivity' — the standard, simple collocation for confirming a network path actually works. The other options are less idiomatic here.