Práctica Cisco DevNet Associate

REST APIs use HTTP methods to exchange resources. Databases, cables, and firewall rules are not APIs.

JSON is a text-based data format used in APIs. It is not a programming language, routing protocol, or device.

YAML is used for configuration and automation files. It is not a database engine, switch model, or DNS record.

Version control tracks changes, branches, and history. Firewalls, load balancers, and tapes are different.

Git is a distributed version control system. Web servers, protocols, and databases are different.

A repository stores code, branches, and commit history. Routers, firewalls, and subnets are network objects.

Branches let developers work independently. Network segments, volumes, and DNS zones are different.

Merging integrates branch changes. Deleting repos, creating VLANs, and encrypting are different.

Commits capture changes in history. Packets, firewall rules, and DNS queries are unrelated.

REST APIs use HTTP, JSON exchanges data, Git controls versions, and repositories store code.

GET retrieves resources without side effects. POST creates, DELETE removes, and PUT updates.

POST creates resources on a server. GET retrieves, DELETE removes, and PUT updates.

PUT updates or replaces a resource. GET retrieves, DELETE removes, and logs record events.

DELETE removes a resource. POST creates, GET reads, and PUT updates.

200 means the request succeeded. 404 is not found, 500 is server error, and 401 is unauthorized.

404 means the requested resource was not found. 200 is OK, 201 is created, and 3xx redirects.

API keys identify clients making requests. Indexes, addresses, and firewall rules are different.

OAuth 2.0 allows delegated authorization. Routing protocols, formats, and switch models are different.

Webhooks push event notifications over HTTP. DNS records, cables, and backups are unrelated.

GET retrieves, POST creates, 404 is not found, and webhooks notify events.

Ansible automates configuration and provisioning. Switches, databases, and firewalls are not automation tools.

Playbooks define tasks in YAML. Routing tables, DNS zones, and VMs are different.

Terraform manages infrastructure declaratively. Protocols, formats, and switches are different.

Modules are reusable automation units. Cables, volumes, and DNS records are not modules.

Idempotent operations can be repeated without harmful changes. Encryption, scaling, and routing are different.

DNA Center exposes APIs for network management and automation. Protocols, storage, and DNS are different.

Meraki APIs manage cloud networks. Switch models, formats, and firewall rules are different.

Controllers centralize network management. Cables, subnets, and DNS records are different.

Intent-based networking translates business intent into network policy. Manual config, static routes only, and no automation are not intent-based.

Ansible automates config, Terraform manages infrastructure, DNA Center manages campus networks, and Meraki manages cloud networks.

IP addresses identify devices at Layer 3. MAC addresses are hardware, and passwords or cables are different.

MAC addresses are burned into interfaces. IP addresses are logical, and DNS records or firewalls are different.

Switches connect LAN devices and forward frames. Routers connect networks, DNS resolves names, and encryption protects data.

Routers forward packets between networks. Switches connect LANs, and storage or printing are unrelated.

VLANs segment traffic logically. Cables, DNS zones, and firewalls are different.

Subnets divide IP ranges. Ports, DNS records, and backups are different.

DNS translates names to addresses. DHCP assigns addresses, firewalls filter, and encryption protects.

DHCP assigns IP configuration to clients. DNS resolves names, routers forward, and firewalls filter.

Firewalls permit or block traffic. DNS resolves, DHCP assigns, and storage stores.

Switches connect LANs, routers forward between networks, DNS resolves names, and DHCP assigns addresses.

Unit tests verify individual components. Full-system tests are integration or end-to-end, and scans or backups are different.

Integration tests verify interactions between components. Unit tests check one function, and rules or queries are unrelated.

Linters catch style and syntax issues. Scanners test networks, compilers build code, and routers forward packets.

Code reviews inspect changes for quality and bugs. Backups, tests, and deployments are different.

Vulnerabilities are exploitable weaknesses. Firewalls protect, patches fix, and DNS records resolve names.

Encryption protects confidentiality. Firewalls filter, DHCP assigns, and DNS resolves.

Authentication verifies identity. Authorization grants permissions, encryption protects, and firewalls filter.

Authorization grants access after authentication. Verification is authentication, and encryption or filtering are different.

Threat models identify risks and mitigations. Rules, zones, and backups are different.

Unit tests verify functions, linters check style, authentication verifies identity, and encryption protects data.

CI automates build and test on changes. Annual deployment, manual testing, or disabling builds are not CI.

CD keeps artifacts ready for release. Deleting releases, manual deploys, and no pipelines are not CD.

Pipelines automate release stages. Routes, firewall rules, and DNS zones are different.

Containers package apps and dependencies. Switches, databases, and DNS records are different.

Docker builds and runs containers. Protocols, firewalls, and formats are different.

Kubernetes orchestrates containers. Databases, switch models, and DNS records are different.

Dockerfiles define image builds. Network configs, DNS zones, and backups are different.

Artifacts are build outputs. Firewall rules, DNS records, and routers are different.

Canary releases test with limited traffic. Deleting old versions, deploying all at once, or disabling monitoring are not canary.

CI/CD automates releases, Docker runs containers, Kubernetes orchestrates, and canary rolls out gradually.