Leaving out an SSH prerequisite or leaving Telnet open
The wrong answers omit something SSH needs or leave Telnet permitted. The RSA key label is built from the hostname and the domain name, so a default hostname with no ip domain-name stops key generation. SSH version 2 needs a key of at least 768 bits, so a 512-bit or 256-bit modulus fails. On the VTY lines, transport input all and transport input telnet still allow clear text, and transport input none blocks everything. Only transport input ssh gives encrypted-only access.
See it in a sample questionSwapping the transports and logins of TFTP and FTP
The wrong answers swap the transports and the login rules of the two file-transfer protocols. TFTP runs over connectionless UDP on port 69 and carries no authentication. FTP runs over TCP, uses ports 20 and 21, and checks a username and password. SCP is a separate protocol that relies on an authenticated SSH session, and HTTPS adds TLS over TCP. A no-login, connectionless transfer of an IOS image points to TFTP.
See it in a sample questionCrediting the wrong SNMP feature with delivery or security
The wrong answers credit the wrong SNMP feature with delivery confirmation or security. A trap is unacknowledged, while an inform is acknowledged by the manager, so only an inform confirms delivery. SNMPv1 and SNMPv2c authenticate with clear-text community strings and give no encryption. SNMPv3 authNoPriv authenticates without encrypting, and authPriv adds encryption. Security level and message type are separate choices, so authPriv does not make notifications acknowledged.
See it in a sample questionAttaching NAT address terms to the wrong host
The wrong answers attach the NAT address terms to the wrong host or the wrong end of the mapping. The inside local address is the private address the host uses, and the inside global address is the registered public address that represents it to the outside. In inside source static, the inside local address is written first and the inside global second. In a PAT table the inside global column shows the shared public address and translated port the server sees, not the inside local socket.
See it in a sample questionConfusing shaping with policing for a rate limit
The wrong answers swap shaping and policing, or offer marking, classification or WRED for a rate problem. Shaping buffers excess traffic and releases it smoothly, which reduces drops and TCP retransmissions. Policing has no queue: it drops or remarks the excess immediately, so it imposes a hard ceiling with no queuing delay but reproduces the drops. Marking and classification only label traffic, and WRED drops early rather than capping a rate.
See it in a sample question