Designing Cisco Network Service Architectures (300-320 ARCH) Exam Guide
Designing Cisco Network Service Architectures is Cisco’s 300-320 ARCH exam, associated with the Cisco Certified Design Professional certification. It validates architecture decisions across enterprise Layer 2 and Layer 3 infrastructures, WAN technologies, data-center integration, network security, and network services. This guide helps you decide whether your preparation should begin with routing, campus design, WAN selection, or a gap assessment—and how to turn the official topic outline into design practice rather than a list of isolated technologies.
What the 300-320 ARCH exam is designed to validate
The exam evaluates whether you can select and shape network architectures for enterprise requirements, not merely recall individual Cisco commands. Cisco identifies the scope as enterprise Layer 2 and Layer 3 infrastructures, WAN technologies, data-center integration, network security, and network services. The exam is identified as Designing Cisco Network Service Architectures, numbered 300-320 ARCH, and Cisco associates it with the Cisco Certified Design Professional certification. [https://learningcontent.cisco.com/documents/exam-topics/300-320-arch.pdf]
That scope points toward decisions such as choosing an appropriate connectivity model, building a scalable addressing plan, controlling route propagation, and designing for availability or convergence. A useful study question is therefore not only “What does this protocol do?” but also “Which business or technical constraint makes this design preferable to the alternatives?”
The official topic document is a guide rather than a promise that every possible question will be limited to its wording. Cisco states that the listed topics are general guidelines, that related topics may also appear, and that the guidelines may change without notice. Check the current Cisco source before scheduling and use the outline as the foundation of your preparation, not as a guarantee of exact coverage. [https://learningcontent.cisco.com/documents/exam-topics/300-320-arch.pdf]
Who should use this guide
This guide is most useful for candidates who already work with enterprise routing, switching, WAN connectivity, or network architecture and need to organize that experience around design outcomes. It is also suitable for experienced network professionals moving from implementation work into architecture decisions, provided they are willing to review areas they have not designed directly.
Do not interpret the certification association as proof that a particular job title or background is mandatory; the supplied Cisco material does not state prerequisites. Instead, compare your current work with the scope. If your experience is limited to one campus, one routing protocol, or a single WAN model, plan deliberate study in the less familiar areas rather than assuming operational familiarity will cover the whole blueprint.
How to read the measured-skill outline
Start with the two documented weighted areas, then use the remaining topic statements to identify unweighted study obligations. Advanced addressing and routing solutions for enterprise networks account for 22% of the documented exam topics, while advanced enterprise campus networks account for 20%. Each percentage belongs to its named domain; neither should be treated as a general pass-score target or compared without its domain label. [https://learningcontent.cisco.com/documents/exam-topics/300-320-arch.pdf]
The outline also identifies WAN design, IPv6, and other architecture subjects. The supplied facts do not provide percentages for every area, so do not invent a complete percentage breakdown. A sensible allocation method is to give extra practice time to the documented weighted domains while reserving explicit sessions for every named topic that could expose a knowledge gap.
Convert each outline item into three notes: the requirement it addresses, the design choice it affects, and the failure or trade-off it is meant to control. For example, “route summarization” should become a design exercise involving hierarchy, route visibility, failure boundaries, and filtering—not a definition copied into flashcards.
Advanced addressing and routing: the highest documented weight
Advanced addressing and routing solutions for enterprise networks account for 22% of the documented exam topics, making this the clearest place to begin if your study time is limited. Build from address hierarchy and summarization into protocol behavior, policy control, IPv6 transition choices, and the relationship between routing design and operational scale. [https://learningcontent.cisco.com/documents/exam-topics/300-320-arch.pdf]
The addressing objectives emphasize structured designs that support summarization, with attention to hierarchy, efficiency, scalability, and NAT. Practice drawing an address plan for several sites and explaining where summaries should be advertised, where exceptions may be necessary, and how NAT changes the edge design. The point is to defend a structure, not merely calculate subnets.
The routing objectives cover stable, secure, and scalable designs for IS-IS, EIGRP, OSPF, and BGP. Compare those protocols by the design problem being solved: internal reachability, policy boundaries, convergence behavior, scalability, or external path control. Keep a decision table that records assumptions and consequences, because memorizing feature names without understanding their architectural use leads to weak answers.
Advanced enterprise campus design: turn requirements into topology choices
Advanced enterprise campus networks account for 20% of the documented exam topics. Prepare by linking availability, Layer 2 scale, convergence, and traffic paths to a concrete campus topology. A design is stronger when you can explain what happens during a link, device, or path failure and why the selected control mechanisms limit disruption. [https://learningcontent.cisco.com/documents/exam-topics/300-320-arch.pdf]
Cisco’s campus objectives include high availability, first-hop redundancy protocols, device virtualization, Layer 2 scalability, fast convergence, and loop-free technologies. Study these as connected concerns. For example, a Layer 2 extension may affect loop prevention, failure domains, convergence, and gateway placement at the same time. Avoid treating each technology as an independent memorization chapter.
Multicampus Layer 3 design objectives include convergence, load sharing, route summarization, route filtering, VRFs, and optimal topologies. Draw at least one multicampus design and annotate the control points: where routes are summarized, where filtering occurs, which paths carry primary and backup traffic, and how VRFs separate routing domains. Then alter one requirement and redesign the affected portion rather than starting over from scratch.
Routing policy: study BGP as a set of design controls
BGP preparation should focus on controlling reachability and path selection at boundaries. The documented objectives include transit prevention, basic route filtering, authentication, communities, basic traffic engineering, and route reflectors. For each objective, write the design risk it addresses and the smallest policy mechanism that mitigates that risk. [https://learningcontent.cisco.com/documents/exam-topics/300-320-arch.pdf]
A useful exercise is to model an enterprise connected to more than one external path. Decide which routes should be accepted, which should be advertised, and how an unintended transit path would be prevented. Add communities to represent policy intent, then identify where route reflection could simplify internal distribution and what consistency concerns it introduces.
Do not reduce BGP study to lists of attributes. Explain the direction of a policy, the boundary where it is applied, the routes it affects, and the failure mode if it is absent. Include authentication in the same design review: security controls are part of an architecture, not an afterthought added after path selection is complete.
The official wording describes basic traffic engineering rather than an unrestricted study of every advanced BGP feature. Prioritize the documented controls first, then expand only where a related topic helps you understand the stated objective. This keeps preparation aligned with the source without assuming that an exhaustive command reference is the exam blueprint.
IPv6 and transition decisions: choose the architecture before the mechanism
The IPv6 objective is to select among overlay tunneling, native dual-stacking, and IPv4/IPv6 translation at boundaries. Prepare by matching each option to the network’s constraints, dependencies, and desired end state. The correct design explanation should include where the transition technique is used and why alternatives are less suitable for that situation. [https://learningcontent.cisco.com/documents/exam-topics/300-320-arch.pdf]
Create three short scenarios: an organization that can operate both protocols across its infrastructure, an environment where parts of the path still require IPv4 transport, and a boundary where IPv4 and IPv6 systems must communicate. For each, select one approach and record the operational costs, routing implications, and points of failure you would investigate.
A common mistake is treating tunneling, dual-stacking, and translation as interchangeable deployment commands. They solve different architectural constraints. Your notes should show the distinction between carrying one protocol across an underlying transport, operating both protocols in the network, and translating between protocol families at a boundary.
WAN architecture: compare the service, not just the acronym
WAN preparation should begin with requirements such as reachability, resilience, security, site scale, extranet access, and Internet-edge behavior. The documented technologies include DMVPN, Layer 2 VPN, MPLS Layer 3 VPN, IPsec, GRE, private lines, and GETVPN, while the WAN section covers connectivity comparison, site-to-site VPNs, resilient strategies, extranet connectivity, and Internet-edge connectivity. [https://learningcontent.cisco.com/documents/exam-topics/300-320-arch.pdf]
Build a comparison matrix with one row per technology and columns for the problem it addresses, the trust or security model it assumes, the topology it supports, the operational dependency it creates, and the type of resilience it can provide. Do not fill gaps with guesses. Where your source material does not establish a property, mark it for verification in Cisco documentation or a lab.
Then apply the matrix to design briefs. One brief might require secure site-to-site communication; another might involve many branches; another might require controlled connectivity to an external organization; another might require a resilient Internet edge. The purpose is to select a service based on constraints rather than choosing a familiar technology by habit.
Separate the underlay from the overlay in every diagram. Label private lines, provider VPN constructs, tunnels, encryption, routing domains, and Internet-facing boundaries. This makes it easier to explain whether a proposed failure affects transport, encapsulation, routing reachability, or security policy.
A practical study sequence for the full scope
Use a requirements-first sequence: inventory the blueprint, refresh foundational behavior, solve addressing and routing designs, work through campus and multicampus cases, compare WAN options, then integrate security, services, data-center, and IPv6 considerations. This order reduces the risk of learning isolated features without understanding how they interact in an enterprise architecture.
Step 1: establish a gap map
Copy each official objective into a study sheet and classify it as strong, usable, or weak. “Strong” means you can explain the design choice and its trade-offs; “usable” means you recognize the technology but need structured practice; “weak” means you would need reference material to begin a design. This is more informative than counting how many chapters you have read.
Mark whether each item is conceptual, diagram-based, or likely to require comparison. Addressing hierarchy, route filtering, first-hop redundancy, and WAN selection should not all be studied with the same method. Your gap map should determine the next week’s work, not merely document what you already know.
Step 2: build the routing and addressing model
Begin with an enterprise address hierarchy and use it to practice summarization, NAT placement, and routing-domain boundaries. Add IS-IS, EIGRP, OSPF, and BGP only after you have a topology in which their design roles are clear. For every protocol decision, state the intended scale, stability, security, and policy result.
Review the BGP objectives separately and test your understanding with route advertisements drawn in both directions. Include transit prevention, basic filtering, authentication, communities, basic traffic engineering, and route reflectors in the same scenario so you learn how controls interact.
Step 3: solve campus and multicampus failures
Create a campus diagram that includes redundant paths, gateway redundancy, Layer 2 boundaries, and a Layer 3 core or interconnection. For each failure you introduce, record the expected convergence path, the traffic that may be affected, and the mechanism intended to prevent loops or preserve availability.
Extend the design to multiple campuses. Add summarization, filtering, load sharing, VRFs, and alternate paths one at a time. This exposes whether you understand the difference between a topology that is physically redundant and one whose routing policy actually uses that redundancy.
Step 4: compare WAN and IPv6 options
Use short design briefs instead of rereading technology descriptions. Each brief should specify site relationships, resilience expectations, security boundaries, Internet or extranet requirements, and IPv4 or IPv6 constraints. Select an architecture, list the rejected alternatives, and state what information you would request before implementation.
Finish this phase by redrawing the chosen design with control-plane and data-plane labels. If you cannot show where routing, encryption, translation, filtering, or provider separation occurs, the design is not yet ready for timed decision practice.
Step 5: integrate the less familiar scope
Reserve time for the stated areas of enterprise Layer 2 and Layer 3 infrastructure, WAN technologies, data-center integration, network security, and network services even when the documented outline gives no percentage for them. Treat these as integration topics: ask how a campus, WAN, routing, security, or service decision changes when another architecture is added.
Use the official outline as your checklist and consult current Cisco material for any topic whose wording or availability may have changed. Cisco explicitly warns that the guidelines may change without notice, so a study plan should include a final source review rather than ending with an old set of notes. [https://learningcontent.cisco.com/documents/exam-topics/300-320-arch.pdf]
How to practice design questions without relying on dumps
Practice by making and defending architecture choices from stated requirements. A sound exercise gives you constraints, several plausible options, and a failure or growth condition that reveals the consequences of each choice. This builds the reasoning the blueprint describes without depending on leaked questions, copied answers, or claims about the live assessment.
Use a requirement-to-design worksheet
For every scenario, write five lines: business requirement, technical constraint, candidate architecture, rejected alternative, and validation concern. For an addressing problem, the worksheet might focus on hierarchy and summarization. For a WAN problem, it might focus on resilience, site-to-site security, or extranet boundaries. The worksheet forces you to connect evidence to a design decision.
Add a “what changes the answer?” line. Examples include more sites, a new external connection, a need for route separation, an IPv6-only segment, or a failed primary path. This trains you to identify the assumption carrying the decision instead of memorizing a single design as universally correct.
Use diagrams as study artifacts
Draw logical topology, routing boundaries, and service relationships separately before combining them. Label route exchange, summaries, filtering points, VRFs, gateway redundancy, tunnel or VPN edges, and Internet boundaries. Then explain the design aloud or in writing without referring to the original notes.
Keep an error log with categories such as wrong requirement interpretation, incorrect boundary, missed failure mode, unsupported assumption, and weak trade-off explanation. Review the category that appears most often. Repeating the same type of error is a stronger signal than a single difficult practice session.
Time-box decisions, not just reading
The official document describes the 300-320 ARCH exam as a 75-minute assessment containing 60–70 questions. That makes pacing a practical preparation concern, although the supplied facts do not establish the format or difficulty of individual questions. Practice moving from requirement to elimination and decision without spending an entire session perfecting one diagram. [https://learningcontent.cisco.com/documents/exam-topics/300-320-arch.pdf]
Use a two-pass method in practice: make an initial decision when the evidence is sufficient, flag uncertainty in your notes, and return only after completing the remaining set. Afterwards, investigate every uncertain choice. The goal is not to rush; it is to prevent one ambiguous problem from consuming the time needed for better-supported decisions.
Common preparation mistakes and how to correct them
Most weak preparation plans fail through misallocation: they over-focus on familiar commands, ignore design trade-offs, or treat the topic list as a complete and permanent question inventory. Correct those habits by studying every named domain, prioritizing the documented weights, and requiring a written rationale for each architecture choice.
Mistake: memorizing protocol features without a requirement
A feature list does not tell you when a design is appropriate. Correct this by pairing every feature with a requirement, a boundary, and a failure mode. For example, when reviewing route filtering or communities, state which advertisements are controlled, where the policy is applied, and what unintended reachability it prevents.
Mistake: studying only the 22% and 20% domains
Advanced addressing and routing solutions for enterprise networks account for 22% of the documented exam topics, and advanced enterprise campus networks account for 20%; these weights justify prioritization, not omission of the rest. Continue through WAN, IPv6, data-center integration, network security, network services, and the other stated scope areas. [https://learningcontent.cisco.com/documents/exam-topics/300-320-arch.pdf]
Mistake: treating every WAN technology as a product-selection answer
The WAN objectives ask you to compare connectivity options and design for site-to-site VPNs, resilience, extranet connectivity, and Internet-edge connectivity. A technology name alone is not a recommendation. State the requirement first, then identify which service characteristics satisfy it and what dependency or limitation must be accepted.
Mistake: ignoring route boundaries
Many architecture errors are boundary errors: a summary is advertised too broadly, a filter is placed on the wrong relationship, a VRF separation is not preserved, or an external path becomes transit. Mark every control-plane boundary on your diagrams and ask what routes should enter, leave, or remain isolated at that point.
Mistake: trusting an old blueprint as a permanent contract
Cisco says the exam topics are general guidelines, related topics may also appear, and the guidelines may change without notice. Verify the current official outline before booking the assessment and again during the final review. If a third-party resource conflicts with the Cisco source, do not silently treat the third-party wording as authoritative. [https://learningcontent.cisco.com/documents/exam-topics/300-320-arch.pdf]
Mistake: using dumps as a substitute for architecture practice
Copied or allegedly leaked questions cannot establish that you understand a design, and memorization does not guarantee a passing result. Replace them with original requirement scenarios, topology sketches, comparison tables, and an error log. This approach also avoids preparing for questions that may be inaccurate, outdated, or unrelated to the current outline.
Choosing resources and verifying current information
Use the Cisco exam-topics document as the authority for the named scope and documented weights, then use current Cisco learning resources to clarify concepts and check for updates. The supplied Cisco Learning Network Space source describes a digital learning platform for training information, course materials, and exam preparation resources; it is a useful place to investigate available learning material, but it does not replace checking the current exam information. [https://learningspace.cisco.com/]
Before relying on any course or book, map its chapters to the official objectives. A resource may explain routing well while giving little attention to multicampus design, WAN comparison, IPv6 transition choices, or data-center integration. Keep a separate list of objectives not covered by the resource and fill those gaps deliberately.
When using labs, favor small experiments that answer architecture questions: what routes are visible across a boundary, how a summary changes reachability, how a filter affects an advertisement, or how a redundant path behaves after a failure. A lab is valuable when its result informs a design rule; unstructured command repetition is less efficient.
The Learning Network Space material also states that users of Cisco eReader applications need a CCO ID rather than an email address, and it directs recently registered Cisco.com users who do not know that ID to Cisco profile management. Treat account and access instructions as platform-specific details and verify them at the source when you begin using Cisco digital content. [https://learningspace.cisco.com/]
A final review plan before scheduling
Schedule only after you can explain the major architecture decisions without leaning on a single memorized topology. Your final review should confirm the current official outline, expose weak domains, and test whether you can make consistent decisions under the assessment’s stated 75-minute duration and 60–70-question scope. [https://learningcontent.cisco.com/documents/exam-topics/300-320-arch.pdf]
One week before the assessment
Recheck the official 300-320 ARCH topic document for scope changes or revised wording. Review your gap map, prioritizing unresolved objectives rather than rereading everything equally. Rework one addressing and routing design, one campus or multicampus design, one WAN comparison, and one IPv6 transition scenario.
Do not add a large new technology area at the last moment unless the current official outline reveals a genuine gap. Consolidate notes into decision rules, boundary diagrams, and failure analyses. Your final materials should help you distinguish plausible answers, not overwhelm you with command syntax.
The day before
Use a light review of your error log and comparison tables. Confirm the official scheduling and account information through Cisco rather than relying on an old third-party page; the supplied research does not establish additional delivery, language, prerequisite, pricing, or scheduling details. Avoid making a new source your primary study method at this stage.
Prepare a short mental checklist: What is the requirement? Where is the boundary? What must scale? What happens during failure? Which routes or services should be isolated? Which alternative was rejected, and why? These questions help turn broad architecture knowledge into a repeatable decision process.
After each practice set
Review reasoning, not only the selected result. For every missed or uncertain item, identify whether the problem was a protocol knowledge gap, an addressing mistake, an overlooked constraint, a boundary error, or poor time management. Then update the relevant study artifact and solve a new scenario that tests the same decision from a different angle.
What a ready candidate should be able to explain
Readiness means you can connect requirements to architecture across the documented scope. You should be able to defend addressing hierarchy and NAT choices, routing design for IS-IS, EIGRP, OSPF, and BGP, campus availability and convergence decisions, multicampus route control, WAN service selection, and the IPv6 transition approach that fits the stated boundary.
Routing and addressing check
You are ready to move on when you can draw a scalable address structure, identify useful summarization points, discuss efficiency and NAT implications, and explain how routing choices support stability, security, and scale. For BGP, include transit prevention, basic filtering, authentication, communities, basic traffic engineering, and route reflectors in your review rather than studying only the protocol’s basic neighbor relationship.
Campus and multicampus check
You should be able to explain how high availability, first-hop redundancy, device virtualization, Layer 2 scalability, fast convergence, and loop-free design fit together. In a multicampus topology, identify convergence behavior, load-sharing paths, summaries, filters, VRFs, and the topology that best matches the requirements.
WAN and IPv6 check
You should be able to compare the documented WAN options in the context of connectivity, site-to-site VPNs, resilience, extranet access, and Internet-edge design. You should also be able to select overlay tunneling, native dual-stacking, or IPv4/IPv6 translation at boundaries based on the scenario rather than defaulting to the technique you have used most often.
Scope and evidence check
Finally, confirm that your preparation includes the stated enterprise Layer 2 and Layer 3, WAN, data-center integration, network security, and network-services scope. Mark any conclusion that comes from personal preference rather than an explicit requirement, and verify time-sensitive exam information with Cisco before scheduling.
Conclusion
Prepare for 300-320 ARCH as a design-decision assessment: start with the official scope, prioritize advanced addressing and routing solutions for enterprise networks at 22% and advanced enterprise campus networks at 20%, then connect routing, campus, WAN, IPv6, security, services, and integration choices through requirement-based exercises. Verify the current Cisco outline before scheduling, practice within the stated 75-minute and 60–70-question scope, and use an error log to turn uncertain decisions into targeted review. That process gives you a practical next step without depending on unsupported exam claims or memorized question material.
