CompTIA Network+ (N10-009) · Lesson 4
Cloud Networking: VPCs, Security Groups, Gateways
Explain network functions virtualization, describe a virtual private cloud and its subnets, compare internet and NAT gateways, and compare network security groups with network security lists.
Tip: turn your phone sideways or use full screen for larger labels.
Captions match the narration word for word. Press Space to play or pause and the arrow keys to change scenes.
Learning objective
Explain network functions virtualization, describe a virtual private cloud and its subnets, compare internet and NAT gateways, and compare network security groups with network security lists.
Exam mapping
Domain 1.0: Networking Concepts (23%). Objective 1.3 in the official N10-009 exam objectives.
Key takeaways
- NFV runs network functions (routers, firewalls, load balancers) as software VNFs on standard servers instead of dedicated hardware.
- A VPC is a logically isolated virtual network in a public cloud. You choose its CIDR range and split it into subnets; route tables steer traffic (Azure: VNet, Oracle Cloud: VCN).
- An internet gateway gives two-way internet access. A subnet whose default route (0.0.0.0/0) points to it is a public subnet; instances also need a public IP.
- A NAT gateway sits in a public subnet and gives private instances outbound-only internet access: replies return, but the internet can't start connections in.
- A network security group applies rules to chosen instances (their interfaces). AWS security groups are allow-only and stateful; Azure NSGs also have deny rules and priorities.
- A network security list applies to every instance in a subnet (Oracle Cloud's name; AWS uses network ACLs, which are stateless, allow and deny, checked by rule number).
Exam tips
How the exam asks about this
Questions describe a situation and expect you to recognize the concept behind it.
| If the question mentions… | Think |
|---|---|
| Firewall or router running as a VM on a standard server | NFV (a VNF) |
| Logically isolated network in a public cloud | VPC |
| Subnet's default route points to it; two-way internet | Internet gateway |
| Private instances need outbound updates, no inbound access | NAT gateway |
| Rules attached to specific instances, stateful | Network security group |
| Rules that cover every instance in a subnet | Network security list (AWS: network ACL) |
Common traps
- A NAT gateway goes in the public subnet, not the private one: the private subnet only points its default route at it.
- A NAT gateway doesn't let the internet reach private servers. If outsiders must connect in, use an internet gateway (or a load balancer) with a public subnet.
- Group vs. list is about scope: a group protects chosen instances, a list covers the whole subnet.
- With a stateless list (AWS network ACL), allowing the request isn't enough: the reply traffic needs its own rule.
Practice
Exam-style questions
Answer each one before you open the explanation.
Question 1. A company replaces its hardware firewall and load balancer with software versions that run as virtual machines on standard servers. What is this called?
- Multitenancy
- Network functions virtualization
- Virtual private cloud
- Network address translation
Show answer
B. Network functions virtualization. NFV runs network functions as software (VNFs) on standard servers. A virtual private cloud is an isolated network in a public cloud; it doesn't describe replacing appliances with software.
Question 2. A database server in a private cloud subnet must download security patches from the internet, but no internet host may start a connection to it. What should the administrator add?
- A public IP address on the database server
- An internet gateway route in the private subnet
- A security list that allows all inbound traffic
- A NAT gateway in a public subnet, with the private subnet's default route pointing to it
Show answer
D. A NAT gateway in a public subnet, with the private subnet's default route pointing to it. A NAT gateway gives private instances outbound-only access: replies return, but new inbound connections are blocked. A route to the internet gateway plus a public IP would make the server reachable from the internet.
Question 3. What makes a subnet in a VPC a public subnet?
- Its route table has a default route to an internet gateway
- It uses a public CIDR block
- It has a network security list attached
- It contains a NAT gateway's clients
Show answer
A. Its route table has a default route to an internet gateway. A subnet is public when its route table sends internet-bound traffic (0.0.0.0/0) to an internet gateway. Subnets normally use private address ranges; the address range isn't what makes them public.
Question 4. An administrator wants one set of rules to apply automatically to every instance in a cloud subnet, including instances launched later. Which TWO controls fit? (Select TWO.)
- Network security list
- Security group attached to one instance
- AWS network ACL
- Internet gateway
- NAT gateway
Show answer
A. Network security list and C. AWS network ACL. Security lists (Oracle Cloud) and network ACLs (AWS) apply at the subnet level, to every instance in it. A security group protects only the instances it is attached to; gateways route traffic but don't filter it by rule.
Question 5. An AWS network ACL allows inbound HTTPS to a web subnet, but clients never receive the responses. The security group is correct. What is the most likely cause?
- The internet gateway is out of capacity
- The security group is stateless
- The network ACL is stateless and has no outbound rule for the return traffic
- The NAT gateway is in the wrong subnet
Show answer
C. The network ACL is stateless and has no outbound rule for the return traffic. AWS network ACLs are stateless, so return traffic needs its own outbound rule (to the clients' ephemeral ports). Security groups are stateful, which is why the replies would pass the group automatically.
Transcript
Lesson transcript
The full narration, scene by scene. The captions file contains the same text with timings.
Scene 1 · 0:00
Lesson 4: Cloud networking. Welcome to lesson four. We start objective 1.3: cloud concepts and connectivity options. In lesson three our small office built its own network. Now the company moves its online store into a public cloud. We'll look at three things. Network functions virtualization, which turns network gear into software. The virtual private cloud, the private network you build inside a provider's cloud. And the gateways and security rules that decide what traffic gets in and out.
Scene 2 · 0:32
NFV: network gear as software. First, network functions virtualization, or NFV. Traditionally, every network job needed its own box: a router, a firewall, a load balancer. With NFV, those functions run as software, called virtual network functions or VNFs, on standard servers under a hypervisor. You can deploy a new firewall in minutes, or add more copies when traffic grows. Cloud providers rely on this idea: the routers, firewalls and gateways you use in the cloud are all software.
Scene 3 · 1:05
VPC: your own network in the cloud. Next, the virtual private cloud, or VPC. It's a logically isolated network inside a public cloud, just for your account. You choose its private IP range as a CIDR block, here 10.0.0.0/16, and split it into subnets. Our store puts its web server in a public subnet, and its app server and database in a private subnet. Route tables decide where each subnet's traffic goes. Azure calls this a VNet, and Oracle Cloud calls it a VCN.
Scene 4 · 1:38
Internet gateway: the two-way door. How do customers reach the web server? Through an internet gateway, attached to the VPC. It's a two-way door between the VPC and the internet. What makes a subnet public is its route table: a default route, 0.0.0.0/0, pointing to the internet gateway. The web server also needs a public IP address. In AWS, the gateway translates between that public address and the server's private one. Outsiders can start connections in, so we'll need rules.
Scene 5 · 2:10
NAT gateway: outbound only. The app server and database live in the private subnet. They have no public addresses, and nobody on the internet should reach them. But the app server still needs software updates. That's the job of a NAT gateway. It sits in the public subnet, and the private subnet's default route points to it. Private instances can start connections out and get the replies, sharing the gateway's public address. But the internet can't start a connection in.
Scene 6 · 2:43
Network security groups. Now the rules. A network security group is a set of firewall rules attached to chosen instances, through their network interfaces. Our web server's group allows HTTPS on port 443 from anyone, and SSH only from the admin's address. In AWS, security groups have allow rules only, so everything else is denied. They're also stateful: if a request is allowed in, the reply is allowed out automatically. Azure's network security groups add deny rules and priorities.
Scene 7 · 3:16
Network security lists. A network security list works at the subnet level instead: its rules apply to every instance in the subnet. That's the name Oracle Cloud uses. In AWS, the equivalent is the network access control list, or network ACL. An AWS network ACL has allow and deny rules, checked in order from the lowest number, and the first match wins. It's stateless, so you must allow the replies too. It's a useful second layer behind the groups.
Scene 8 · 3:49
Security group vs. security list. Let's compare them side by side. A security group protects the instances you choose, while a security list or network ACL covers a whole subnet. In AWS, groups allow only and are stateful, while network ACLs can allow or deny, are stateless, and are checked in number order. A packet from the internet passes the subnet's list first, then the instance's group. Using both gives you defense in depth, so one mistake doesn't expose a server.
Scene 9 · 4:22
How the exam asks about this. On the exam, match the clue to the answer. Routers and firewalls running as virtual machines on standard servers means NFV. A logically isolated network in a public cloud is a VPC. Two-way internet access for a subnet is an internet gateway. A private subnet that needs outbound updates only is a NAT gateway. Rules attached to specific instances are a security group, and rules for a whole subnet are a security list or ACL.
Scene 10 · 4:55
Recap: cloud networking. To recap: NFV runs network functions as software on standard servers. A VPC is your isolated network in the cloud, split into subnets with route tables. An internet gateway gives a public subnet two-way internet access, while a NAT gateway lets private instances reach out without letting anyone in. Security groups protect chosen instances, and security lists cover whole subnets. Next, we'll connect the cloud to the office, and compare cloud deployment and service models.
Sources and accuracy
Checked against the official CompTIA N10-009 exam objectives and the standards below on October 24, 2026. Diagrams and addresses in the animation are illustrative.
- CompTIA Network+ N10-009 exam objectives (objective 1.3)
- ETSI: Network Functions Virtualisation (NFV)
- AWS: Internet gateways and NAT gateways (Amazon VPC User Guide)
- AWS: Security groups vs. network ACLs (Amazon VPC User Guide)
- Oracle Cloud: Security lists and network security groups
This free course is independent and isn't affiliated with or endorsed by CompTIA. CompTIA and Network+ are trademarks of CompTIA, Inc.
Preparing a team for Network+?
I run hands-on networking and cloud training for teams, built around your own environment and goals.