CISCO 200-901 Developing Applications and Automating Workflows using Cisco Core Platforms (DEVASC) Free Practice Test — 30 Questions
This practice bank exercises core skills for the Cisco DEVASC exam: Python programming logic (factorial, list comprehensions, set operations), CI/CD pipeline efficiency (Jenkins parallel builds, dependency management), API design and testing (RESTful principles, OpenAPI validation with Postman, Swagger), and network/cloud fundamentals (subnetting, VLAN trunking, Zero Touch Provisioning, scaling in public cloud and microservices). It also touches on data handling (GDPR encryption, IoT data volume calculation) and development practices (TDD, debugging). Master these scenarios to recognize patterns in applying Python, automation tools, and network services to solve real-world integration and DevOps challenges.
What this 200-901 practice set measures
This is an analysis of the practice bank, not a claim about the vendor's live exam blueprint. Use it to identify the knowledge, judgment, and recall patterns exercised here, then verify your coverage against the current official exam guide.
Python and Data Structures in Automation
The practice bank repeatedly tests Python proficiency in automation contexts: calculating factorials (iterative vs recursive), processing transaction lists with dictionaries, computing cart totals using list comprehensions, and performing set operations for permission management. These questions require applying Python constructs efficiently—using generator expressions within sum(), set difference for unique permissions, and conditional filtering on nested data. Understanding Python’s data structures and control flow is critical for writing clean, optimized automation scripts in a CI/CD pipeline or network automation context.
- Iterative factorial avoids recursion depth limits; use for loop with result accumulation.
- Generator expressions (price * quantity for price, quantity in cart) within sum() are memory-efficient.
- Set difference (P_A - P_B) returns elements unique to P_A; intersection returns common elements.
- When filtering transactions, ensure inclusive range conditions (>= and <=) to avoid off-by-one errors.
CI/CD Pipeline Efficiency and Automation
Multiple questions focus on optimizing Jenkins CI/CD pipelines: running builds in parallel across agents, handling burst requests with rate limiting, and enforcing mandatory pull request reviews with automated tests. The calculations show that with enough agents, total build time equals a single build duration if all projects run concurrently. For web services, a token bucket approach processes base rate plus burst, then continues with remaining requests in subsequent seconds. These scenarios underscore the importance of resource-aware pipeline design and safe merge strategies.
- Parallel builds: with 5 agents and 5 projects, all can run simultaneously; total time = 1 build duration (e.g., 10 or 30 minutes).
- Rate limiting with burst: process base rate + burst in first second, then remaining requests in following seconds (e.g., 100 rate + 50 burst = 150 in sec1, then 100 in sec2).
- Merge conflicts: implement mandatory PR review with automated tests to prevent untested code from entering main branch.
- CI/CD dependency: use Terraform's `depends_on` to ensure ordered provisioning (e.g., web server before app server).
API Design, Testing, and Documentation
The bank emphasizes RESTful API best practices: stateless interactions, proper HTTP methods (POST for create, GET for retrieve, PUT/PATCH for update, DELETE), and leveraging OpenAPI/Swagger for documentation validation. Postman testing strategies include writing automated tests against response schemas to ensure required fields and data types align with the spec, rather than relying on manual review or code generation. Troubleshooting 404 errors involves first verifying the endpoint URL against Swagger docs before checking environment variables or network traces.
- Stateless API scales better; avoid server-side session state.
- Use HTTP methods consistently: POST for create, GET for read, PUT/PATCH for update, DELETE for delete.
- Validate API responses in Postman using test scripts that check schema against OpenAPI spec.
- For 404 errors, confirm the endpoint path and method in Swagger documentation first.
Network, Cloud, and Security Fundamentals
Questions cover subnetting (calculating usable IPs for /24 block to get 500 hosts, which requires a /23 mask), VLAN trunking (allow all needed VLANs on trunk ports), Zero Touch Provisioning (auto-configuration via central server), public cloud benefits (dynamic scaling via Cisco CloudCenter), and microservices architecture (independent deployability, fault isolation). Security topics include AES-256 for data at rest and TLS 128-bit minimum for data in transit under GDPR. IoT data volume calculations reinforce handling large-scale sensor data.
- To get ≥500 usable IPs from a /24, a /23 mask (255.255.254.0) provides 510 usable addresses.
- Trunk ports must explicitly allow VLANs 10, 20, 30 to carry traffic for the respective departments.
- ZTP automates device configuration by pulling config from a central server after basic network connectivity.
- Public cloud with Cisco solutions (e.g., CloudCenter) enables auto-scaling based on demand.
- Microservices: EPGs with contracts in ACI isolate tenants, while Service Graphs allow dynamic scaling.
Practice CISCO 200-901 Developing Applications and Automating Workflows using Cisco Core Platforms (DEVASC) with real flashcards
Read the prompt, commit to an answer, then flip the card. Move through the deck at your own pace and repeat any topic that does not come back quickly.
Card 1 of 20
1 reviewed this session
Static practice bank
Start the 30-question diagnostic
The complete question bank is embedded in this pre-rendered page. There is no database request or second content download when you begin.
In a software development project, a team is tasked with creating a function that calculates the factorial of a number. The function must handle both positive integers and zero, returning the correct factorial value. Additionally, the team needs to ensure that the function is efficient and does not exceed a maximum recursion depth of 1000 calls. Given the following implementation in Python, identify the potential issues and the best approach to optimize the function while maintaining correctness.
Study workflow
Turn one 200-901 attempt into a study plan
- 1
Analyze Python Automation Scenarios
When encountering a Python problem in these practice questions, first identify the required output (e.g., factorial, total cost, unique permissions). Choose the most Pythonic approach: iterative loops for recursion issues, generator expressions for memory efficiency, and set operations for comparing groups. Test edge cases like zero input or negative numbers.
- 2
Calculate CI/CD and Rate Limiting Outcomes
For CI/CD parallelism, count available agents vs projects. If agents >= projects, total time equals single build time. For rate limiting, apply base rate plus burst allowance; track remaining requests across seconds. Use a token bucket mental model: process the burst limit first, then steady state.
- 3
Apply RESTful and API Testing Best Practices
When designing or testing APIs, always use stateless interactions and correct HTTP methods. To validate documentation, write automated tests in Postman that check response JSON schemas against the OpenAPI specification. For 404 errors, start by verifying the endpoint path in Swagger before other troubleshooting steps.
- 4
Solve Subnetting and VLAN Trunking Problems
To find a subnet mask for a required number of hosts, use the formula: usable IPs = 2^(32-prefix) - 2. For networks needing 500+ hosts, prefix /23 (mask 255.255.254.0) works. For VLAN trunking, ensure the trunk port configuration permits all VLANs that need inter-switch communication; explicitly list them rather than using 'all' or restricting any.
- 5
Evaluate Cloud and Microservices Architecture Decisions
When choosing cloud models, prioritize public cloud for elasticity and managed services. In microservices, use EPGs and contracts in Cisco ACI to isolate tenants and control communication. For orchestration, Terraform provisions infrastructure with explicit dependencies (`depends_on`), while Ansible handles configuration management.
FAQ
Questions about this 200-901 practice page
Clear boundaries on what the bank covers, how to use it, and where official vendor information still matters.
What is the key difference between iterative and recursive factorial implementations for the DEVASC exam?+
Iterative factorial avoids Python's recursion depth limit (default 1000) by using a loop, making it safe for larger inputs. Recursive may hit RecursionError. The practice bank's explanation recommends iterative for efficiency.
How does rate limiting with burst work in a web service scenario?+
If the limit is 100 req/s with a burst of 50, the service can handle up to 150 requests in the first second. Excess requests are queued and processed in subsequent seconds at the base rate. This smooths traffic spikes.
Why must trunk ports explicitly allow all needed VLANs, not just some?+
Restricting trunk ports to only certain VLANs will block traffic for other VLANs across switches, breaking department connectivity. Explicit allowance ensures all required VLANs can traverse the trunk.
What is the role of `depends_on` in Terraform for multi-tier deployments?+
`depends_on` creates an explicit ordering so that one resource (e.g., application server) is provisioned only after another (e.g., web server) is ready. This ensures dependencies are met before configuration occurs.
How does the practice bank recommend handling a 404 error when testing an API?+
First review the API documentation (e.g., Swagger) to confirm the endpoint URL and HTTP method are correct. If that's accurate, then check environment variables and network tools like Wireshark. The documentation check is the initial step to rule out simple mistakes.
Build the next review session
Browse another free bank or use the study strategy guide to turn your misses into spaced review.