98-366 Networking Fundamentals: Exam Scope, Retirement Status, and a Practical Study Roadmap
Exam 98-366, Networking Fundamentals, validated foundational knowledge of network infrastructure, hardware, protocols, and services for learners building toward IT infrastructure work. It was associated with Microsoft Technology Associate certification and expected general networking knowledge plus practical familiarity with Windows Server, DNS, TCP/IP, name resolution, management tools, protocols, and topologies. The immediate decision for a reader today is not simply how to study: Microsoft retired MTA exams on June 30, 2022, so confirm whether you are reviewing a legacy credential or choosing a current Microsoft learning path before investing in preparation materials.
Can you still take Exam 98-366?
No. Exam 98-366 is no longer available to new candidates because Microsoft retired the MTA certification and its exams on June 30, 2022. A study plan can still help someone understand the historical blueprint, document existing knowledge, or prepare for broader networking work, but it cannot create a current exam appointment or a new MTA award.
Microsoft’s retirement guidance says candidates could register for and take MTA exams until June 30, 2022, and that MTA exams could not be retaken after that date. The same guidance states that a candidate who passed the required exam before it expired earned the certification, which appeared on the certification transcript.
This distinction matters on a page about exam preparation. Do not treat an old 98-366 practice product, voucher reference, or scheduling instruction as evidence that the exam is open. Check Microsoft’s current retirement information before acting on any older third-party page. Microsoft explains that a retired credential is no longer available for new candidates to earn.
What this means for different readers
If you already passed 98-366, the credential remains part of your Microsoft certification record. Microsoft says MTA certifications do not expire, while its retirement policy explains that a retired credential without an expiration date remains in the Active section for two years following retirement before moving according to the transcript policy. Consult your Microsoft Learn profile for the record that applies to you.
If you planned to sit the exam but never completed it, do not build a current certification plan around 98-366. Use the published domains as a networking fundamentals syllabus, then compare Microsoft’s current Fundamentals or role-based options with the job direction you want. Microsoft’s retirement FAQ describes Fundamentals certifications as a starting point for foundation understanding and a bridge toward role-based learning.
What did 98-366 validate?
The exam validated general networking concepts and technologies across three connected areas: network infrastructure, network hardware, and protocols and services. The intended audience was expected to understand foundational terminology and apply it to common network designs, devices, addressing choices, communication models, and services rather than study an isolated list of product commands.
Microsoft’s objective document also lists hands-on experience with Windows Server, Windows-based networking, network-management tools, DNS, TCP/IP, name resolution, network protocols, and topologies as expected background. Treat that list as a readiness check, not as permission to skip fundamentals: practical exposure is most useful when you can explain why a component or service is used.
The three official domains
Understanding network infrastructure accounts for 30–35% of the exam. The network-infrastructure domain includes the Internet, intranet, extranet, VPNs, security zones, firewalls, LANs, WANs, wireless networking, network topologies, and access methods.
Understanding network hardware accounts for 20–25% of the exam. The network-hardware domain covers switches, routers, network addressing, NAT, QoS, and media types.
Understanding protocols and services accounts for 45–50% of the exam. The protocols-and-services domain includes the OSI model, TCP/IP, TCP, UDP, well-known ports, packets, frames, and IPv4 subnetting.
These percentages are blueprint weights, not a promise about the number or order of questions. They are most useful for deciding study emphasis. Protocols and services has the largest stated share, but it depends on infrastructure and hardware concepts: subnetting is easier to interpret when addressing, routing, and device roles are clear.
Which candidates would have benefited from this exam?
98-366 was aimed at people starting in IT infrastructure, especially learners developing a base in networking rather than specialists designing large production environments. Microsoft’s support material mapped Exam 366 to the Networking Fundamentals certification and described the broader IT infrastructure certifications as suitable for people intending to build careers in desktop infrastructure, server infrastructure, or private cloud computing.
That audience includes students, junior support technicians, Windows administrators strengthening their network knowledge, and career changers who need a structured vocabulary. It does not mean that passing the historical exam alone demonstrated advanced troubleshooting, security engineering, cloud architecture, or production network administration. Those capabilities require deeper study and practical work beyond the stated objectives.
A useful self-assessment is to explain a complete path from a client to a remote service. Can you distinguish a LAN from a WAN, identify where a switch and router belong, describe how an address is translated by NAT, explain how DNS resolves a name, and relate an application conversation to TCP or UDP? Gaps in that chain reveal where to begin.
When 98-366 content is still worth studying
The content remains useful as a fundamentals checklist even though the credential is retired. Network infrastructure, addressing, transport protocols, name resolution, and device roles are transferable concepts. Study it as technical foundation, not as evidence that the obsolete exam is a current hiring requirement or a substitute for a current certification.
For a current credential decision, begin with the role you want to perform. A learner targeting cloud administration may need a modern cloud fundamentals path; someone targeting network operations may need vendor-neutral or vendor-specific networking study; someone targeting Windows infrastructure may need current Microsoft role-based material. The official retirement FAQ points learners toward newer generations of certifications rather than a direct successor named for 98-366.
How should you sequence the study?
Study from physical and logical design toward communication behavior: first map infrastructure and hardware, then learn how protocols and services move data through that design. This order prevents memorization without context. Finish by solving small scenarios that require several domains at once, such as choosing a device, locating a failure, or calculating an IPv4 subnet.
A practical sequence is: establish baseline knowledge, learn infrastructure, learn hardware, master protocols and services, integrate the subjects, and perform a final evidence check. The sequence is a recommendation for learning; Microsoft’s objective document supplies the scope and weights, not a mandatory timetable or study schedule.
Before each new topic, write one operational question. For a VPN, ask what it protects and how it connects separated networks. For NAT, ask which address is changed and why. For DNS, ask what happens when a name cannot be resolved. Questions framed around behavior produce stronger understanding than copying definitions.
Stage one: baseline and vocabulary
Start by making a four-column inventory: infrastructure terms, hardware, protocols and services, and practical tools. Place each objective into one column, then mark it as explain, recognize, or apply. “Explain” means you can describe the purpose; “recognize” means you can identify it in a scenario; “apply” means you can use it to reason through a configuration or fault.
Do not spend the first study sessions collecting port numbers or abbreviations. First establish distinctions that commonly collapse together: Internet versus intranet, switch versus router, packet versus frame, TCP versus UDP, and name resolution versus address assignment. Once those pairs are clear, add the details that support them.
Use the official Networking Fundamentals learning series as a structured companion. Microsoft describes the series as covering the building blocks of network design and function and as preparation for 98-366. Its listed topics include LANs, the OSI model, wired and wireless networks, Internet Protocol, TCP/IP command-line tools, network services, WANs, and network infrastructure and security.
Stage two: infrastructure before devices
Learn infrastructure by drawing small networks rather than reading every term in isolation. Create one LAN, one WAN connection, one wireless segment, and one design containing a firewall, security zone, VPN, intranet, and extranet. Label the trust boundary, the users or systems being connected, and the path traffic would take.
For each design, explain the access method and topology in plain language. Then ask what changes when the link is wireless, when a remote user connects through a VPN, or when a service is exposed to an extranet. This exercise turns the domain list into decisions about reachability, separation, and protection.
A common mistake is treating a firewall, VPN, and security zone as interchangeable security labels. They address related but different design questions. A firewall controls or filters traffic according to policy; a VPN provides a protected logical connection over another network; a security zone groups systems or interfaces according to a security boundary. Keep the roles distinct while studying.
Stage three: hardware and addressing
Next, map device responsibilities. A switch connects devices within a local network; a router connects different networks and makes forwarding decisions; NAT changes address information as traffic crosses a boundary; QoS manages traffic treatment when application requirements compete. These concise descriptions are starting points, not a replacement for examining how the devices interact.
Add media types and wireless considerations to the same diagrams. Ask which component is forwarding locally, which component is routing between networks, where addressing is assigned, and where translation occurs. If your answer names only a device but not the traffic movement, revisit the scenario.
Keep addressing practice separate from vague hardware recognition. Work through IPv4 examples on paper: identify the network and host portions, determine whether two addresses share a subnet, and state what a router must do when they do not. Do not rely on a memorized shortcut without checking the mask and the resulting ranges.
Stage four: protocols and services
Give the largest study block to protocols and services because understanding protocols and services accounts for 45–50% of the exam. Organize the material by communication function: models and layers, addressing, transport behavior, ports, units of data, and subnetting. This is more durable than maintaining an unconnected glossary.
Use the OSI model and TCP/IP as explanatory frameworks. For a client request, identify the application activity, transport choice, addressing information, and the local delivery unit. Then distinguish a packet from a frame and explain why the same data can be described differently at different layers.
Compare TCP and UDP by behavior and use case rather than by a single sentence. TCP is associated with connection-oriented, reliable delivery behavior; UDP avoids the same connection and reliability mechanisms. The point of the comparison is to reason about why an application might use one transport rather than recite a preference.
Build a port table only after you understand services. For each well-known port you study, record the associated service, the transport protocol, and the troubleshooting question it helps answer. Keep the table limited to the services represented in the objective scope and verify every entry against authoritative learning material rather than copying an unreviewed dump.
How can you turn the objectives into practical exercises?
Use small, repeatable exercises that make you explain a network from end to end. You do not need access to live exam questions. A diagram, a notebook, and a safe lab or classroom environment are enough to practice device roles, addressing, name resolution, protocol selection, and troubleshooting logic without pretending that configuration practice reproduces the retired assessment.
For a simple scenario, draw a client, switch, router, firewall, DNS service, and remote application. Trace a request by answering: what name is requested, how is it resolved, what address is contacted, which transport behavior is expected, which device forwards the traffic, and where a policy or translation boundary might affect it? Repeat the trace after removing one component.
If you have Windows networking experience, connect study to observable tools and results. The objective document names network-management tools and Windows-based networking as expected background, while Microsoft’s learning series includes TCP/IP command-line tools. The recommendation is to use tools to test a hypothesis: inspect configuration, test reachability, check name resolution, and interpret the result instead of running commands as a memorization exercise.
Keep a fault log with four fields: symptom, likely layer or component, test, and conclusion. Examples include a name that fails to resolve, a host that reaches local devices but not a remote network, or an application that behaves differently under TCP and UDP. Record why a test narrows the possibilities. This habit is valuable beyond any retired certification.
Scenario prompts to practise
A remote employee can reach an internal application by address but not by name. Start with name resolution rather than replacing the switch. Identify the DNS dependency, test whether the name maps correctly, and then consider routing or firewall policy only if the evidence requires it.
Two devices communicate on the same LAN, but a host on another network is unreachable. Check the addressing and subnet relationship, identify the default routing requirement, and locate the router or other Layer 3 boundary. Avoid concluding that the cable or switch is faulty simply because the remote destination fails.
A service is reachable internally but not from an external network. Draw the boundary and consider NAT, firewall rules, exposed service placement, and the intended security zone. The exercise is not to guess a configuration; it is to explain which design controls would need examination.
What study mistakes create false confidence?
The most damaging mistakes are studying retired-exam folklore instead of the published objectives, memorizing isolated terms, ignoring IPv4 subnetting, and treating practice questions as the primary learning method. A candidate can recognize familiar wording while still being unable to explain how a request moves through a network.
Avoid materials that claim access to leaked or live questions. Exam dumps cannot establish that you understand the domains, and memorizing recalled items does not guarantee a passing result. Use the official objective document to define scope, authoritative learning resources to clarify concepts, and original scenarios to test reasoning.
Another error is allocating time only by personal interest. Understanding network infrastructure accounts for 30–35% of the exam and understanding network hardware accounts for 20–25% of the exam, while understanding protocols and services accounts for 45–50% of the exam. Use those labeled weights to prioritize, but do not abandon the smaller domains because they supply the context for the largest one.
Do not confuse a lab’s familiarity with readiness. Clicking through a network simulator can feel productive while hiding uncertainty about why a route, port, address, or policy is needed. After every exercise, close the interface and explain the result from memory. If you cannot explain it, the task was exposure, not mastery.
Finally, do not study old product details as if they were timeless requirements. The blueprint emphasizes concepts such as DNS, TCP/IP, protocols, topologies, hardware, and network design. Learn the underlying behavior first, then use current documentation for any modern platform or role-based path you choose after reviewing the retirement status.
A better review test
For each objective, require three outputs: a definition in your own words, a labeled diagram or comparison, and a short troubleshooting scenario. For IPv4 subnetting, the output should include a worked calculation and an explanation of what the result means for communication. For a protocol, include its role, the relevant transport behavior, and a symptom that could point toward it.
If you miss a question in a self-check, classify the cause before reviewing the answer: terminology gap, diagram gap, calculation error, or reasoning error. Then repair that specific weakness. Re-reading an entire chapter after every miss wastes time and makes progress difficult to measure.
What should a final review look like?
A final review should demonstrate coverage and explanation, not merely a high score on an unofficial quiz. Revisit every objective domain, redraw one complete network, solve fresh IPv4 subnetting problems, explain OSI and TCP/IP relationships, and walk through failures involving hardware, routing, DNS, transport, and security boundaries.
Create a one-page set of contrasts: LAN and WAN, Internet and intranet, switch and router, packet and frame, TCP and UDP, NAT and firewall, and name resolution and addressing. For each pair, write what problem each concept addresses and what evidence would distinguish them during troubleshooting.
Then perform a closed-book verbal review. Explain the path from a local client to a remote service, including the relevant address information, forwarding device, transport behavior, service lookup, and security boundary. Any point at which your explanation becomes a list of terms rather than a sequence of actions is a priority for another study session.
Because 98-366 is retired, the final review should end with a credential decision rather than a scheduling assumption. If you need a current certification, compare the skills you now understand with current Microsoft offerings and the requirements of your target role. If you are documenting a previously earned MTA credential, verify that it appears correctly on your transcript.
A readiness checklist for the underlying skills
You are ready to move on from the historical blueprint when you can explain the purpose of each listed infrastructure component, identify the role of switches and routers, reason through NAT and QoS, distinguish packets from frames, compare TCP and UDP, use well-known ports in context, and calculate or interpret IPv4 subnets without relying on a memorized answer.
You should also be able to connect the concepts. Given a symptom, identify a plausible layer or component, choose a test, and explain what each possible result would mean. That standard is a practical recommendation, not an official pass rule, but it is a more useful measure of networking understanding than recognizing terminology alone.
What are the next steps after studying 98-366 topics?
The next step depends on whether your goal is historical documentation or current career development. A previously earned MTA certification remains on the Microsoft transcript, while a candidate who never passed 98-366 cannot now earn the retired credential. For new study, carry the networking foundation into a current path selected by role, technology, and employer expectations.
Use Microsoft’s retirement pages to verify the status of any related credential before paying for training or scheduling an assessment. Microsoft states that retired exams and associated credentials are no longer available for new candidates after the retirement date. Its retirement policy also notes that certification programs change as technologies and required skills change.
If you are an educator or training provider, the objective document can still serve as a compact syllabus for introductory networking lessons. Pair it with current examples, current security practices, and current platform documentation. Label the material clearly as historical 98-366 coverage so learners do not mistake it for an open exam or a current certification requirement.
If you are an individual learner, save your own notes, diagrams, subnetting work, and fault log. Those artifacts show what you can explain and identify the next technical gap. Then select a current learning or certification target and map its published objectives against the foundation you already built.
How to use this page responsibly
Use this guide to decide what to learn and how to sequence it; do not use it as evidence that an exam appointment is available. The official Microsoft objective document is the authority for the historical scope, and Microsoft Learn is the authority for retirement and transcript guidance.
Third-party practice content should be treated as a study aid only when it explains the underlying concept and allows you to reason through an original scenario. Avoid any source promising real questions, guaranteed results, or a shortcut around learning. Those promises are not supported by the official material supplied for this guide.
Where should you verify the official information?
Start with the Microsoft objective document for the historical title, audience, background expectations, domains, and domain weights. Use Microsoft’s retirement FAQ and retirement policy for availability and transcript questions. The Networking Fundamentals learning series can support concept study, but current certification decisions should be checked against Microsoft’s current credential pages rather than an archived exam reference.
The official links below are the appropriate places to verify status and scope. Dates and program policies can change for other credentials, so do not transfer the retirement details for 98-366 to a different Microsoft exam without checking that exam’s own official page.
Recommended source order
First, read the 98-366 objective document and mark the three domains. Second, review the MTA retirement FAQ to understand why the exam cannot be pursued now. Third, use the Networking Fundamentals series for foundational explanations and exercises. Finally, consult the general retirement and expiration policies when interpreting a transcript or evaluating another credential.
This order separates learning content from credential administration. It also prevents a common research error: using an old exam outline to infer current scheduling, delivery, pricing, renewal, or replacement details that the supplied sources do not establish.
Conclusion
Exam 98-366 is best treated as a retired certification blueprint and a focused networking fundamentals syllabus, not as a current exam opportunity. Its most substantial area was understanding protocols and services at 45–50%, supported by infrastructure and hardware knowledge. Build from network design to devices, then protocols, addressing, subnetting, and troubleshooting scenarios. Before taking any next action, verify your Microsoft transcript if you already earned MTA and choose a current Microsoft or networking path if you did not.
pen_spark
pen_spark
pen_spark
pen_spark
pen_spark