300-915
Developing Solutions Using Cisco IoT and Edge Platforms (DEVIOT)
Developing Solutions Using Cisco IoT and Edge Platforms (DEVIOT) Exam Guide
DEVIOT 300-915 validated knowledge of IoT application development across Cisco edge-compute and network architecture, including Cisco IOx, Cisco EFM, data visualization, and security methods. It was associated with the Cisco Certified DevNet Professional and Cisco Certified DevNet Specialist—IoT certifications. The most important decision for a reader today is scheduling: Cisco classifies DEVIOT as End of Life/Retired and states that the last day to take it was January 20, 2024. Use this guide as a blueprint-based study reference, not as confirmation that a new booking is available.
Can you still schedule DEVIOT 300-915?
No. Cisco’s DevNet v1.1 release notes classify DEVIOT 300-915 as End of Life/Retired, and Cisco states that January 20, 2024 was the last day to take the exam. A candidate should therefore verify any current Cisco certification requirements before investing in DEVIOT-specific preparation or attempting to book it.
This status changes the purpose of preparation. The material remains useful for understanding Cisco IoT application development and for reviewing the skills represented by the historical blueprint, but it should not be treated as a currently available exam pathway. The official Cisco pages linked in this guide are the appropriate places to check for any replacement or revised certification information.
Do not rely on an old practice-test listing, an archived booking page, or a third-party course title as evidence that DEVIOT has returned. Those resources may describe the former exam accurately while still being unsuitable for a current scheduling decision.
What did the exam validate?
DEVIOT evaluated IoT application-development knowledge as it applied to Cisco IoT edge compute and network architecture. The subject areas included Cisco IOx, Cisco EFM, IoT data visualization, and security methods. That combination made the exam broader than a narrow programming test: candidates had to connect application behavior with devices, networks, deployment locations, and operational safeguards.
The blueprint emphasized applied decisions. A candidate needed to reason about how a sensor connects through an IoT topology, where processing should occur, how an application reaches an edge platform, and how data can be exposed or visualized. Studying isolated product definitions would not address the full intent of these tasks.
Cisco associated DEVIOT with the Cisco Certified DevNet Professional and Cisco Certified DevNet Specialist—IoT certifications. Because the exam is retired, treat those associations as historical context and confirm current certification structures directly with Cisco rather than assuming that passing or preparing for DEVIOT now creates a new credential.
Which blueprint domains deserve the most attention?
The published blueprint gives Cisco Network IoT Architecture 20% and Compute and Analysis 10%; the remainder should be studied through the named subject areas and task statements rather than guessed percentages. Keep each percentage attached to its official domain name, because a bare percentage can easily be mistaken for a different domain or a current exam weighting.
Cisco Network IoT Architecture accounts for 20% of the exam blueprint. Its scope includes interpreting topology and data flow through gateways, access points, firewalls, routers, and switches. It also includes PLCs, embedded microcontrollers, RTOS systems, Cisco interfaces, communication protocols, and communication standards.
Compute and Analysis accounts for 10% of the exam blueprint. Cisco describes this domain as comparing edge devices with generic compute devices and selecting cloud or edge deployment for an application scenario. The decision is architectural: the candidate must connect application needs to an appropriate execution location and device type.
The blueprint also requires constructing a workflow for connecting a sensor and troubleshooting sensor-connectivity issues. It includes constructing a Python script to deploy an application at the edge using FND and GMM APIs. These task statements are more useful for study planning than memorizing product names because they indicate what the candidate was expected to do with the knowledge.
The Cisco exam-topics document also identifies Cisco IOx, Cisco EFM, IoT data visualization, and security methods as subject areas. Use those labels to organize notes, then connect each one to a flow: device or sensor, network path, edge or cloud processing, application deployment, data presentation, and security control.
How should you study the architecture before the code?
Start with a system diagram, not an API reference. Draw a sensor, the local control or embedded layer, the network devices that carry its traffic, the edge compute location, the cloud or remote service, and the visualization destination. Then explain the direction and purpose of each data flow in plain language.
For the network portion, practise identifying the role of each component in a topology rather than treating gateways, access points, firewalls, routers, and switches as interchangeable labels. Ask what traffic each device handles, where a boundary exists, and what failure would look like if that component were unavailable.
Add PLCs, embedded microcontrollers, and RTOS systems to the device side of the diagram. Record which interface or communication protocol connects each layer. The goal is not to create an unverified catalogue of every supported technology; it is to become comfortable tracing a realistic industrial or operational data path using the categories named by Cisco.
For every topology exercise, write two explanations: a normal-flow explanation and a fault explanation. In the fault explanation, identify the first observable symptom, the layer where it originates, and the next diagnostic check. This habit prepares you for the blueprint’s explicit requirement to troubleshoot sensor connectivity without depending on recalled exam questions.
How should you practise edge-versus-cloud decisions?
Choose the deployment location from the application scenario’s constraints rather than from a blanket preference for edge or cloud. Compare the need for local processing, the available compute device, connectivity assumptions, response requirements, data movement, and operational boundaries. Cisco’s Compute and Analysis domain specifically tests selecting cloud or edge deployment for an application scenario.
Use a decision table with two columns headed edge and cloud. For each scenario, write what must happen locally, what can be transmitted, what happens during a network interruption, and what resource the application needs. Then state the trade-off in one sentence. This is a practical study technique, not an additional Cisco requirement.
Compare an edge device with a generic compute device by considering its position in the topology and its relationship to the connected equipment. Avoid treating “edge” as merely a smaller server or “cloud” as automatically superior. The exam objective is the suitability of the deployment choice for the stated application scenario.
A common mistake is to select a platform before identifying the workload. Reverse that order: define the workload, identify its timing and connectivity needs, locate the data source, and only then select the likely execution location. Keep the reasoning visible in your notes so you can audit a conclusion instead of memorizing it.
What Python and API practice is relevant?
The historical blueprint includes constructing a Python script to deploy an application at the edge using FND and GMM APIs. Preparation should therefore focus on the structure of an automation workflow: gather inputs, authenticate as required by the platform, identify the target, submit the deployment action, inspect the response, and handle an unsuccessful result.
Build a small study script in stages. First write the data structure for the application and target. Next add request construction and response handling. Then add validation for missing inputs and a clear error path. Finally, annotate which part of the workflow identifies the edge target and which part initiates deployment. This sequence tests understanding without relying on live exam content.
Keep API names and workflow steps separate in your notes. A candidate may recognize an API label but still fail to understand what information the call needs, what object it acts on, or what evidence confirms completion. For each FND or GMM operation you study, record its purpose, inputs, expected result, and a likely failure condition only when the official technical documentation supports those details.
Do not turn the exercise into a memorization contest. Reconstruct the workflow from the scenario: what is being deployed, where it belongs, what service manages the action, and how the script should respond if the target or request is invalid.
How do you prepare for sensor-connectivity troubleshooting?
Treat sensor troubleshooting as a layered workflow. Begin at the sensor and move outward through its interface, embedded or control system, gateway or access point, network path, edge application, and data destination. At each layer, identify what should be observable and what test would distinguish a local fault from a transport or application fault.
Create troubleshooting cards with four fields: symptom, suspected layer, confirming check, and corrective direction. Examples of symptoms can remain generic—no data, intermittent data, or data that arrives in the wrong form—while the checks should refer to the architecture you drew. This keeps practice focused on diagnosis rather than imagined exam questions.
The blueprint’s wording calls for constructing a workflow for connecting a sensor and troubleshooting sensor-connectivity issues. Practise producing the workflow from a blank page. Include the sensor connection, the path through the relevant network elements, the edge application, and the point at which data is consumed or visualized.
Avoid jumping straight to application code when the symptom is absence of data. First establish whether the sensor produces data, whether the next interface receives it, whether the network path carries it, and whether the edge application processes it. This ordering reduces random changes and creates a defensible troubleshooting record.
How should IOx, EFM, visualization, and security fit together?
Study these topics as parts of one solution lifecycle. Cisco identifies Cisco IOx, Cisco EFM, IoT data visualization, and security methods among the DEVIOT subject areas. Organize notes around how an application is hosted or connected, how device data is handled, how users interpret that data, and how the solution is protected.
For Cisco IOx, focus your historical blueprint review on the relationship between the edge-hosted application and the device or network environment around it. Link the platform to the deployment workflow rather than learning the name without a role. Your notes should answer: what is deployed, where it runs, what it consumes, and how it participates in the larger topology.
For Cisco EFM, place the technology in the data and device-management story supported by your source material. Avoid inventing implementation details from memory or from unrelated Cisco products. If a study resource makes a specific claim, verify it against Cisco documentation before using it as a fact.
For visualization, trace the data from its source to the view that a user or operator needs. For security, identify the assets, interfaces, communications, and deployment actions that need protection. The official topic list establishes these as subject areas; the exact security implementation should be learned from current, authoritative technical documentation rather than assumed from a generic security checklist.
What delivery details were published for DEVIOT?
Cisco identified DEVIOT as exam 300-915, Developing Solutions Using Cisco IoT and Edge Platforms v1.0. The historical overview listed a 90-minute duration and English as the available exam language. Those details describe the retired exam and should not be interpreted as evidence of current delivery or booking availability.
Cisco listed February 24, 2020 as the first date to test for DEVIOT. It also states that January 20, 2024 was the last day to take the exam. The latter fact is the scheduling detail that matters for present-day decisions.
Because the exam is retired, do not plan around an assumed delivery method, current appointment inventory, current price, passing score, question count, or rescheduling policy. No such details should be inferred from older pages or from another Cisco exam. Verify any current replacement pathway through Cisco’s current certification information.
What study materials should you trust?
Use the Cisco exam-topics page and the official DEVIOT exam overview as the primary historical references for scope and published delivery details. Use Cisco’s exam-topics PDF for the named subject areas, and use Cisco DevNet technical material to deepen understanding of IOx-related application development. Check the publication status of each resource before treating it as current guidance.
A useful evidence hierarchy is: current Cisco certification information for scheduling, the official blueprint for historical objectives, Cisco technical documentation for product behavior, and third-party explanations for additional practice only after verification. A third-party question bank should never override a Cisco source or be treated as a substitute for building the workflows described in the blueprint.
Cisco’s IOx Interoperability Verification Testing page explains that its testing program tests IOx-hosted applications for security vulnerabilities and network friendliness, and says tested applications help reduce integration costs, accelerate deployments, and reduce risk of failure. This is useful context for understanding why application validation and operational behavior matter, but it is not a DEVIOT exam requirement or a promise about exam performance.
Do not use leaked questions, exam dumps, or memorization claims as a preparation strategy. They cannot establish current exam availability, do not teach the architecture, and do not replace the ability to reason through a topology, deployment choice, or troubleshooting workflow.
What is a practical preparation roadmap?
For historical study or skills development, use a four-stage roadmap: establish the architecture, practise deployment decisions, build the automation workflow, and integrate troubleshooting with visualization and security. At the end, produce a complete solution explanation from sensor to user-facing data. Since DEVIOT is retired, the final action is not booking; it is confirming which current Cisco learning or certification objective should replace it.
Stage one: map the architecture. Read the official topic statements and create a glossary for gateways, access points, firewalls, routers, switches, PLCs, embedded microcontrollers, RTOS systems, interfaces, protocols, and standards. Draw at least one end-to-end topology and annotate data direction, processing location, and likely fault boundaries.
Stage two: practise deployment analysis. For several application scenarios, compare edge and cloud placement and compare an edge device with a generic compute device. Write the decision and its reason. Mark any assumption that comes from your own recommendation rather than from Cisco’s blueprint.
Stage three: reconstruct the Python workflow. Study the FND and GMM API roles from authoritative Cisco material, then write a deployment script structure with input validation, target selection, request handling, and failure reporting. The purpose is to demonstrate the workflow, not to reproduce a memorized code sample.
Stage four: integrate the solution. Start with a sensor, construct its connection workflow, trace the topology, select edge or cloud processing, deploy the application conceptually, describe how data is visualized, and identify security considerations. Finish by diagnosing a deliberately broken link in the path. This sequence reveals whether you understand relationships between domains.
At the end of each stage, keep a short gap list. Separate “I do not know the concept,” “I cannot explain the data flow,” and “I cannot implement the workflow.” Each problem requires a different next action: read, diagram, or code.
Which mistakes waste the most preparation time?
The largest mistake is preparing as if DEVIOT were still schedulable. Confirm status before buying a course, reserving study time for a booking deadline, or treating a historical exam overview as a current offer. The second is studying product names without practising the decisions and workflows explicitly described by the blueprint.
Another mistake is treating the 20% Cisco Network IoT Architecture domain and the 10% Compute and Analysis domain as interchangeable indicators of overall difficulty. They are different official domains with different task emphases: one centers on topology, devices, interfaces, protocols, standards, and sensor connectivity; the other centers on compute comparison, deployment location, and an edge-deployment Python workflow.
Do not troubleshoot by changing several layers at once. If you alter the sensor configuration, network path, and application code simultaneously, you cannot identify the cause. Isolate the layer, record the observation, perform one confirming check, and then update the diagram.
Do not overstate what a source proves. The official topic list can establish scope, but it does not automatically establish a current product version, a current API behavior, a current exam delivery method, or a current certification requirement. Label personal study techniques as recommendations and verify technical implementation details in current Cisco documentation.
What should you do next?
First, treat DEVIOT 300-915 as a retired exam and do not attempt to schedule it. Second, use Cisco’s current certification information to identify the relevant successor or alternative objective. Third, retain the historical blueprint only if its IoT and edge-application skills match your learning goal. This three-step check prevents outdated exam preparation from becoming an outdated career plan.
If your goal is technical learning, begin with one architecture diagram and one sensor-connectivity workflow. Then make one edge-versus-cloud decision and outline a Python deployment workflow using the FND and GMM API objectives. Use official Cisco technical references to fill in implementation details, and keep unsupported assumptions out of your notes.
If your goal is a certification, pause after identifying the current path and rebuild the study plan around its active blueprint. Do not transfer DEVIOT’s historical duration, language, domain emphasis, or delivery assumptions to another exam unless the current official source states them.
Conclusion
DEVIOT provides a useful historical model of Cisco IoT application development: understand the network topology, connect and troubleshoot sensors, choose an appropriate compute location, deploy an edge application, and relate data visualization and security to the complete solution. However, Cisco’s published status and last test date make the scheduling decision clear: DEVIOT is not a current exam to book. Use the official sources to verify the present certification route, and use the blueprint-based workflows here only as technical study structure or legacy exam context.
Related exams
- Automating and Programming Cisco Security Solutions (300-735 SAUTO)
- 300-835 exam — Automating Cisco Collaboration Solutions (CLAUTO)
- 300-910 exam — Implementing DevOps Solutions and Practices using Cisco Platforms (DEVOPS)
- 300-920 exam — Developing Applications for Cisco Webex and Webex Devices (DEVWBX)
- 350-901 exam — Developing Applications using Cisco Core Platforms and APIs (DEVCOR)