Study guide · Topic overview

Networking & Cloud: how traffic and services fit

A subject-based path for the ideas behind everyday networks and cloud platforms: addresses and ports, the devices that move traffic, how names become IP addresses, and who manages what in IaaS, PaaS, and SaaS.

Subject path · not a named certification5 study domainsReviewed October 2026

Scope notice: Networking & Cloud Fundamentals is an independent study topic, not CompTIA Network+, Cloud+, CCNA, or a vendor cloud exam. The domains below organize foundational skills. Items tagged Extra sit outside that everyday set. Port numbers, private ranges, and cloud models match the facts used in the CompTIA A+ networking notes.

What Networking & Cloud Fundamentals covers

A network moves data between hosts. An address says where a host lives, a port says which program should receive the message, and a name such as www.example.com has to be translated into an address before anything is sent. Cloud computing rents those same ideas: virtual networks, virtual machines, storage, and applications, billed by use and scaled with demand.

This path stays at the foundation. You should be able to explain why a laptop shows 169.254.x.x, which port HTTPS uses, why channels 1, 6, and 11 matter on 2.4 GHz, and why the customer still patches the operating system on an IaaS virtual machine.

Who it is for

  • Learners who need a clear map of TCP/IP before a certification course
  • Help-desk and junior admin students connecting Wi-Fi, DNS, and DHCP symptoms
  • Developers who deploy to the cloud and need the shared-responsibility model

What this path is not

  • Not a named certification and not a substitute for official exam objectives
  • Not a routing-protocol, firewall-design, or Kubernetes course
  • Not a cloud-console simulator; vendor menus change and are not reproduced here

Study domains and weighting

These weights organize the notes, flashcards, and 200 practice questions. They are not official exam weights.

  • 1.0 Models, addresses, and ports25%
  • 2.0 Devices, media, and wireless20%
  • 3.0 DNS, DHCP, and troubleshooting20%
  • 4.0 Cloud models and services25%
  • 5.0 Identity and shared responsibility10%
Domain 1.025%

Models, addresses, and ports

Where a packet is going, and which program should receive it.

  • OSI and TCP/IP layers, and what lives at each one
  • IPv4 private ranges, APIPA, loopback, and IPv6 address types
  • CIDR prefixes and usable host counts
  • Common TCP and UDP ports, including which ones are encrypted
Domain 2.020%

Devices, media, and wireless

The boxes and the air that carry the frames.

  • Switch, router, access point, firewall, and modem roles
  • Copper versus fiber, and what PoE is for
  • 802.11 generations, bands, and 2.4 GHz channel planning
  • SSID, and why 6 GHz Wi-Fi 6E expects WPA3
Domain 3.020%

DNS, DHCP, and troubleshooting

How a host gets an address and a name, and what to test first.

  • DNS record types and port 53
  • DHCP DORA and ports 67 and 68
  • Default gateway, ping, and traceroute
  • Separating a local link problem from a DNS problem
Domain 4.025%

Cloud models and services

What you rent, and what still runs on virtual hardware.

  • IaaS, PaaS, and SaaS, and public, private, hybrid, community
  • Elasticity, metered use, regions, and availability zones
  • Block, file, and object storage
  • Type 1 and Type 2 hypervisors, and containers versus virtual machines
Domain 5.010%

Identity and shared responsibility

Who locks the door after the provider builds the building.

  • Shared responsibility by service model
  • TLS in transit, encryption at rest, and HTTPS versus HTTP
  • MFA, least privilege, and roles versus long-lived keys
  • WPA2, WPA3, and why open Wi-Fi does not encrypt traffic

Address and port map

Memorize the ranges and ports you will see in troubleshooting. The same facts are in the core notes and flashcards.

Addresses and ports used throughout this study path. Extra rows are context, not the everyday set.
ItemValueRemember
Private IPv410.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16Not routed on the public internet. 172.16.0.0/12 is 172.16 through 172.31.
APIPA169.254.0.0/16The host could not get a DHCP lease.
Loopback127.0.0.1 and ::1The host talking to itself.
IPv6 link-localfe80::/10Used on the local link, similar in purpose to APIPA.
IPv6 global unicast2000::/3Publicly routable IPv6 space.
/24Mask 255.255.255.0, 254 usable hostsUsable hosts are 2(32 − prefix) − 2.
SSH / HTTP / HTTPSTCP 22 / 80 / 44322 and 443 are encrypted. 80 is not.
DNS / DHCP53 / UDP 67 and 68DNS also uses TCP for large replies and zone transfers.
SMTP / IMAP / POP3TCP 25 / 143 / 110SMTP sends mail. IMAP leaves it on the server. POP3 usually downloads it.
SMB / RDP / LDAPTCP 445 / 3389 / 389File sharing, graphical remote desktop, and directory queries.

Cloud model map

Ask two questions: who operates the stack, and who else shares the infrastructure. Examples are illustrations, not a requirement to use that vendor.

Service models and what the customer still manages. Deployment models describe who shares the infrastructure.
ModelCustomer still managesConcrete picture
IaaSOperating system, middleware, applications, and dataA virtual machine you patch yourself
PaaSApplications and dataA runtime where you deploy code, not the OS
SaaSSettings, user accounts, and dataMicrosoft 365, Google Workspace, or Salesforce
PublicYour configuration and data on shared provider hardwareMultitenant infrastructure over the internet
PrivateOften more of the stack, dedicated to one organizationSingle-tenant cloud, on premises or hosted
HybridBoth sides, plus the link between themPublic and private connected, often by VPN

How to practice without a lab requirement

The ideas are testable from the notes. A small lab makes them stick.

Read an address before you change it

On your own machine, find the IPv4 address, mask, default gateway, and DNS servers. Decide whether the address is private, APIPA, or public before you renew a lease.

Separate name problems from path problems

If a name fails and the IP address works, start with DNS. If the default gateway does not answer, start with the local link, the address, or the DHCP lease.

Name the boundary in the cloud

For any service, say what the provider operates and what you still configure. A virtual machine and a mailbox do not have the same patching job.

How to plan your networking and cloud study

A practical sequence if IP addresses and cloud names still blur together.

01

Learn the address types out loud

Private ranges, APIPA, loopback, and a /24 mask. If you cannot say why 169.254.12.8 is a DHCP clue, stay here.

02

Attach a port to a job

SSH, HTTP, HTTPS, DNS, DHCP, SMTP, IMAP, SMB, and RDP. Say whether the traffic is encrypted by default.

03

Place each device

A switch forwards by MAC address. A router forwards between IP networks. An access point attaches wireless clients. Then add Wi-Fi bands and channels 1, 6, and 11.

04

Practice the first troubleshooting split

Gateway versus public IP versus hostname. Pair that with DHCP DORA and the A, AAAA, CNAME, and MX records.

05

Draw the cloud boundary

Use the flashcards for IaaS, PaaS, SaaS, regions versus availability zones, and who is responsible for data and access.

06

Take timed practice exams

Work through original questions, review every explanation, and return to the notes on domains below 75%.

The NodnWebTools networking and cloud study path

The overview, core notes, flashcards, and practice exams are all published.

Networking & cloud hub →
Available · You are here

Overview

Scope, domains, address and port map, cloud models, and a study plan.

Available

Core Notes

Reference notes for layers, addresses, ports, devices, Wi-Fi, DNS, DHCP, and cloud models.

Available

Practice Exams

200 original questions with custom exams, explanations, and a score report by domain.

Frequently asked questions

Is Networking & Cloud Fundamentals a certification exam?

No. This is a subject-based learning path for everyday networking and cloud ideas. It is not CompTIA Network+, Cloud+, CCNA, or AWS Cloud Practitioner, and it does not award a credential.

Which cloud providers do these notes assume?

The notes stay vendor-neutral. Examples name common services only to make a model concrete, such as a virtual machine for IaaS or Microsoft 365 for SaaS. Console steps differ by provider.

Do I need a cloud account to study?

No. The pages explain the ideas and include practice questions. A free-tier account is optional if you want to click through a console. Do not put real data in a practice account.

What does Extra mean on these pages?

Items tagged Extra are useful context that sits outside the everyday set this path emphasizes, such as Wi-Fi 7 or legacy ports like TFTP.

How is the practice exam scored?

Scores are unofficial percentages. There is no scaled 100-900 score because this is not a named certification exam. Domains below 75% are marked as focus areas.

Address plans, Wi-Fi rules, and cloud console names change. Confirm current behavior with the network you administer and the provider you use.

Related Tools

Useful companions while you study.

All study topics →