Developing Solutions Using Cisco IoT and Edge Platforms (DEVIOT) Exam Guide
DEVIOT 300-915 validated IoT application-development knowledge 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 now is not how to schedule the exam: Cisco classifies DEVIOT as End of Life/Retired and states that January 20, 2024 was the last day to take it. Use this guide to assess its historical skills and decide whether its blueprint still supports your current learning plan.
Is DEVIOT still available to schedule?
DEVIOT is retired, so a candidate should not treat 300-915 as a currently schedulable Cisco certification exam. 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 it. That changes the preparation decision from booking an appointment to evaluating transferable skills and current Cisco certification options.
What the historical exam represented
Cisco identified DEVIOT as exam 300-915, Developing Solutions Using Cisco IoT and Edge Platforms v1.0. The exam evaluated IoT application-development knowledge as it related to Cisco IoT edge-compute and network architecture. Its published subject areas included Cisco IOx, Cisco EFM, IoT data visualization, and security methods.
What this means for a learner today
Use the published blueprint as a technical study reference rather than as evidence that an exam appointment can be obtained. If a job, course, or certification plan still mentions DEVIOT, confirm the requirement with the organization that issued it and consult Cisco’s current certification information before investing in exam-specific preparation.
Who would have benefited from the DEVIOT blueprint?
The blueprint was aimed at practitioners who needed to connect operational sensors, understand industrial and network components, and develop or deploy applications near the data source. It suited a candidate combining software development with infrastructure reasoning, rather than someone preparing only through memorization of product names or isolated programming syntax.
Application developers working at the edge
A developer following this blueprint needed to reason about applications deployed on edge infrastructure, including the workflow for connecting a sensor and the handling of sensor-connectivity problems. The emphasis was practical: understand how data enters the system, how an application processes it, and how the deployment environment affects the design.
Network and industrial technology practitioners
The architecture domain included gateways, access points, firewalls, routers, and switches, as well as PLCs, embedded microcontrollers, RTOS systems, Cisco interfaces, communication protocols, and communication standards. That combination made the exam relevant to people working across operational technology, networking, and application integration.
Candidates pursuing related DevNet credentials at the time
Cisco associated DEVIOT with the Cisco Certified DevNet Professional and Cisco Certified DevNet Specialist—IoT certifications. Those associations explain why the blueprint combined development tasks with architecture and deployment decisions, but they do not establish a current path through DEVIOT now that Cisco has retired the exam.
What capabilities did the exam measure?
The central capability was translating an IoT application requirement into an edge solution: interpret the network and device path, choose an appropriate compute location, connect and troubleshoot a sensor, and automate deployment. A strong preparation plan therefore studies decisions and workflows, not just definitions of Cisco platforms.
Network and device-flow interpretation
Cisco assigned 20% of the exam blueprint to Cisco Network IoT Architecture. The domain required understanding how gateways, access points, firewalls, routers, and switches participate in topology and data-flow interpretation. It also covered industrial components and the interfaces, protocols, and standards used to move information between them.
Compute-location decisions
Cisco assigned 10% of the exam blueprint to Compute and Analysis. This domain covered comparing edge devices with generic compute devices and selecting cloud or edge deployment for an application scenario. Preparation should focus on identifying the requirement that drives the choice, such as where processing must occur and what the application needs from its environment, without inventing criteria not stated in the scenario.
Sensor connection and fault isolation
The blueprint required candidates to construct a workflow for connecting a sensor and troubleshoot sensor-connectivity issues. That calls for a layered method: establish the sensor and interface assumptions, trace the communication path, identify where data stops or changes form, and distinguish a configuration problem from a transport or device problem.
Edge deployment automation
The blueprint included constructing a Python script to deploy an application at the edge using FND and GMM APIs. This is more demanding than recognizing an API name. A learner should be able to map inputs, authentication or access assumptions when documented, request sequence, response handling, and failure reporting into a coherent deployment workflow.
How should the blueprint domains shape study time?
Give the largest deliberate block of study to architecture because Cisco assigned Cisco Network IoT Architecture 20% of the blueprint, then connect that knowledge to the practical sensor and deployment tasks. Compute and Analysis carried 10%, so it deserves focused practice rather than being ignored as a small domain. The remaining topics should be organized by task dependency, not by an arbitrary product list.
Start with the data path
Begin by drawing a simple end-to-end path for an IoT application: sensor, local interface or controller, network components, edge compute, and any downstream service. Label what each component contributes. Then redraw the path for a different deployment choice. This exercise makes topology interpretation and cloud-versus-edge reasoning concrete.
Use weighted domains as a prioritization signal
The published percentages are useful for deciding where to spend attention, but they are not a substitute for the complete Cisco topic list. Treat Cisco Network IoT Architecture as a major preparation area because its official allocation is 20%, and treat Compute and Analysis as a targeted area because its official allocation is 10%. Do not compare those figures without their domain labels.
Finish with integrated scenarios
After studying individual technologies, combine them. For example, take a sensor workflow, place a gateway and firewall in the path, choose an edge device, and describe how an application would be deployed and monitored. The purpose is not to predict exam questions; it is to test whether your reasoning survives a change in topology or deployment constraints.
Which technical subjects deserve hands-on attention?
Prioritize subjects that force you to explain what happens between a physical signal and an application result. Cisco’s published material names IOx, EFM, IoT data visualization, and security methods, while the detailed blueprint adds device, protocol, connectivity, and deployment tasks. Build small, controlled exercises around those relationships instead of collecting disconnected notes.
Cisco IOx and edge application behavior
Study IOx as an application-hosting and edge-compute context, then ask what an application needs from the host, network, and data source. Record the assumptions of each exercise: where the application runs, how it receives data, and how you would recognize a deployment or runtime failure. Keep product behavior tied to Cisco documentation available for the version being studied.
Cisco EFM and integration boundaries
Treat Cisco EFM as part of the integration problem. The useful question is not simply what the acronym expands to, but how the relevant platform or service participates in collecting, forwarding, managing, or exposing IoT information. Map that role against the sensor, edge application, and visualization layer, and mark any interface that needs separate verification.
Data visualization
For visualization practice, trace the complete route from measurement to displayed result. Identify the transformation, aggregation, or filtering that occurs before a user sees information. Then consider what a misleading display might indicate: stale input, an incorrect mapping, a broken connection, or an application-side processing error.
Security methods
Study security as a property of the workflow rather than a final vocabulary chapter. Examine the boundaries between sensor, controller, network, edge host, application, and service. For each boundary, note what must be protected and what evidence would indicate a problem. Use Cisco’s applicable technical documentation for precise implementation details instead of assuming that a generic cloud-security pattern maps directly to an industrial edge system.
How do you practice the sensor workflow?
Practice by writing the connection process in an order that another engineer could follow. Include the device assumptions, physical or logical interface, communication method, destination, application handoff, and validation step. Then deliberately remove one assumption and diagnose the resulting failure. This mirrors the blueprint’s construction and troubleshooting emphasis without relying on unauthorized exam material.
Build a connection checklist
A useful checklist begins with the sensor’s role and output, then identifies the receiving component and expected communication path. Add configuration values only when your lab or official documentation supplies them. End with a validation that confirms meaningful data, not merely that a device appears reachable.
Troubleshoot by layer
When data does not arrive, avoid changing several variables at once. Check the sensor and power or interface assumptions first, then the local controller or gateway, communication settings, network path, edge application, and downstream display. At each layer, write the observation that would confirm or reject the hypothesis.
Separate connectivity from data quality
A reachable device can still produce unusable information. Distinguish no connection, intermittent transport, malformed payloads, incorrect units, stale values, and application-processing errors. This separation improves both troubleshooting accuracy and the quality of explanations you give for an architecture scenario.
How should you prepare for the Python and API task?
Prepare to explain a deployment script as a sequence of reliable operations, not as a memorized block of code. The official blueprint specifically names a Python script that deploys an application at the edge using FND and GMM APIs. Practice reading API documentation, forming requests from supplied inputs, handling responses, and reporting failures clearly.
Plan the script before writing it
Write the deployment flow in plain language first: gather inputs, establish the required API interaction, identify the target edge environment, submit the application deployment request, inspect the result, and handle an unsuccessful response. Only then translate the flow into Python. This exposes missing assumptions before syntax becomes a distraction.
Practice documentation-driven coding
Use official API references and a controlled lab or mock where available. Identify required fields, data types, response structures, and error behavior from the documentation. Do not copy an example without understanding which values are environment-specific. A script that looks plausible but sends the wrong target or payload is not a dependable deployment solution.
Test failure handling
Include cases such as a missing input, an unavailable target, an unsuccessful response, and an unexpected response body. The exact handling depends on the documented API behavior, so avoid inventing status codes or authentication details. The preparation goal is to demonstrate disciplined reasoning when the happy path does not work.
What study sequence works best?
Use a dependency-based sequence: architecture first, then sensor connectivity, then compute selection, followed by edge deployment automation and visualization or security integration. This order lets each later exercise reuse an earlier data path. End every study session with a written explanation of one design choice and one troubleshooting decision.
Phase one: establish the architecture model
List the devices and services in a representative IoT topology and describe the direction of data flow. Review gateways, access points, firewalls, routers, switches, PLCs, embedded microcontrollers, and RTOS systems as they relate to the application path. Your output should be a labeled diagram and a short explanation of each boundary.
Phase two: work through sensor integration
Construct a sensor-connection workflow from the blueprint topics. For each step, identify the expected input and the evidence that the step succeeded. Create several fault variations and troubleshoot them one at a time. This phase converts architecture vocabulary into operational reasoning.
Phase three: make compute and deployment decisions
Compare an edge device with a generic compute device for a stated application scenario, then justify whether processing belongs at the edge or in the cloud. Follow that with a Python deployment exercise using the FND and GMM API material available to you. Keep the scenario and assumptions visible so the decision can be reviewed.
Phase four: integrate application concerns
Add the named subject areas of IOx, EFM, data visualization, and security methods to the workflow. Ask how each affects deployment, data handling, observability, or protection. Finish with a timed review of your own diagrams, scripts, and troubleshooting notes rather than rereading every page from the beginning.
What common preparation mistakes should you avoid?
The most damaging mistakes are treating the retired exam as schedulable, memorizing product terms without tracing data flow, and practicing only successful deployments. A sound approach verifies exam status first, ties every technology to a design task, and tests failure reasoning. Avoid dumps and leaked-question material; memorization of unauthorized content does not establish the skills described by Cisco’s blueprint.
Mistake: planning around an old appointment
Because Cisco states that the last day to take DEVIOT 300-915 was January 20, 2024, a new candidate should not build a calendar around an assumed testing window. Confirm the status before purchasing training, booking travel, or allocating exam-specific study time.
Mistake: learning architecture as a glossary
Knowing that a component is a gateway, firewall, or PLC is not enough. Explain where it sits in the topology, what data crosses it, and what failure would look like. If you cannot draw the path or identify the next diagnostic check, return to the architecture exercise.
Mistake: ignoring interfaces and protocols
The blueprint includes Cisco interfaces, communication protocols, and communication standards alongside industrial devices and systems. Do not study these as interchangeable labels. Record what each one connects, what assumptions it introduces, and which part of the workflow depends on it.
Mistake: writing only the happy-path script
A deployment script that works once with fixed values provides weak preparation. Vary the target and inputs, inspect the API response, and decide how the script should report failure. Keep the implementation tied to documented FND and GMM API behavior rather than filling gaps with guesses.
What were the documented delivery details?
Cisco’s historical DEVIOT overview listed a 90-minute exam duration and English as the available exam language. It also listed February 24, 2020 as the first date to test. These are historical delivery details for the identified exam, not a current scheduling promise; the retirement information takes precedence for present-day planning.
How to interpret the 90-minute duration
For historical study or comparison, the listed 90-minute duration suggests that practice should include concise scenario analysis and deliberate time control. Do not infer an unsupported question count, passing score, item format, or current delivery method from the duration alone. Cisco’s cited overview does not establish those details here.
What is confirmed about language
Cisco listed English as the available exam language for DEVIOT. That fact applies to the historical exam overview and should not be generalized to other Cisco exams or replacement credentials without checking their own official information.
How can DEVIOT knowledge support a current learning decision?
Treat the DEVIOT topics as a skills inventory: industrial and network architecture, sensor integration, edge-versus-cloud analysis, API-based deployment, visualization, and security. Then compare that inventory with the current role or certification requirement. This is more useful than trying to preserve an obsolete exam routine unchanged.
For an IoT application developer
Keep the sensor workflow, Python automation, deployment reasoning, and data-path troubleshooting. Build a small portfolio exercise that documents assumptions, API interactions, error handling, and the route from input to visualization. Label it as skills practice rather than evidence of passing a retired exam.
For a network-focused practitioner
Emphasize topology interpretation and the relationship among gateways, access points, firewalls, routers, switches, industrial controllers, and protocols. Add enough application context to explain why a network choice affects edge behavior and troubleshooting, rather than studying network components in isolation.
For a certification candidate
Do not assume that DEVIOT’s historical association with the Cisco Certified DevNet Professional or Cisco Certified DevNet Specialist—IoT certifications describes a current route. Verify the active certification structure and current exam requirements through Cisco before selecting a replacement target.
Can tested IOx applications inform preparation?
Cisco’s IOx Interoperability Verification Testing material explains that its program tests IOx-hosted applications for security vulnerabilities and network friendliness. It says tested applications help reduce integration costs, accelerate deployments, and reduce the risk of failure. This is useful context for understanding why deployment quality and compatibility matter, but it is not a substitute for the retired DEVIOT blueprint.
Use interoperability as a design lens
When reviewing an edge application, ask whether it behaves responsibly on the intended network and whether its security properties have been considered. Examine configuration assumptions, resource expectations, communication behavior, and failure reporting. Keep these as engineering review questions, not claims that an application has passed Cisco testing.
Connect testing concerns to the blueprint
The testing context reinforces several historical DEVIOT themes: application deployment at the edge, network interaction, security methods, and reduction of integration risk. It can therefore enrich a lab review after the core architecture and API workflow are understood.
What should you do next?
First, confirm that your objective is current: DEVIOT 300-915 is retired and cannot be approached as a new booking. Next, extract the transferable skills that match your role, choose current Cisco information for any active credential decision, and build one end-to-end lab or design exercise covering architecture, sensor connectivity, compute placement, and deployment automation.
A practical checklist
Verify the certification requirement with the employer, course, or project that mentioned DEVIOT. Review the official historical topic list. Draw and explain an IoT data path. Practice a sensor connection and layered fault diagnosis. Compare edge and generic compute for a defined scenario. Construct a documented Python deployment workflow using the available FND and GMM API references. Review visualization and security boundaries.
How to judge readiness for the skills, not the retired exam
You are making useful progress when you can justify a topology, explain the role of each component, identify where sensor data can fail, defend an edge or cloud choice from the scenario, and describe how an API-driven deployment should handle success and failure. If any explanation depends on memorized answers rather than documented behavior, return to the relevant lab.
Conclusion
DEVIOT remains a useful historical map of Cisco IoT and edge-development skills, but it is not a current exam target: Cisco classifies 300-915 as End of Life/Retired and records January 20, 2024 as its last day to take the exam. Study its blueprint only when those capabilities serve a present role or learning objective. Base preparation on architecture diagrams, sensor troubleshooting, compute-placement analysis, documented API workflows, and integrated security and visualization reasoning—not dumps or unsupported assumptions about a replacement exam.
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)
