Appendix D. Chapter Quiz Answers

This appendix consolidates the answer keys and concise rationales for the practice quizzes that accompany each chapter, providing a fast way to verify understanding and revisit core concepts without rereading full sections. Each item pairs the correct choice with a sentence or two explaining why it’s right (and often why tempting distractors are not), while pointing learners back to the originating chapter for deeper study. The coverage is intentionally broad, spanning foundational device roles, models, and media through advanced switching, routing, security, wireless, and automation topics that map closely to the CCNA exam blueprint.

The material reinforces layer-by-layer fundamentals (cabling limits, Auto MDI-X, Ethernet framing, MAC learning, ARP, broadcast versus unknown unicast behavior), the TCP/IP model and encapsulation, IPv4/IPv6 addressing and subnetting, and the mechanics of forwarding (longest-prefix match, ECMP, static versus dynamic routes, metrics and administrative distance). It ties these to campus switching skills—VLANs and trunks (native/allowed VLANs, DTP/VTP), loop prevention and recovery (STP/RSTP roles and timers), EtherChannel formation and consistency—and to routing concepts and services (OSPF roles and elections, default routes, router-on-a-stick inter-VLAN routing, FHRPs like HSRP/VRRP/GLBP). Operational know‑how is threaded throughout: IOS modes and file storage, saving and securing configs (enable secret, service password-encryption), interface defaults and troubleshooting counters, common transport ports and behaviors (TCP/UDP), along with essential network services and tools (NTP, DNS, DHCP, CDP/LLDP, Syslog, SNMP, TFTP/FTP, NAT, QoS queues/markings).

Security and wireless are treated pragmatically: standard and extended ACL placement and syntax, campus protections (Port Security, DHCP Snooping, Dynamic ARP Inspection), core concepts (CIA, AAA, 802.1X), and best practices (non-default native VLAN, hashed credentials). Wireless sections clarify RF effects, bands and channels (2.4/5/6 GHz planning), identifiers (SSID/BSSID), controller-based designs (LWAP/WLC, CAPWAP, FlexConnect), and security progressions from WEP/TKIP to WPA2/WPA3 (CCMP/GCMP, SAE, forward secrecy). Broader architecture and modernization topics round it out—LAN and spine–leaf designs, MPLS and VPN types (IPsec, GRE, DMVPN), virtualization and cloud models (hypervisors, VRF, IaaS/SaaS), SDN/DNAC planes and APIs, REST semantics and HTTP codes, plus data formats (JSON, YAML, XML). Across all domains the appendix highlights defaults, command syntax, and test‑worthy behaviors, making it a concise checkpoint for revision and a map back to fuller explanations when needed.

• 1. Which of the following statements about Ansible are true? (select two)
• A: Ansible is written in Python.
• D: The Ansible control node connects to port 22 of managed devices.
• Ansible is written in Python and employs an agentless model in which it uses SSH (TCP port 22) to connect to managed devices. Unlike Puppet and Chef, Ansible uses a push model; the Ansible control node pushes configurations to managed devices, instead of managed devices retrieving configurations from the control node.
• 2. Which of the following statements about Puppet are true? (select two)
• A: Puppet is written in Ruby.
• B: Puppet agents connect to port 8140 on the Puppet master.
• Puppet is written in Ruby. Unlike Ansible, Puppet is agent-based and employs a pull model in which the Puppet agent on managed devices connects to the REST API (TCP port 8140) on the Puppet master to retrieve configurations.
• 3. Which language are most Ansible files written in?
• B: YAML
• Most Ansible files, including inventory and playbook files, are written in YAML , which is popular for its readability and ease of use.
• 4. Which of the following statements about Chef are true? (select two)
• B: Chef uses a pull model.
• C: A Chef client must be installed on managed devices.
• Like Puppet, Chef is agent-based and requires an agent called the “Chef client” to be installed on managed devices. It also uses a pull model, in which the Chef client connects to the Chef server’s REST API to retrieve configurations.
• 5. What kind of file are Puppet resources and classes written into?
• B: Manifest
• In Puppet, resources and classes are defined in manifest files. These files describe the desired state of the system using Puppet's declarative language.
• 6. Which statements about Puppet’s DSL are true? (select two)
• B: It can perform complex tasks with less effort than general languages.
• C: It is a declarative language.
• Puppet uses a domain-specific language (DSL)—a type of computer language specialized for a particular purpose, unlike general-purpose languages like Python or Ruby. Puppet’s DSL is declarative, meaning that it specifies the desired outcome rather than the specific procedures to achieve that outcome. It can often perform complex tasks with much less effort than a general language would require.
• 7. Which of the following configuration management tools use an agent-based model? (select two)
• A: Puppet
• C: Chef
• Both Puppet and Chef use an agent-based model where agents installed on managed devices communicate with a central server (Puppet master or Chef server) to retrieve configuration information and apply it.
• 8. Which Ansible file defines automation tasks to manage configuration on managed devices?
• C: Playbook
• In Ansible, playbooks are the primary files where automation tasks are defined. Playbooks are written in YAML and describe the configurations of managed devices.

FAQ