Designing Cisco Network Service Architectures 300-320 ARCH Exam Guide
The 300-320 ARCH exam validates design judgment across enterprise Layer 2 and Layer 3 infrastructure, WAN technologies, data-center integration, network security, and network services. Cisco associates it with the Cisco Certified Design Professional certification. This guide is for network professionals who must decide whether their current knowledge is ready for an architecture-focused assessment or whether they need a structured study period first. It explains the documented scope, turns the objectives into practical study tasks, and helps you choose what to review before scheduling through official Cisco channels.
What the 300-320 ARCH exam is designed to validate
The exam is intended to test whether you can select and shape scalable, resilient, secure network designs rather than merely recall isolated commands. Cisco identifies Designing Cisco Network Service Architectures as the ARCH exam numbered 300-320 and associates it with the Cisco Certified Design Professional certification.
The documented scope spans enterprise Layer 2 and Layer 3 infrastructures, WAN technologies, data-center integration, network security, and network services. That breadth changes the preparation task: you need to connect addressing, routing, campus, WAN, and service decisions into a coherent architecture.
Treat the official topic document as the controlling study boundary, not as a promise that every question will reproduce a heading from the document. 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 material again before booking the exam.
Who should use this guide before scheduling
This guide best fits candidates who already work with enterprise network design or who are deliberately building that capability. It is particularly useful if you can explain why a design uses a particular routing boundary, WAN model, campus availability mechanism, or IPv6 transition approach—not just how to configure one device.
A practical readiness decision is whether you can start with business and technical constraints, identify competing design options, and defend a selection. If your study has so far been command-led, schedule more design practice before scheduling the exam itself.
Do not treat a certification title as proof that every prerequisite has been met. The supplied Cisco research identifies the certification association and exam scope, but it does not establish a prerequisite, required work experience, language list, delivery method, or current registration policy. Verify those items in the current official exam information before making a booking decision.
What the documented blueprint prioritizes
The clearest documented emphasis is advanced addressing and routing solutions for enterprise networks, which account for 22% of the documented exam topics. Advanced enterprise campus networks account for 20% of the documented exam topics. Use those labeled domains to set study priority, while still covering the remaining published scope.
The 22% advanced addressing and routing solutions for enterprise networks domain includes structured addressing that facilitates summarization, with attention to hierarchy, efficiency, scalability, and NAT. Its routing objectives cover stable, secure, and scalable designs for IS-IS, EIGRP, OSPF, and BGP.
The BGP objectives specifically include transit prevention, basic route filtering, authentication, communities, basic traffic engineering, and route reflectors. Study these as design controls with a purpose: for example, explain how a route-reflector choice affects scale, or how filtering and transit prevention protect the intended routing policy.
The 20% advanced enterprise campus networks domain includes high availability, first-hop redundancy protocols, device virtualization, Layer 2 scalability, fast convergence, and loop-free technologies. The multicampus Layer 3 objectives add convergence, load sharing, route summarization, route filtering, VRFs, and optimal topologies.
The source does not provide a complete set of percentage allocations in the supplied research. Do not invent weights for WAN, IPv6, data-center integration, security, or network services. Instead, use the full objective document to make sure that the two documented percentages do not cause you to neglect the other domains.
How to turn addressing and routing objectives into design practice
Begin with an addressing exercise that forces hierarchy and summarization decisions. Draw a regional or campus structure, allocate address blocks by function and location, and identify where summarization can reduce routing information without hiding a required path. Then review efficiency, future growth, and NAT implications.
A good study output is not a list of subnet calculations. It is a short design record that states the allocation model, summarization points, exceptions, and expected operational trade-offs. Mark every exception explicitly; an unplanned exception is often evidence that the hierarchy is not doing enough work.
For each of IS-IS, EIGRP, OSPF, and BGP, compare the design problem the protocol is solving. Ask how the proposed architecture supports stability, security, and scale. Concentrate on boundaries, policy, failure behavior, and information movement rather than memorizing configuration syntax.
For BGP, build a decision table with the documented objectives as rows: transit prevention, route filtering, authentication, communities, basic traffic engineering, and route reflectors. In each row, record the design intent, the risk being controlled, and the evidence you would seek before approving the choice.
Include IPv6 as a selection problem. The documented objective asks candidates to choose among overlay tunneling, native dual-stacking, and IPv4/IPv6 translation at boundaries. Practice stating the conditions that would favor each approach, the dependencies it introduces, and the operational burden it leaves behind.
How to study campus and multicampus architecture
Study campus design by tracing availability and convergence from the user edge toward the Layer 3 core. You should be able to explain how first-hop redundancy, device virtualization, Layer 2 scalability, loop-free technologies, and fast convergence interact rather than treating them as unrelated features.
Create a campus diagram with at least an access layer, aggregation or distribution function, and core or interconnection role. Label failure domains, gateway placement, Layer 2 extension boundaries, and the expected traffic path. Then remove a link or device and describe what should happen, what should remain reachable, and where convergence is expected.
For multicampus Layer 3 work, practice comparing topologies rather than drawing a single preferred answer. Include convergence, load sharing, route summarization, route filtering, VRFs, and optimal topologies in your review. For every design, state what is shared, what is isolated, and where policy is enforced.
A common mistake is to optimize for redundancy without defining the failure being addressed. Two paths are not automatically useful if they create loops, asymmetric behavior that the services cannot tolerate, or an unclear troubleshooting boundary. Add a failure analysis to each practice design and connect it to the stated business requirement.
How to organize WAN and security preparation
The WAN objectives require comparison and selection, not just recognition of technology names. The documented technologies include DMVPN, Layer 2 VPN, MPLS Layer 3 VPN, IPsec, GRE, private lines, and GETVPN; the WAN section also covers site-to-site VPNs, resilient WAN strategies, extranet connectivity, and Internet-edge connectivity.
Build a comparison matrix for the WAN technologies named by Cisco. Use columns such as transport assumption, segmentation model, encryption role, scalability concern, failure behavior, and operational dependency. Keep the matrix tied to design decisions instead of turning it into a catalog of definitions.
Practice from requirements: branch count, connectivity pattern, trust boundaries, resilience needs, Internet exposure, and interconnection with partners or external environments. Then select a design and document why alternatives were rejected. This is more valuable than memorizing which acronym appears next to which feature.
Include a security review in every WAN exercise. Ask where authentication, encryption, filtering, and trust boundaries belong; how an extranet differs from an internal connection; and how Internet-edge connectivity changes the design assumptions. The supplied research confirms these topic areas but does not provide a separate security percentage, so do not assign one.
Avoid a technology-first mistake: choosing MPLS, IPsec, GRE, DMVPN, or another option before clarifying the connectivity and security requirement. The objective is to compare options and design resilient connectivity, so your notes should show the requirement-to-architecture chain.
How to connect data-center and network-service topics
The stated scope includes data-center integration, network security, and network services alongside enterprise infrastructure and WAN design. Prepare to explain how these areas affect the surrounding architecture, even though the supplied facts do not provide individual weightings or a detailed list of every sub-objective.
Use an integration map rather than studying these subjects in isolation. Place campus, WAN, data-center, Internet-edge, and service locations on one logical diagram. Mark routing domains, security boundaries, segmentation points, and dependencies such as address translation or shared services.
For each service or integration point in your study material, ask four questions: what consumes it, where should it reside, how is it reached, and what happens during a path or site failure? These questions turn a vocabulary review into a design review without assuming that the real exam uses any particular scenario format.
Keep the source boundary clear. The official research supports the broad scope, but it does not verify particular data-center products, service implementations, question styles, or configuration tasks. Use current Cisco learning content to fill in details rather than presenting an unsupported product list as exam requirements.
What the exam timing means for your preparation
Cisco describes the 300-320 ARCH exam as a 75-minute assessment containing 60–70 questions. That combination requires disciplined reading and a decision process that prevents one difficult architecture problem from consuming the session.
Use timed practice only after you understand the domains. In an early phase, pause and justify every answer. Later, work in short timed blocks, record where you hesitated, and classify the cause: missing technical knowledge, misread requirement, weak elimination, or poor time control.
A useful decision routine is: identify the required outcome, list the explicit constraints, eliminate options that violate them, then compare the remaining designs for scale, resilience, security, and operational clarity. This keeps you from selecting the most familiar technology before understanding the question.
Do not infer an unverified passing score, question format, language, delivery method, or testing-center policy from the timing and question range. Those details are not established in the supplied research. Confirm current logistics through Cisco before scheduling and use the official registration information as the final authority.
A practical six-phase study roadmap
A staged plan works better than reading every technology in sequence. First establish the blueprint and your gaps, then build design artifacts, connect the domains, and finish with timed decisions. Adjust the pace to your available study time rather than treating the phases as a guaranteed calendar.
Phase one: baseline and scope. Read the current official exam topics and create a checklist for addressing, routing, campus, multicampus, WAN, IPv6, data-center integration, security, and network services. Rate each objective as explain, design, or not yet understood. Use the weakest design-critical areas to set the first study block.
Phase two: addressing and routing. Produce an addressing hierarchy, summarization plan, and NAT decision record. Review IS-IS, EIGRP, OSPF, and BGP through stability, security, and scalability outcomes. Add the BGP control table and a separate IPv6 choice analysis covering overlay tunneling, native dual-stacking, and translation at boundaries.
Phase three: campus and multicampus. Draw a resilient campus, label first-hop redundancy and Layer 2 boundaries, and test link and device failures on paper. Follow with multicampus topologies that demonstrate convergence, load sharing, summarization, filtering, VRFs, and an explicit rationale for the chosen topology.
Phase four: WAN and integration. Compare the documented WAN technologies against realistic requirements, then add VPN, extranet, Internet-edge, data-center, and security considerations. Review whether the design introduces unnecessary complexity or unclear ownership at a boundary.
Phase five: integrated design reviews. Give yourself a requirement set and produce a one-page architecture. Defend addressing, routing, campus, WAN, IPv6, segmentation, and resilience choices. Have a peer challenge assumptions if possible, but do not rely on leaked or recalled exam material; use legitimate Cisco learning content and your own design reasoning.
Phase six: readiness check. Revisit every missed decision and rewrite the rationale in plain language. Complete timed practice only when you can explain the relevant objective. Schedule only after you have verified current exam logistics and can consistently make defensible choices across the full scope, not merely the highest documented domains.
How to use official Cisco learning resources
Use the Cisco exam-topics document as your scope anchor and Cisco Learning Network Space as a source of learning materials and preparation resources. The supplied Learning Space information describes a digital learning platform with training information, course materials, and exam preparation resources.
Start with the exam-topics PDF, convert its objectives into study tasks, and then locate learning content for the specific task you cannot explain. Keep notes organized by design question—such as scale, failure domain, policy, or migration choice—rather than by product name alone.
Learning Space information supplied for this guide also states that recently registered Cisco.com users who do not know their CCO ID can find it under Username in the Cisco.Com Profile Management page. This is an account-access detail, not evidence about exam eligibility or delivery, so handle it separately from technical preparation.
Because Cisco says the topic guidelines may change without notice, save the official link and review it again near registration. A study plan built from an old blueprint can leave gaps even when the underlying technologies remain familiar.
Mistakes that waste preparation time
The most expensive study mistakes are usually planning mistakes: treating the blueprint as a command list, studying only the two weighted domains, and confusing recognition with design judgment. Correct those habits by producing and reviewing architecture decisions with explicit constraints and trade-offs.
Mistake one is memorizing protocol features without defining the failure or scale problem they solve. Replace feature lists with comparison tables and failure exercises. For every major choice, write what improves, what becomes more complex, and what assumption could invalidate the design.
Mistake two is ignoring addressing until the end. Addressing hierarchy affects summarization, routing scale, segmentation, and future growth. Design the address plan early, then reuse it in campus, multicampus, WAN, and IPv6 exercises.
Mistake three is selecting a WAN technology from familiarity. Start with connectivity, resilience, trust, and operational requirements. Only then compare DMVPN, Layer 2 VPN, MPLS Layer 3 VPN, IPsec, GRE, private lines, and GETVPN as possible answers.
Mistake four is using exam dumps or leaked questions as a preparation strategy. They cannot establish genuine design competence, may be inaccurate or unauthorized, and do not guarantee a passing result. Use official objectives, legitimate learning resources, and original practice designs instead.
Mistake five is booking from an outdated assumption about logistics. The supplied facts verify the question range and assessment time, but not all current registration details. Confirm the live Cisco information before paying, selecting a delivery option, or planning time away from work.
Your final readiness checklist
You are closer to scheduling when you can explain an architecture from requirements to trade-offs, not simply name the technologies in the blueprint. Use the checklist below to identify the last gap and make the next action specific.
Confirm that you can create a hierarchical address plan that supports summarization and discuss efficiency, scalability, and NAT. Confirm that you can compare IS-IS, EIGRP, OSPF, and BGP design choices for stable, secure, and scalable outcomes.
Confirm that you can explain BGP transit prevention, basic filtering, authentication, communities, basic traffic engineering, and route reflectors in design terms. Confirm that you can choose an IPv6 transition approach among overlay tunneling, native dual-stacking, and translation at boundaries when requirements change.
Confirm that your campus designs address high availability, first-hop redundancy, device virtualization, Layer 2 scalability, fast convergence, and loop-free operation. Confirm that your multicampus designs address convergence, load sharing, summarization, filtering, VRFs, and topology selection.
Confirm that you can compare the documented WAN options and design site-to-site VPNs, resilient WAN strategies, extranet connectivity, and Internet-edge connectivity. Then connect those decisions to data-center integration, security boundaries, and network services.
Finally, reread the current official topics and verify registration details. If one objective remains a vocabulary-only topic, convert it into a one-page design explanation before scheduling. If several objectives remain uncertain, extend preparation instead of trying to compensate with memorization.
What to do next
Your next step should be an evidence-based gap review: open the official 300-320 ARCH topics, mark each objective by confidence, and choose one design artifact to complete first. That gives you a concrete starting point without assuming that an old blueprint or unofficial question source represents the current assessment.
Download or review the official exam-topics document, build the domain checklist, and begin with the documented addressing and routing emphasis. Use Cisco Learning Network Space for available learning materials, then return to the checklist to test whether you can apply the concepts in an integrated design.
Before registration, verify current Cisco information for any detail not established here, including prerequisites, availability, language, delivery, registration procedure, and policies. After registration, use the confirmed appointment information to refine your timed practice and final review rather than relying on generic scheduling assumptions.
Conclusion
The 300-320 ARCH exam calls for architecture reasoning across routing, addressing, campus, WAN, IPv6, integration, security, and services. The strongest preparation is to turn each objective into a design decision, test it against scale and failure, and explain the trade-off clearly. Use the official Cisco topic document as the boundary, Cisco learning resources as the study source, and current Cisco registration information for logistics. Once your gap review shows repeatable competence across the full scope, scheduling becomes a practical decision rather than a guess.
