Cisco 350-901 Exam Details & Actual Exam Questions
- Exam Code/Number: 350-901
- Exam Name/Title: Developing Applications using Cisco Core Platforms and APIs (DEVCOR)
- Certification Provider: Cisco
- Corresponding Certification: Cisco Certified DevNet Professional
- Exam Questions: 566
- Updated On: Jun,16 2026
- Certification Level: Professional
Cisco Developing Applications using Cisco Core Platforms and APIs (DEVCOR) Exam Questions
View 350-901 actual exam questions, answers and explanations for free.
95% student found the test questions almost same
All the information you need to pass Cisco Developing Applications using Cisco Core Platforms and APIs (DEVCOR) 350-901 exam and free practice exam verified by EduDump exam experts.
Said the test questions were almost same
Passed the exams with the material
Found the study quides effective and helpful
(18 Up Votes)Cisco 350-901 Exam Overview:
| Certification Vendor: | Cisco |
| Exam Name: | Developing Applications using Cisco Core Platforms and APIs (DEVCOR) |
| Exam Number: | 350-901 |
| Available Languages: | English, Japanese |
| Passing Score: | Variable (750-850 / 1000) |
| Exam Price: | $400 USD |
| Certificate Validity Period: | 3 years |
| Related Certifications: | Cisco Certified DevNet Professional Cisco Certified DevNet Specialist - Core |
| Real Exam Qty: | 90-110 |
| Exam Duration: | 120 minutes |
| Exam Format: | Multiple-choice, Multiple-response, Drag-and-drop, Simulation |
| Sample Questions: | Cisco 350-901 Sample Questions |
| Exam Way: | Pearson VUE (Online or Test Center) |
| Pre Condition: | No formal prerequisites, but 3-5 years of software development experience including Python is recommended. |
| Official Syllabus URL: | https://learningnetwork.cisco.com/s/devcor-exam-topics |
Cisco 350-901 Exam Syllabus Topics:
| Section | Weight | Objectives |
|---|---|---|
| Software Development and Design | 20% | - Design patterns (MVC, Observer, Factory, Singleton) - Distributed applications related to the concepts of front-end, back-end, and load balancing - Application design considering latency and rate limiting - Application design and implementation considering observability - Architectural patterns (monolithic, services-oriented, microservices, event-driven, serverless) - Application design and implementation considering maintainability - Application design considering scalability and modularity - Application design considering high availability and resiliency - Basics of software testing - Diagnosing problems with application design - Use of version control (Git) |
| Infrastructure and Automation | 20% | - Basics of Linux and networking (IP addressing, routing, DNS, NTP) - Model-driven programmability (YANG, NETCONF, RESTCONF) - Source code review and code quality assurance - Usage of JSON and YAML for data serialization - Infrastructure as Code (IaC) concepts - Network automation concepts (Ansible, Puppet, Terraform) |
| Cisco Platforms | 20% | - API capabilities of Cisco Meraki - Capabilities of Cisco Nexus platforms - Capabilities of Cisco collaboration platforms (Webex Teams) - Capabilities of Cisco Unified Computing System (UCS) - Capabilities of Cisco security platforms (Firepower, ISE) - Capabilities of Cisco MGMT platforms (vManage, DNA Center, Intersight) - API capabilities of Cisco AppDynamics |
| Application Deployment and Security | 20% | - Application deployment models (on-premises, hybrid, cloud, edge) - OWASP top 10 security risks - Encryption techniques (data in transit, data at rest) - Components of a CI/CD pipeline (build, test, deploy) - Container concepts (Docker, Kubernetes) - Secrets management (HashiCorp Vault, CyberArk) - Benefits of continuous integration and continuous deployment (CI/CD) - Device authentication and authorization (OAuth2, API keys, tokens) |
| Using APIs | 20% | - Usage of software development kits (SDKs) - API authentication/authorization methods (basic auth, OAuth, API keys, tokens) - Common HTTP response codes associated with REST APIs - Pagination and rate-limiting concepts - Synchronous and asynchronous API calls - API styles/protocols (REST, RPC, gRPC, GraphQL, webhook) - Error handling - JSON/YAML data formats |
0
0
0
10