Exam Domain
A major topic area covered by the exam.
Getting Started: Exam Overview
Free knowledge base
DevNet Associate (DEVASC) v1.0 — key terms, tricks & tips
Everything from the course in one searchable place: 308 entries. Use it to review before a practice test or look up a word you forgot.
308 results · showing first 300, refine your search
Weighting
Percentage of total exam score attributed to a domain.
Getting Started: Exam Overview
Pearson VUE
Third-party vendor administering Cisco certification exams.
Getting Started: Exam Overview
Multiple-choice
Question type with one or more correct options.
Getting Started: Exam Overview
Simulation
Question type testing practical skills in a virtual environment.
Getting Started: Exam Overview
Score Report
Document detailing exam performance by domain.
Getting Started: Exam Overview
Retake Policy
Rules governing how soon an exam can be reattempted.
Getting Started: Exam Overview
Understanding the DEVASC Exam Structure
To remember the high-weight domains: 'APIs, Software, Platforms, Automation' (ASPA) are the big ones. Network Fundamentals is tiny!
Getting Started: Exam Overview
Understanding the DEVASC Exam Structure
The DEVASC exam (200-901) is 120 minutes long and covers six specific domains with defined weightings. Memorize these six domains and their approximate weightings to prioritize your study.
Getting Started: Exam Overview
Understanding the DEVASC Exam Structure
Spending too much time on low-weighted topics like Network Fundamentals, neglecting higher-weighted areas.
Getting Started: Exam Overview
Understanding the DEVASC Exam Structure
Not understanding the different question types, especially multiple-answer or simulation questions, which require specific strategies.
Getting Started: Exam Overview
Understanding the DEVASC Exam Structure
Ignoring the score report after a failed attempt, missing valuable feedback on weak areas.
Getting Started: Exam Overview
Cisco DevNet
Cisco's developer program for APIs, tools, and learning.
Getting Started: Exam Overview
API Documentation
Detailed guides for using an API, including endpoints and data.
Getting Started: Exam Overview
SDK (Software Development Kit)
Tools and libraries to build applications for a platform.
Getting Started: Exam Overview
DevNet Sandbox
Free, on-demand access to real Cisco hardware/software.
Getting Started: Exam Overview
Always-On Sandbox
Continuously available, shared DevNet sandbox environment.
Getting Started: Exam Overview
Reservable Sandbox
Dedicated DevNet sandbox for a specific, scheduled period.
Getting Started: Exam Overview
Code Exchange
DevNet repository for community-contributed code samples.
Getting Started: Exam Overview
Learning Labs
Step-by-step tutorials and exercises on DevNet.
Getting Started: Exam Overview
Navigating Cisco DevNet Resources
To navigate DevNet, remember 'T-L-S-C-C': Technologies, Learning, Sandboxes, Code Exchange, Community. It's like finding your way through a library!
Getting Started: Exam Overview
Navigating Cisco DevNet Resources
The DEVASC exam expects you to know the purpose of DevNet Sandboxes (Always-On vs. Reservable) and where to find API documentation for common Cisco platforms like DNA Center or Meraki.
Getting Started: Exam Overview
Navigating Cisco DevNet Resources
Not using DevNet Sandboxes for hands-on practice, relying only on theoretical knowledge.
Getting Started: Exam Overview
Navigating Cisco DevNet Resources
Failing to explore the 'Learning' section for specific DEVASC study materials and labs.
Getting Started: Exam Overview
Navigating Cisco DevNet Resources
Underestimating the importance of navigating DevNet quickly to find relevant API documentation.
Getting Started: Exam Overview
SDLC
Software Development Life Cycle; structured process for software creation.
Software Development Fundamentals
Waterfall
Linear, sequential development methodology; each phase finishes before next.
Software Development Fundamentals
Agile
Iterative, flexible development methodology; emphasizes collaboration and rapid delivery.
Software Development Fundamentals
Sprint
A short, time-boxed iteration in Agile development, typically 1-4 weeks.
Software Development Fundamentals
Scrum
A popular Agile framework for managing complex software projects.
Software Development Fundamentals
Kanban
An Agile method focusing on visualizing work and limiting work-in-progress.
Software Development Fundamentals
Requirements Gathering
Collecting and documenting what a software system needs to do.
Software Development Fundamentals
Deployment
Releasing software to users or production environments.
Software Development Fundamentals
Software Development Methodologies & SDLC
Remember 'WAFAS' for Waterfall: 'W' for 'Wait for each step,' 'A' for 'Analyze upfront,' 'F' for 'Fixed plan,' 'A' for 'After each phase,' 'S' for 'Sequential.' For Agile, think 'ADAPT': 'A' for 'Adaptable,' 'D' for 'Deliver frequently,' 'A' for 'CollaborAte,' 'P' for 'Prioritize,' 'T' for 'Teamwork.'
Software Development Fundamentals
Software Development Methodologies & SDLC
The exam expects you to distinguish between Waterfall and Agile, understanding their core principles and when each is best applied. Look for keywords like 'sequential,' 'fixed requirements,' 'iterative,' or 'changing requirements' in questions.
Software Development Fundamentals
Software Development Methodologies & SDLC
Confusing the phases of SDLC or their order.
Software Development Fundamentals
Software Development Methodologies & SDLC
Assuming Agile is always better than Waterfall; each has its place.
Software Development Fundamentals
Software Development Methodologies & SDLC
Not understanding that Scrum and Kanban are specific implementations of Agile, not separate methodologies.
Software Development Fundamentals
Syntax
The set of rules that define how a Python program is written.
Software Development Fundamentals
Indentation
Whitespace used to define code blocks in Python; crucial for structure.
Software Development Fundamentals
Data Type
Classification of data that tells the interpreter how to interpret values.
Software Development Fundamentals
Conditional Statement
Code that executes based on whether a condition is true or false (if/elif/else).
Software Development Fundamentals
Loop
A control flow statement that executes a block of code repeatedly.
Software Development Fundamentals
Function
A named block of reusable code that performs a specific task.
Software Development Fundamentals
Mutable
Refers to objects whose state can be modified after creation (e.g., lists).
Software Development Fundamentals
Immutable
Refers to objects whose state cannot be changed after creation (e.g., tuples, strings).
Software Development Fundamentals
Python Basics: Syntax, Data Types, Control Flow
ITALIC: Indentation, Types, If/Else, Loops, Input/Output, Comments. Remember these core concepts for Python basics!
Software Development Fundamentals
Python Basics: Syntax, Data Types, Control Flow
The exam expects you to recognize correct Python syntax, identify common data types (int, str, list, dict, bool), and understand how 'if/elif/else' and 'for/while' loops control program flow. Pay attention to indentation and the use of colons.
Software Development Fundamentals
Python Basics: Syntax, Data Types, Control Flow
Incorrect indentation: Python uses whitespace for code blocks; inconsistent or incorrect indentation will cause 'IndentationError'.
Software Development Fundamentals
Python Basics: Syntax, Data Types, Control Flow
Confusing mutable and immutable types: Trying to modify a tuple or string in place will result in an error.
Software Development Fundamentals
Python Basics: Syntax, Data Types, Control Flow
Forgetting colons: 'if', 'for', 'while', and 'def' statements must end with a colon (:) to define the start of a new code block.
Software Development Fundamentals
List
Ordered, mutable collection of items in Python.
Software Development Fundamentals
Tuple
Ordered, immutable collection of items in Python.
Software Development Fundamentals
Dictionary
Unordered collection of key-value pairs for fast lookup.
Software Development Fundamentals
Set
Unordered collection of unique elements.
Software Development Fundamentals
Algorithm
Step-by-step procedure to solve a problem.
Software Development Fundamentals
Linear Search
Checks each item sequentially until target is found.
Software Development Fundamentals
Binary Search
Efficient search for sorted lists by halving intervals.
Software Development Fundamentals
Big O Notation
Describes algorithm's efficiency growth with input size.
Software Development Fundamentals
Advanced Python: Data Structures & Algorithms
L-T-D-S: Lists are Like Tupperware (changeable), Tuples are Tightly sealed (unchangeable), Dictionaries are Doorways (key-value access), Sets are for Singles (unique items).
Software Development Fundamentals
Advanced Python: Data Structures & Algorithms
The exam often tests your ability to select the most appropriate Python data structure for a given scenario. Pay close attention to keywords like 'unique items,' 'fast lookup by key,' 'ordered and unchangeable,' or 'ordered and changeable.' Memorize the characteristics of lists, tuples, dictionaries, and sets.
Software Development Fundamentals
Advanced Python: Data Structures & Algorithms
Using a list for frequent lookups by a unique identifier when a dictionary would be much faster.
Software Development Fundamentals
Advanced Python: Data Structures & Algorithms
Attempting to use binary search on an unsorted list, which will produce incorrect results.
Software Development Fundamentals
Advanced Python: Data Structures & Algorithms
Not considering the Big O complexity for large datasets, leading to inefficient code that performs poorly under scale.
Software Development Fundamentals
Version Control System (VCS)
Software to manage changes to documents, code, and other files over time.
Software Development Fundamentals
Git
A distributed version control system widely used for tracking changes in source code.
Software Development Fundamentals
Repository
A project's entire history, including all files and revisions.
Software Development Fundamentals
Commit
A snapshot of your repository at a specific point in time, with a message.
Software Development Fundamentals
Branch
A lightweight movable pointer to a commit, allowing parallel development.
Software Development Fundamentals
Merge
The process of combining changes from one branch into another.
Software Development Fundamentals
Staging Area
An intermediate area where changes are prepared before being committed.
Software Development Fundamentals
Remote Repository
A shared repository hosted on a server, used for collaboration.
Software Development Fundamentals
Version Control with Git: Basics and Workflows
Remember 'ACPU' for the core Git actions: Add, Commit, Push, Update (pull).
Software Development Fundamentals
Version Control with Git: Basics and Workflows
The DevNet Associate exam expects you to understand the difference between local and remote repositories and the purpose of commands like 'git clone', 'git add', 'git commit', 'git push', and 'git pull'. Pay attention to the order of operations.
Software Development Fundamentals
Version Control with Git: Basics and Workflows
Forgetting to 'git add' files before 'git commit', resulting in an empty commit or missing changes.
Software Development Fundamentals
Version Control with Git: Basics and Workflows
Trying to 'git push' without first 'git pull'ing recent changes from the remote, leading to conflicts.
Software Development Fundamentals
Version Control with Git: Basics and Workflows
Working directly on the 'main' branch for new features instead of creating a dedicated feature branch.
Software Development Fundamentals
REST
Architectural style for networked applications.
Mastering API Interactions
Resource
Any identifiable information, accessed via URI.
Mastering API Interactions
URI
Uniform Resource Identifier, unique name for a resource.
Mastering API Interactions
Representation
How resource state is delivered (e.g., JSON, XML).
Mastering API Interactions
Statelessness
Server does not store client context between requests.
Mastering API Interactions
Idempotence
Operation yields same result if executed multiple times.
Mastering API Interactions
HTTP Methods
Verbs (GET, POST, PUT, DELETE) for resource actions.
Mastering API Interactions
Uniform Interface
Standardized way to interact with resources.
Mastering API Interactions
REST API Concepts and Principles
To remember REST principles: 'CLSUC' - Clients Like Servers, Understand Caching. (Client-Server, Layered System, Statelessness, Uniform Interface, Cacheability)
Mastering API Interactions
REST API Concepts and Principles
The exam often tests the core REST constraints. Memorize 'Client-Server, Stateless, Cacheable, Uniform Interface, Layered System'. Also, know which HTTP methods are idempotent.
Mastering API Interactions
REST API Concepts and Principles
Confusing REST with a protocol; it's an architectural style.
Mastering API Interactions
REST API Concepts and Principles
Assuming REST APIs must use JSON; while common, XML or other formats are also valid representations.
Mastering API Interactions
REST API Concepts and Principles
Expecting the server to remember your previous actions (violating statelessness).
Mastering API Interactions
Authentication
Verifying the identity of a user or application.
Mastering API Interactions
Authorization
Granting permission to an authenticated entity.
Mastering API Interactions
Basic Authentication
Sends Base64 encoded username:password in Authorization header.
Mastering API Interactions
Token-Based Auth
Uses an access token (e.g., JWT) for subsequent requests.
Mastering API Interactions
OAuth 2.0
Authorization framework for delegated access, not authentication.
Mastering API Interactions
Access Token
Credential allowing access to protected resources.
Mastering API Interactions
Authorization Code
Temporary code exchanged for an access token in OAuth 2.0.
Mastering API Interactions
Resource Owner
The entity (user) that grants access to their protected resources.
Mastering API Interactions
API Authentication: Basic, Token, OAuth 2.0
BAT-O: Basic, Access Token, OAuth. Remember them like a baseball bat hitting an 'O' for authentication!
Mastering API Interactions
API Authentication: Basic, Token, OAuth 2.0
For the DevNet Associate exam, memorize the four main grant types of OAuth 2.0 and understand the high-level steps of the Authorization Code Grant flow. Keywords to spot include 'delegated access' and 'authorization framework'.
Mastering API Interactions
API Authentication: Basic, Token, OAuth 2.0
Using Basic Authentication without HTTPS, exposing credentials.
Mastering API Interactions
API Authentication: Basic, Token, OAuth 2.0
Confusing authentication (who you are) with authorization (what you can do).
Mastering API Interactions
API Authentication: Basic, Token, OAuth 2.0
Implementing OAuth 2.0 flows incorrectly, leading to security vulnerabilities.
Mastering API Interactions
Endpoint
A specific URL where an API can be accessed.
Mastering API Interactions
HTTP Method
The action to be performed (GET, POST, PUT, DELETE).
Mastering API Interactions
curl
Command-line tool for making HTTP requests.
Mastering API Interactions
Postman
GUI tool for API development, testing, and documentation.
Mastering API Interactions
Status Code
A 3-digit number indicating the HTTP request outcome.
Mastering API Interactions
Request Body
Data sent from client to server in a POST/PUT request.
Mastering API Interactions
Exploring API Documentation & Testing Tools
Docs, Curl, Postman: 'DCP' for 'Debug, Check, Play' with APIs!
Mastering API Interactions
Exploring API Documentation & Testing Tools
The exam expects you to identify key sections of API documentation (endpoints, methods, parameters, authentication) and understand the basic usage of `curl` and Postman for testing and troubleshooting API calls. Focus on interpreting status codes and error messages.
Mastering API Interactions
Exploring API Documentation & Testing Tools
Ignoring error messages in the API response, which often contain crucial debugging information.
Mastering API Interactions
Exploring API Documentation & Testing Tools
Not checking authentication details (API keys, tokens) as a first step when receiving 401/403 errors.
Mastering API Interactions
Exploring API Documentation & Testing Tools
Assuming the API documentation is always perfectly up-to-date; always cross-reference with actual testing.
Mastering API Interactions
Webhook
An automated HTTP POST request sent by a service when an event occurs.
Mastering API Interactions
Polling
Repeatedly making requests to an API to check for new data or changes.
Mastering API Interactions
Rate Limiting
Restricting the number of API requests an application can make in a timeframe.
Mastering API Interactions
HTTP 429
Status code indicating 'Too Many Requests' due to rate limiting.
Mastering API Interactions
JSON
JavaScript Object Notation; a lightweight, human-readable data interchange format.
Mastering API Interactions
XML
Extensible Markup Language; a tag-based data interchange format.
Mastering API Interactions
Key-Value Pair
A fundamental data structure where a unique key maps to a specific value.
Mastering API Interactions
Exponential Backoff
A strategy for retrying failed operations with progressively longer delays.
Mastering API Interactions
Webhooks, Rate Limiting, and Data Formats
W-R-D: Webhooks React Directly (push), Rate limits Restrict Demands, Data formats Describe Data.
Mastering API Interactions
Webhooks, Rate Limiting, and Data Formats
For the DEVASC exam, be prepared to distinguish between polling and webhooks, recognize HTTP 429 as a rate limit indicator, and identify JSON and XML as primary API data formats. Understand their basic structure.
Mastering API Interactions
Webhooks, Rate Limiting, and Data Formats
Confusing webhooks (push) with polling (pull) and their respective efficiency implications.
Mastering API Interactions
Webhooks, Rate Limiting, and Data Formats
Ignoring HTTP 429 responses and not implementing retry logic, leading to application failures.
Mastering API Interactions
Webhooks, Rate Limiting, and Data Formats
Misunderstanding the basic structure of JSON or XML, causing parsing errors in API integrations.
Mastering API Interactions
Cisco DNA Center
Centralized network management platform for enterprise networks.
Cisco Platforms for Developers
Northbound API
APIs used by external applications to consume services from a platform.
Cisco Platforms for Developers
Southbound API
APIs used by a platform to communicate with network devices.
Cisco Platforms for Developers
Cisco Meraki
Cloud-managed networking solution with centralized control.
Cisco Platforms for Developers
Meraki Dashboard API
RESTful API for programmatic management of Meraki networks.
Cisco Platforms for Developers
Webhooks
Automated messages sent from a system when specific events occur.
Cisco Platforms for Developers
Assurance APIs
DNA Center APIs for monitoring network health and performance.
Cisco Platforms for Developers
Cisco DNA Center & Meraki APIs
DNA Center has 'North' for 'New' applications and 'South' for 'Systems' (devices). Meraki is 'Mighty' in the 'Cloud'.
Cisco Platforms for Developers
Cisco DNA Center & Meraki APIs
The exam expects you to know that DNA Center uses northbound APIs for integration with external systems and southbound APIs for device interaction. For Meraki, remember it's a cloud-managed platform and its APIs are RESTful for network management.
Cisco Platforms for Developers
Cisco DNA Center & Meraki APIs
Confusing DNA Center's northbound and southbound API directions.
Cisco Platforms for Developers
Cisco DNA Center & Meraki APIs
Assuming Meraki APIs are only for monitoring, neglecting their configuration capabilities.
Cisco Platforms for Developers
Cisco DNA Center & Meraki APIs
Not understanding that DNA Center manages on-premise enterprise networks, while Meraki is cloud-managed.
Cisco Platforms for Developers
Webex Teams API
RESTful interface for programmatic interaction with Webex Teams.
Cisco Platforms for Developers
Full-Stack Observability (FSO)
Holistic view of application and infrastructure performance.
Cisco Platforms for Developers
AppDynamics
Cisco's FSO solution for application performance monitoring.
Cisco Platforms for Developers
Bot
Automated program interacting with users in Webex Teams spaces.
Cisco Platforms for Developers
Space (Room)
A collaboration area in Webex Teams for messaging and sharing.
Cisco Platforms for Developers
Webex Teams & FSO Development
To remember Webex Teams APIs, think: 'Mice Run Past People's Windows' for Messages, Rooms, People, Webhooks.
Cisco Platforms for Developers
Webex Teams & FSO Development
The exam often tests your understanding of *which* API resources are used for *what* purpose in Webex Teams, e.g., 'Which API would you use to send a message?' (Messages API). Also, recognize the core benefit of FSO: holistic visibility.
Cisco Platforms for Developers
Webex Teams & FSO Development
Confusing Webex Teams API authentication methods (e.g., trying to use OAuth for a simple bot personal access token).
Cisco Platforms for Developers
Webex Teams & FSO Development
Not understanding the difference between polling an API and receiving real-time updates via webhooks.
Cisco Platforms for Developers
Webex Teams & FSO Development
Thinking FSO is just basic monitoring; it's about correlating data across the entire stack, not just collecting metrics.
Cisco Platforms for Developers
ACI
Application Centric Infrastructure, an SDN solution for data centers.
Cisco Platforms for Developers
APIC
Application Policy Infrastructure Controller, central controller for ACI.
Cisco Platforms for Developers
SD-WAN
Software-Defined Wide Area Network, for distributed network management.
Cisco Platforms for Developers
vManage
Centralized management platform for Cisco SD-WAN.
Cisco Platforms for Developers
Policy-driven
Network configuration based on high-level application requirements.
Cisco Platforms for Developers
Overlay Network
A virtual network built on top of an existing physical network.
Cisco Platforms for Developers
ACI, SD-WAN, and DevNet Sandbox
Remember 'ACI for Data Center Apps' and 'SD-WAN for Wide Area Paths'. ACI is inside the building, SD-WAN connects buildings.
Cisco Platforms for Developers
ACI, SD-WAN, and DevNet Sandbox
The exam often asks about the primary function or key components of ACI (APIC, data center automation) versus SD-WAN (vManage, WAN optimization). Memorize their distinct use cases.
Cisco Platforms for Developers
ACI, SD-WAN, and DevNet Sandbox
Confusing ACI's data center focus with SD-WAN's wide area network focus.
Cisco Platforms for Developers
ACI, SD-WAN, and DevNet Sandbox
Underestimating the importance of DevNet Sandbox for hands-on learning and exam preparation.
Cisco Platforms for Developers
ACI, SD-WAN, and DevNet Sandbox
Not understanding that both ACI and SD-WAN are software-defined, but for different domains.
Cisco Platforms for Developers
IOS XE
Linux-based Cisco OS for enterprise routing/switching.
Cisco Platforms for Developers
NX-OS
Cisco OS for Nexus data center switches.
Cisco Platforms for Developers
NETCONF
Protocol for network device configuration and monitoring.
Cisco Platforms for Developers
RESTCONF
HTTP-based protocol for network device configuration.
Cisco Platforms for Developers
YANG
Data modeling language for network configuration and state.
Cisco Platforms for Developers
NX-API
RESTful API for programmatic access to NX-OS devices.
Cisco Platforms for Developers
Model-driven
Configuring devices using structured data models (YANG).
Cisco Platforms for Developers
Event-driven
Automation triggered by specific network events.
Cisco Platforms for Developers
IOS XE & NX-OS Programmability Features
YANG is like a YARDSTICK for your network data – it measures and defines everything precisely for NETCONF and RESTCONF.
Cisco Platforms for Developers
IOS XE & NX-OS Programmability Features
On the DevNet Associate exam, pay close attention to the distinction between IOS XE and NX-OS features. Know that NETCONF and RESTCONF use YANG for data modeling, and understand the benefits of model-driven approaches over traditional CLI scripting.
Cisco Platforms for Developers
IOS XE & NX-OS Programmability Features
Confusing NETCONF/RESTCONF with traditional CLI scripting; they offer structured, transactional management.
Cisco Platforms for Developers
IOS XE & NX-OS Programmability Features
Not understanding that YANG is a data modeling language, not a protocol itself.
Cisco Platforms for Developers
IOS XE & NX-OS Programmability Features
Assuming all Cisco devices support the exact same programmability features; IOS XE and NX-OS have distinct capabilities.
Cisco Platforms for Developers
Container
Isolated package of app and its dependencies.
Application Deployment & Security
Docker
Platform for building, sharing, and running containers.
Application Deployment & Security
Docker Image
Read-only template for creating Docker containers.
Application Deployment & Security
Kubernetes (K8s)
Orchestration platform for automating container management.
Application Deployment & Security
Pod
Smallest deployable unit in Kubernetes, holds one or more containers.
Application Deployment & Security
Node
Worker machine (VM or physical server) in a Kubernetes cluster.
Application Deployment & Security
Control Plane
Manages the Kubernetes cluster state and worker nodes.
Application Deployment & Security
Dockerfile
Text file defining steps to build a Docker image.
Application Deployment & Security
Containerization: Docker & Kubernetes Basics
Imagine a 'container ship' (Docker) carrying many 'shipping containers' (applications) across the 'ocean' (Kubernetes) to different 'ports' (servers).
Application Deployment & Security
Containerization: Docker & Kubernetes Basics
The exam often tests the fundamental differences between VMs and containers, focusing on resource efficiency and isolation. Be prepared to distinguish the roles of Docker (container runtime) and Kubernetes (orchestration).
Application Deployment & Security
Containerization: Docker & Kubernetes Basics
Confusing VMs with containers: VMs virtualize hardware and run a full OS; containers share the host OS kernel.
Application Deployment & Security
Containerization: Docker & Kubernetes Basics
Thinking Docker is a replacement for Kubernetes: Docker runs individual containers, Kubernetes orchestrates many containers.
Application Deployment & Security
Containerization: Docker & Kubernetes Basics
Underestimating the importance of container images: They are the immutable blueprints for your applications.
Application Deployment & Security
Continuous Integration (CI)
Frequent merging of code changes into a central repository, followed by automated builds and tests.
Application Deployment & Security
Continuous Delivery (CD)
Extends CI to ensure software is always in a deployable state, ready for manual release to production.
Application Deployment & Security
Continuous Deployment (CD)
Extends Continuous Delivery by automatically deploying every change to production after passing all tests.
Application Deployment & Security
CI/CD Pipeline
An automated workflow that orchestrates the entire software delivery process from code commit to deployment.
Application Deployment & Security
Artifact
A deployable component created by the build process, such as a compiled binary or Docker image.
Application Deployment & Security
Automated Testing
Running tests (unit, integration, etc.) automatically within the pipeline to ensure code quality.
Application Deployment & Security
CI/CD Concepts and Pipelines
CI/CD: 'Can I Deploy? Certainly, Dude!' – CI (Can I) integrates and tests, CD (Certainly, Dude) delivers or deploys.
Application Deployment & Security
CI/CD Concepts and Pipelines
The exam expects you to differentiate between Continuous Delivery and Continuous Deployment. Remember: Delivery means 'ready to deploy' (manual step), Deployment means 'automatically deployed' (no manual step). Keywords like 'automated release' usually point to Continuous Deployment.
Application Deployment & Security
CI/CD Concepts and Pipelines
Confusing Continuous Delivery with Continuous Deployment: Delivery means 'ready to go to production,' Deployment means 'automatically goes to production.'
Application Deployment & Security
CI/CD Concepts and Pipelines
Neglecting comprehensive automated testing: A CI/CD pipeline is only as good as its tests; without them, you're just automating bad code to production.
Application Deployment & Security
CI/CD Concepts and Pipelines
Ignoring feedback loops: CI/CD isn't just one-way. Monitoring and feedback are crucial to continuously improve the process and the software.
Application Deployment & Security
OWASP Top 10
List of the most critical web application security risks.
Application Deployment & Security
Least Privilege
Granting only the minimum necessary permissions to users/systems.
Application Deployment & Security
Defense in Depth
Employing multiple layers of security controls to protect assets.
Application Deployment & Security
SAST
Static Application Security Testing; analyzes code without running it.
Application Deployment & Security
DAST
Dynamic Application Security Testing; tests running applications.
Application Deployment & Security
Threat Modeling
Structured approach to identify, quantify, and mitigate security risks.
Application Deployment & Security
Application Security Best Practices
SQL INJECTION: Never Trust User Input! Always Sanitize, Parameterize, and Validate!
Application Deployment & Security
Application Security Best Practices
The exam often tests your knowledge of common attack types and their prevention. Pay close attention to SQL Injection, Cross-Site Scripting (XSS), and Broken Authentication. Know that input validation and output encoding are key defenses.
Application Deployment & Security
Application Security Best Practices
Assuming security is only the job of the security team, not developers.
Application Deployment & Security
Application Security Best Practices
Delaying security testing until the very end of the development cycle.
Application Deployment & Security
Application Security Best Practices
Hardcoding sensitive information like API keys or database credentials directly into application code.
Application Deployment & Security
Secrets
Sensitive data like API keys, passwords, certs.
Application Deployment & Security
MFA
Multi-Factor Authentication; multiple verification factors.
Application Deployment & Security
API Key
Token for app-to-API authentication.
Application Deployment & Security
OpenID Connect
Identity layer built on OAuth 2.0.
Application Deployment & Security
Authentication, Authorization & Secrets Management
AuthN (Authentication) is 'N-ter the system.' AuthZ (Authorization) is 'Z-ealous about permissions.'
Application Deployment & Security
Authentication, Authorization & Secrets Management
The exam often tests the distinction between authentication and authorization, and the importance of secure secrets management. Look for keywords like 'verify identity' (authentication) vs. 'grant access/permissions' (authorization). Be prepared to identify insecure practices for handling credentials.
Application Deployment & Security
Authentication, Authorization & Secrets Management
Confusing authentication with authorization (they are distinct concepts).
Application Deployment & Security
Authentication, Authorization & Secrets Management
Hardcoding sensitive credentials directly into application code or committing them to public repositories.
Application Deployment & Security
Authentication, Authorization & Secrets Management
Using weak or default passwords for API keys or service accounts.
Application Deployment & Security
Network Programmability
Managing network devices via software using APIs.
Infrastructure Automation & Programmability
API
Application Programming Interface; a set of rules for software interaction.
Infrastructure Automation & Programmability
Orchestrator
A system that coordinates multiple automated tasks and systems.
Infrastructure Automation & Programmability
Controller
A central component managing and configuring network devices.
Infrastructure Automation & Programmability
Declarative Configuration
Defining desired state, not step-by-step instructions.
Infrastructure Automation & Programmability
Imperative Configuration
Providing explicit, step-by-step instructions for devices.
Infrastructure Automation & Programmability
Data Model
A structured representation of configuration and operational data.
Infrastructure Automation & Programmability
Network Programmability Concepts
API: 'A Powerful Interface' – it's how programs talk to the network!
Infrastructure Automation & Programmability
Network Programmability Concepts
The exam often contrasts traditional CLI management with programmable network approaches. Look for keywords like 'automation,' 'APIs,' 'orchestration,' and 'centralized control' to identify programmable solutions. Memorize that APIs are the fundamental enablers.
Infrastructure Automation & Programmability
Network Programmability Concepts
Confusing network programmability with simply scripting CLI commands; programmability implies using structured APIs.
Infrastructure Automation & Programmability
Network Programmability Concepts
Believing programmability completely replaces human network engineers; it augments their capabilities, allowing them to focus on higher-level tasks.
Infrastructure Automation & Programmability
Network Programmability Concepts
Thinking all network devices support the same APIs; vendor implementations and supported API styles can vary.
Infrastructure Automation & Programmability
Agentless
No special software required on managed nodes.
Infrastructure Automation & Programmability
Playbook
YAML file in Ansible defining automation tasks.
Infrastructure Automation & Programmability
Manifest
Puppet DSL file describing desired system state.
Infrastructure Automation & Programmability
Cookbook
Ruby files in Chef defining infrastructure config.
Infrastructure Automation & Programmability
Desired State
The intended, consistent configuration of a system.
Infrastructure Automation & Programmability
Push Model
Control node sends configurations to managed nodes.
Infrastructure Automation & Programmability
Pull Model
Managed nodes request configurations from a central server.
Infrastructure Automation & Programmability
Automation Tools: Ansible, Puppet, Chef
To remember the primary language/format: 'A-Y-P-D-C-R' — Ansible-YAML, Puppet-DSL, Chef-Ruby. It sounds like a secret code!
Infrastructure Automation & Programmability
Automation Tools: Ansible, Puppet, Chef
The exam often asks to distinguish between agent-based and agentless tools. Remember Ansible is agentless, while Puppet and Chef are agent-based. Also, know their primary configuration definition formats: YAML for Ansible, Puppet DSL for Puppet, and Ruby for Chef.
Infrastructure Automation & Programmability
Automation Tools: Ansible, Puppet, Chef
Confusing Ansible's agentless nature with Puppet/Chef's agent-based model.
Infrastructure Automation & Programmability
Automation Tools: Ansible, Puppet, Chef
Incorrectly identifying the primary language/format for defining configurations (e.g., saying Puppet uses YAML).
Infrastructure Automation & Programmability
Automation Tools: Ansible, Puppet, Chef
Assuming all configuration management tools use a push model; remember Puppet and Chef use a pull model.
Infrastructure Automation & Programmability
Infrastructure as Code (IaC)
Managing infrastructure using code, not manual processes.
Infrastructure Automation & Programmability
Declarative IaC
Specifies desired end state; tool determines steps.
Infrastructure Automation & Programmability
Imperative IaC
Specifies exact steps to achieve a state.
Infrastructure Automation & Programmability
Infrastructure as Code & Data Models (YANG)
YANG is like a 'Yummy, Accurate, Network Grammar' – it defines the precise syntax and structure for all your network data, making it delicious for machines to consume!
Infrastructure Automation & Programmability
Infrastructure as Code & Data Models (YANG)
The exam often tests your understanding of YANG's purpose and its relationship with NETCONF/RESTCONF. Remember, YANG defines the *structure* of the data, while NETCONF/RESTCONF are the *protocols* that transport that structured data to/from devices.
Infrastructure Automation & Programmability
Infrastructure as Code & Data Models (YANG)
Confusing YANG with a protocol: YANG is a data modeling language, not a communication protocol itself. Protocols like NETCONF and RESTCONF use YANG models.
Infrastructure Automation & Programmability
Infrastructure as Code & Data Models (YANG)
Thinking IaC is only for servers: IaC applies equally to network devices, security appliances, and cloud resources.
Infrastructure Automation & Programmability
Infrastructure as Code & Data Models (YANG)
Underestimating the importance of data models: Without structured data, automation is fragile and difficult to scale.
Infrastructure Automation & Programmability
gRPC
High-performance RPC framework using Protocol Buffers and HTTP/2.
Infrastructure Automation & Programmability
Telemetry
Automated, real-time data collection from network devices.
Infrastructure Automation & Programmability
Protocol Buffers
Language-neutral, platform-neutral serialization for structured data.
Infrastructure Automation & Programmability
Streaming Telemetry
Push-based data collection for real-time network insights.
Infrastructure Automation & Programmability
NETCONF, RESTCONF, gRPC, and Telemetry
NETCONF is 'Nifty XML' over 'Secure SHell'. RESTCONF is 'RESTful JSON' over 'HTTP Secure'. gRPC is 'Google's Rapid Protocol' for 'Streaming Data'.
Infrastructure Automation & Programmability
NETCONF, RESTCONF, gRPC, and Telemetry
The exam often asks you to distinguish between NETCONF and RESTCONF based on their transport protocols (SSH vs. HTTPS) and data encoding (XML vs. JSON/XML). Also, know that gRPC uses Protocol Buffers and HTTP/2 for high-performance streaming.
Infrastructure Automation & Programmability
NETCONF, RESTCONF, gRPC, and Telemetry
Confusing NETCONF's XML-only data encoding with RESTCONF's support for both XML and JSON.
Infrastructure Automation & Programmability
NETCONF, RESTCONF, gRPC, and Telemetry
Assuming SNMP can provide the same real-time, high-frequency data as streaming telemetry.
Infrastructure Automation & Programmability
NETCONF, RESTCONF, gRPC, and Telemetry
Mixing up the transport protocols: NETCONF primarily uses SSH, while RESTCONF uses HTTPS, and gRPC uses HTTP/2.
Infrastructure Automation & Programmability
OSI Model
A 7-layer conceptual framework for network communication.
Network Fundamentals for Developers
TCP/IP Stack
A 4-layer practical protocol suite that powers the Internet.
Network Fundamentals for Developers
Encapsulation
Adding header information to data as it moves down the stack.
Network Fundamentals for Developers
Protocol
A set of rules governing data communication.
Network Fundamentals for Developers
Application Layer
The layer where user applications interact with the network.
Network Fundamentals for Developers
Transport Layer
Provides end-to-end communication and reliability (TCP/UDP).
Network Fundamentals for Developers
Network Layer
Handles logical addressing and routing across networks (IP).
Network Fundamentals for Developers
Data Link Layer
Manages physical addressing and error detection on a segment.
Network Fundamentals for Developers
OSI Model & TCP/IP Stack
To remember the OSI layers from top to bottom: 'Please Do Not Throw Sausage Pizza Away' (Physical, Data Link, Network, Transport, Session, Presentation, Application).
Network Fundamentals for Developers
OSI Model & TCP/IP Stack
The DevNet Associate exam frequently asks about the mapping between OSI and TCP/IP layers. Memorize which OSI layers correspond to each TCP/IP layer, especially the Application and Network Access layers of TCP/IP.
Network Fundamentals for Developers
OSI Model & TCP/IP Stack
Confusing the OSI Model (conceptual) with the TCP/IP Stack (implemented protocols).
Network Fundamentals for Developers
OSI Model & TCP/IP Stack
Incorrectly mapping OSI layers to TCP/IP layers, especially the combined layers.
Network Fundamentals for Developers
OSI Model & TCP/IP Stack
Believing that the OSI Model is actively used for protocol development today, rather than as a reference.
Network Fundamentals for Developers
IP Address
Numerical label identifying a device on a network.
Network Fundamentals for Developers
IPv4
32-bit IP address, dotted-decimal format.
Network Fundamentals for Developers
IPv6
128-bit IP address, hexadecimal format, larger address space.
Network Fundamentals for Developers
Router
Device forwarding data packets between different networks (Layer 3).
Network Fundamentals for Developers
Switch
Device connecting devices within a single LAN (Layer 2).
Network Fundamentals for Developers
MAC Address
Physical address unique to a network interface card.
Network Fundamentals for Developers
Default Gateway
Router's IP address that traffic leaves the local network through.
Network Fundamentals for Developers
ARP
Protocol resolving IP addresses to MAC addresses on a local network.
Network Fundamentals for Developers
IP Addressing, Routing, and Switching Basics
Rout3rs at Layer 3, Swit2hes at Layer 2. The number in the device name matches the OSI layer it primarily works on!
Network Fundamentals for Developers
IP Addressing, Routing, and Switching Basics
The exam frequently distinguishes between IPv4 and IPv6, focusing on their address formats and the reason for IPv6's creation. Also, know that routers operate at Layer 3 (Network) and switches at Layer 2 (Data Link) of the OSI model.
Network Fundamentals for Developers
IP Addressing, Routing, and Switching Basics
Confusing the roles of a router and a switch; routers connect networks, switches connect devices within a network.
Network Fundamentals for Developers
IP Addressing, Routing, and Switching Basics
Not understanding that IP addresses are logical and can change, while MAC addresses are physical and permanent for a NIC.
Network Fundamentals for Developers
IP Addressing, Routing, and Switching Basics
Forgetting the address format differences between IPv4 (dotted-decimal) and IPv6 (hexadecimal).
Network Fundamentals for Developers
Wi-Fi
Wireless networking technology based on IEEE 802.11 standards.
Network Fundamentals for Developers
WAP
Wireless Access Point; device that allows Wi-Fi devices to connect to a wired network.
Network Fundamentals for Developers
WPA2
Wi-Fi Protected Access 2; a strong wireless security protocol using AES encryption.
Network Fundamentals for Developers
Firewall
Network security system that controls traffic based on security rules.
Network Fundamentals for Developers
VPN
Virtual Private Network; creates a secure, encrypted connection over public networks.
Network Fundamentals for Developers
Malware
Malicious software designed to disrupt, damage, or gain unauthorized access.
Network Fundamentals for Developers
Confidentiality
Ensuring data is accessible only to authorized individuals.
Network Fundamentals for Developers
Integrity
Maintaining the accuracy and consistency of data over its lifecycle.
Network Fundamentals for Developers
Wireless Concepts & Network Security Basics
CIA: Confidentiality, Integrity, Availability – the three pillars of network security. Remember it like a secret agent's job!
Network Fundamentals for Developers
Wireless Concepts & Network Security Basics
The DevNet Associate exam expects you to know the difference between WEP, WPA, WPA2, and WPA3, and why WPA2/WPA3 are preferred. Focus on the core security principles (CIA triad) and the basic function of firewalls and VPNs.
Network Fundamentals for Developers
Wireless Concepts & Network Security Basics
Using WEP or WPA (instead of WPA2/WPA3) for wireless security, which are easily compromised.
Network Fundamentals for Developers
Wireless Concepts & Network Security Basics
Neglecting to update firmware on WAPs and routers, leaving them vulnerable to known exploits.
Network Fundamentals for Developers
Wireless Concepts & Network Security Basics
Assuming a firewall alone provides complete network security; it's one piece of a larger strategy.
Network Fundamentals for Developers
Ping
Utility to test reachability of a host on an IP network.
Network Fundamentals for Developers
Traceroute
Utility to display the path and measure transit delays of packets.
Network Fundamentals for Developers
IPConfig
Windows command to display current TCP/IP network configuration.
Network Fundamentals for Developers