300-560 NPDEV Exam Guide: Scope, Availability, and Preparation Decisions
Cisco 300-560 was the Network Programmability Developer (NPDEV) exam, designed to assess Python-based network application development, data handling, controller platforms, device APIs, Cisco SDKs, and networking fundamentals. It served candidates building or validating practical network programmability skills rather than studying only traditional device configuration. The most important decision now is whether you can still register for this exam: Cisco’s current exam list does not display 300-560, and Cisco says DevNet certifications moved to the CCNA, CCNP, and CCIE Automation track starting February 3, 2026. Use this guide to confirm availability first, then choose between historical 300-560 preparation and a current automation exam.
Is 300-560 still available?
Treat availability as the first preparation checkpoint, not an administrative detail. Cisco’s current list of available exams does not display 300-560, while Cisco’s certification update says DevNet certifications moved to the CCNA, CCNP, and CCIE Automation track starting February 3, 2026. Confirm the exam code and an active registration path with Cisco or Pearson VUE before buying training or scheduling study time.
The older 300-560 overview identifies Pearson VUE as the registration and delivery provider, but that historical delivery information does not prove that appointments remain open today. An exam page, search result, or third-party listing may preserve old information after an exam has changed status. The official current-exams list and Cisco’s certification update should take priority when deciding whether this is a live examination target.
If you already have an authorization, appointment, or employer requirement tied specifically to 300-560, verify it directly through the official Cisco and Pearson VUE channels. Ask for confirmation of the exact code, the applicable blueprint version, and whether the appointment can still be completed. Do not assume that a previously downloaded blueprint or a practice product establishes current eligibility.
What the historical exam was intended to validate
300-560 assessed whether a candidate could apply software development techniques to network automation tasks. Its scope joined programming fundamentals with network-specific data formats, controllers, APIs, SDKs, and networking concepts. The intended candidate therefore needed more than Python syntax: the candidate had to interpret how code, structured data, protocols, and network platforms work together.
The official scope names programming fundamentals, data handling and formats, network controller platforms and protocols, device programmability, APIs, Cisco SDKs, and networking fundamentals. These areas describe a developer-oriented assessment. A candidate who knows commands by memory but cannot reason about payloads, API responses, authentication, models, or debugging would have a significant preparation gap.
This distinction helps with a practical decision. If your goal is a current Cisco certification, begin with the current Automation-track options rather than assuming 300-560 remains the correct endpoint. If you are preparing for a historical requirement, migration project, archived internal assessment, or an already confirmed appointment, use the 300-560 topics as a skills inventory and validate the applicable version before studying.
What format and language were documented?
Cisco’s historical overview describes 300-560 as a 90-minute assessment containing 65–75 questions, with English listed as the available language. The same overview identifies Pearson VUE as the registration and delivery provider. These details are useful for planning only if Cisco confirms that your specific exam appointment or delivery remains valid.
The documented question range means you should practise switching between short code-reading tasks, structured-data interpretation, API concepts, and platform scenarios rather than spending all preparation time on one long coding exercise. It does not establish a passing score, scoring method, item mix, or the precise order of topics. Cisco has not supplied those details in the provided research, so do not invent them from unofficial practice products.
Do not treat the historical duration as a promise about a current replacement exam. Cisco’s newer Automation-track examinations may have different blueprints, delivery details, languages, or registration rules. Check the current exam page before transferring a 300-560 study schedule to another code.
Which blueprint version applies?
The v1.1 exam-topics PDF states that its version applies to written exams scheduled on June 26, 2018, and later. Cisco’s older v1.0 page recommends that version for candidates scheduled to take the written exam before June 26, 2018. If you have a confirmed historical appointment, match your study material to the appointment date and the official blueprint version rather than mixing documents casually.
Version control matters because Cisco states that exam-topic guidelines may change without notice and that related topics may also appear on a specific exam delivery. A study guide based on a remembered topic list, an old forum post, or a commercial question bank cannot replace the applicable official outline.
For a confirmed historical appointment, save the relevant official PDF and note its version date in your study plan. For a new certification decision, stop using the version question as a scheduling shortcut: first determine whether 300-560 is available at all, then identify the current Automation exam that matches your objective.
How should you read the skill domains?
Prepare by connecting the domains into a development workflow: write or inspect Python, represent information as JSON or XML, use a model or API to reach a controller or device, submit and interpret a request, and verify the resulting network state. This sequence is more useful than memorizing isolated product names because it exposes the relationships the exam was designed to test.
The blueprint does not provide verified percentage weights in the supplied research. Do not assign personal importance to bare percentages or repeat unlabelled weight claims from third-party sites. Instead, use the named domains as a checklist and allocate time according to your demonstrated weaknesses, the official topic list, and any confirmed exam version.
A productive diagnostic is to take one small task from each area without looking up the answer. For example, read a Python function, parse a JSON response, identify a YANG-to-RESTCONF relationship, explain a controller concept, select an appropriate device API, and troubleshoot a networking assumption. Record whether the problem was syntax, data representation, protocol behavior, platform knowledge, or basic networking. That classification should drive the next study block.
Programming fundamentals
The programming-fundamentals domain includes constructing, interpreting, and debugging Python code, including code that uses JSON, XML, requests, and ncclient. Study for comprehension as well as construction: be able to trace variables, recognize data types, identify malformed logic, and explain why a request or NETCONF operation produces a particular result.
Build short exercises instead of one large application. Write a function that accepts structured input, validates a required field, sends a request through an appropriate library pattern, and handles an unsuccessful response. Then alter one assumption at a time and debug it. Practise reading code you did not write, because interpretation and debugging are explicitly part of the domain.
Common mistakes include confusing a Python dictionary with a JSON document, overlooking string-versus-list behavior, failing to inspect an exception, and treating an HTTP response as proof that the intended configuration was applied. Keep the code small enough that you can explain every line and every returned object.
Data handling and formats
The data-handling domain covers constructing and parsing JSON or XML payloads, manipulating network entries, validating YANG models, and translating YANG models into RESTCONF URI and JSON representations. The preparation target is accurate movement between representations, not superficial familiarity with braces, tags, or field names.
Use a repeatable exercise: start with a network intent, express it as JSON or XML, identify the relevant model path, derive the RESTCONF resource location, and inspect the response for namespace, hierarchy, and value errors. Compare the intended object with the returned object. This exposes whether the problem is a payload shape, URI path, namespace, datatype, or device capability issue.
A frequent pitfall is copying a payload without understanding its model. YANG determines structure and meaning; a syntactically valid JSON document can still be unsuitable for a particular modeled resource. Another mistake is treating XML and JSON as interchangeable text formats without checking how lists, namespaces, containers, leaves, and operational responses are represented.
Controller platforms and protocols
The controller-platform domain includes ACI policy models, ACI application profiles, APIC-EM services and its Network Information Database, service tickets, OpenFlow, OpFlex, rollback procedures, and resource utilization. Study these as control and policy concepts: identify the platform role, the object or service being manipulated, the protocol or interface involved, and the expected operational consequence.
Create comparison notes with one row per concept and columns for purpose, data or policy object, interaction method, and failure or rollback consideration. This prevents a common error—remembering a product label while losing the relationship between policy, controller state, and device behavior.
Do not reduce controller study to endpoint memorization. Work through scenarios such as selecting a service, interpreting a ticket-related workflow, distinguishing a policy model from an application profile, or deciding why rollback and resource utilization matter. The answer should be justified by the controller’s function, not by a memorized acronym alone.
Device programmability and ASA API work
The device-programmability domain covers NX-OS API, ASA API, and IOS XE/XR, including configuration deployment through RESTCONF and NETCONF. The blueprint also includes ASA network objects, access lists, security groups, and requests that combine multiple ASA REST operations in one POST. Prepare to distinguish platform-specific behavior from general API habits.
Build a device matrix for NX-OS, ASA, and IOS XE/XR. For each platform, record the relevant API or protocol, the kind of configuration or state it exposes, the data representation involved, and how you would verify success. Keep separate notes for ASA objects, access lists, and security groups so that their purposes do not blur together.
For ASA-focused practice, reason about an operation that combines several REST actions in one POST. Ask what each action changes, how dependencies affect ordering, what a partial failure could mean, and how you would inspect the response. Do not assume that an API request is safe merely because it is syntactically correct or bundled into one call.
APIs, SDKs, and networking fundamentals
The API and SDK portion should be studied alongside networking fundamentals, not after them. A developer must understand addressing, transport behavior, authentication context, request and response semantics, and the device or controller’s role before a Cisco SDK abstraction becomes meaningful.
For every API exercise, write down the target, resource, method or operation, authentication requirement, input representation, expected response, and verification step. Then explain which part would change if the target platform changed. This turns a memorized example into a transferable troubleshooting method.
Refresh the networking concepts needed to interpret automation failures: addressing and reachability, transport connections, device roles, configuration versus operational state, and the difference between a successful connection and a successful network change. The official research does not provide a detailed subtopic list for every networking item, so use the published blueprint as the boundary and avoid inventing a more precise weighting or syllabus.
Which lab platforms are worth comparing?
Cisco lists VIRL, APIC Simulator, NX-OSv, DevNet sandboxes, ASAv, and CSR1000v as virtual platforms to compare for testing network applications. Choose a platform based on the skill you need to observe, its availability to you, and whether it represents the API behavior you are trying to practise; do not collect environments merely to increase lab count.
A sensible sequence is to begin with a general Python and data-handling exercise, then use a reachable platform to test API or model interactions, and finally compare how the workflow changes across device or controller types. Keep a lab record containing the request, payload, response, resulting state, and error encountered. That record becomes a revision tool and exposes repeated misunderstandings.
Availability and behavior can vary by sandbox, simulator, software release, and account arrangement. Treat lab output as evidence for the environment you used, not as proof that every Cisco platform behaves identically. When a task depends on a product-specific feature, return to the official topic list and relevant product documentation rather than generalizing from one lab.
A study roadmap that produces evidence
Use a staged plan with a diagnostic, focused skill blocks, integrated practice, and a final decision checkpoint. The purpose is not to complete a calendar for its own sake; it is to produce evidence that you can explain code, data, APIs, and network outcomes without relying on recalled answers.
Stage one: establish the target. Confirm whether 300-560 can still be scheduled, identify the official blueprint version for any valid appointment, and list your prior Python, networking, and Cisco platform experience. If there is no current registration path, decide whether your objective is historical knowledge or a current Automation-track certification.
Stage two: diagnose fundamentals. Work through small Python, JSON, XML, and networking tasks without a question bank. Mark each error by cause. If you cannot explain a failing request, pause API study and repair the underlying programming or data-handling gap rather than adding more product notes.
Stage three: build the core skills. Alternate Python debugging with structured-data translation. Practise requests and ncclient in controlled examples, then explain what the server, controller, or device should do. Add YANG and RESTCONF exercises only after you can reliably inspect inputs and outputs.
Stage four: integrate platforms. Compare controller concepts with device programmability. Use the listed virtual-platform options where accessible, and connect each lab to an explicit objective such as an API request, configuration deployment, model translation, response parsing, or rollback reasoning. Record failures as carefully as successful results.
Stage five: simulate decision-making. Use original tasks and official topic headings, not leaked questions or memorized answer sets. Mix code interpretation, data conversion, controller scenarios, device APIs, and networking reasoning. After each task, explain why the selected approach works and what evidence would disprove it.
Stage six: review and verify. Revisit only the error categories that remain weak, check the official status again, and confirm the exam code, language, provider, and blueprint version for any appointment. If the target has moved to a current Automation exam, rebuild the roadmap around that exam’s official blueprint instead of assuming that 300-560 coverage transfers completely.
What preparation mistakes waste the most time?
The costliest mistake is studying before confirming that the exam is a live scheduling option. The next is treating a dump or recalled answer set as preparation. Such material cannot establish current availability, may reflect a different blueprint, and encourages recognition without the ability to construct, debug, or verify a real automation workflow.
Avoid studying every technology at the same depth. Use your diagnostic to identify whether your limitation is Python, structured data, modeled interfaces, controller concepts, platform-specific APIs, or networking. Then cycle back through integration tasks so that improvement in one domain does not remain isolated.
Do not memorize payloads without their model and endpoint context. Do not assume similar API names imply identical behavior across NX-OS, ASA, and IOS XE/XR. Do not declare success because a request returned a response; inspect the response and verify the intended state. Finally, do not rely on an old version label without matching it to the appointment date and official guidance.
How should you use practice questions safely?
Use practice questions to expose reasoning gaps, not to predict live items. The official topic guidance says related topics may also appear on a specific delivery, and Cisco warns that exam-topic guidelines may change without notice. A reliable practice routine therefore explains the answer, tests a variation, and verifies the underlying concept in an official source or controlled lab.
After answering a question, write a short justification containing the domain, the relevant object or protocol, the expected behavior, and the evidence that would confirm it. For a code item, trace the data and failure path. For an API item, identify the resource and representation. For a controller item, explain the policy or service relationship. If you cannot justify the answer, classify it as unresolved rather than marking it learned.
Reject any resource claiming that memorization guarantees a pass or offering leaked exam content. Apart from violating fair testing expectations, those materials are particularly risky for an exam whose topics and availability may have changed. Build competence that remains useful for current automation work even if 300-560 is no longer schedulable.
What should you do before scheduling or switching exams?
Make the final decision from current official information. First check Cisco’s current exam list and certification update. If 300-560 is absent and no official registration path is confirmed, stop treating it as a normal upcoming exam and investigate the applicable CCNA, CCNP, or CCIE Automation route. If Cisco or Pearson VUE confirms a historical appointment, retain that confirmation and use the matching blueprint.
Before committing, write down the exact exam code, blueprint version, delivery provider, language, and the skills you still need to practise. The supplied official overview documents English for 300-560 and Pearson VUE as the provider, but current replacement exams must be checked independently. Do not carry those historical details across to a different exam without evidence.
Your next action should be one of two things: verify and prepare for a confirmed 300-560 appointment, or select a current Automation-track exam and restart the scope review from its official blueprint. Either route is better than paying for obsolete material or measuring readiness against an exam that may no longer be available.
Conclusion
300-560 remains useful as a map of network-programmability skills: Python debugging, JSON and XML handling, YANG and RESTCONF translation, controller concepts, device APIs, Cisco SDKs, and networking fundamentals. Its historical overview documents a 90-minute, 65–75-question English assessment delivered through Pearson VUE, but Cisco’s current information changes the scheduling decision: 300-560 is not shown on the current exam list, and DevNet certifications moved to the Automation track starting February 3, 2026. Verify status first, then prepare against the correct official blueprint and use labs to prove that you can explain and validate automation behavior.
Related exams
- 500-210 exam — SP Optical Technology Field Engineer Representative
- 650-059 exam — Cisco Lifecycle Services Advanced Routing and Switching (LCSARS)
