Security Fundamentals

298 soru

Soru 121Soru

Match each Public Key Infrastructure (PKI) component or Multi-Factor Authentication (MFA) element on the left to its corresponding function or definition on the right.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Certificate Signing Request (CSR)
Certificate Authority (CA)
Online Certificate Status Protocol (OCSP)
Time-based One-Time Password (TOTP)

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Certificate Signing Request (CSR) matches the encoded block containing a public key and metadata; Certificate Authority (CA) matches the entity issuing signed certificates; Online Certificate Status Protocol (OCSP) matches the real-time revocation query protocol; Time-based One-Time Password (TOTP) matches the dynamic MFA factor generated using a shared secret and timestamp.
Each item accurately aligns with its standard PKI or security definition: CSR is the initial request containing public key and identity data, CA is the signing body, OCSP is the query protocol for checking revocation status, and TOTP is a time-synchronized dynamic multi-factor credential.

Adım Adım Çözüm

1
Identify the role of a Certificate Signing Request (CSR).
Recognize that a CSR is created by the requester and contains the public key along with subject details destined for a CA.
CSR generation is the initial step in obtaining an X.509 digital certificate.
2
Identify the role of a Certificate Authority (CA).
Associate the CA with the trusted issuer that signs certificates.
The CA establishes trust in PKI by signing certificates with its own private key.
3
Differentiate between certificate validation protocols and authentication mechanisms.
Link OCSP to real-time revocation checks and TOTP to temporary time-based MFA factor generation.
OCSP provides efficient status checks over HTTP, whereas TOTP serves as a possession-based authentication factor.

Anahtar Kavram

PKI Components and MFA Authentication Factors
Soru 122Soru

A network administrator enables DHCP Snooping globally and on VLAN 20. To protect against DHCP denial-of-service (DoS) starvation attacks, the administrator configures `ip dhcp snooping limit rate 15` on all untrusted access interfaces. Shortly after, a user workstation interface transitions into the `err-disabled` state. Which operational behavior explains why this interface was placed into the `err-disabled` state?

Cevabı ve açıklamayı göster

Cevap: The interface received DHCP traffic exceeding the threshold of 15 packets per second configured on the untrusted port.

Cevap

The interface received DHCP traffic exceeding the threshold of 15 packets per second configured on the untrusted port.
Configuring `ip dhcp snooping limit rate` on an untrusted interface imposes a ceiling on incoming DHCP control traffic. If a connected device sends DHCP messages faster than the configured threshold (15 packets per second in this scenario), the switch detects a rate violation and immediately transitions the port to the `err-disabled` state to protect network resources.

Adım Adım Çözüm

1
Identify the Layer 2 security feature and command configured on the interface.
The switch has DHCP Snooping rate limiting configured via `ip dhcp snooping limit rate 15` on untrusted access interfaces.
This command sets a maximum allowed rate of 15 DHCP packets per second on untrusted ports.
2
Analyze the switch response when the rate limit threshold is exceeded.
If an untrusted host sends more than 15 DHCP packets per second, the switch shuts down the port and places it in the err-disabled state.
DHCP Snooping rate limiting enforces traffic ceilings to mitigate DHCP exhaustion/starvation attacks.

Anahtar Kavram

DHCP Snooping Interface Rate Limiting
Soru 123Soru

An organization is updating its administrative access policy for Cisco enterprise network devices. To enforce multi-factor authentication (MFA) for secure SSH management access, network administrators configure AAA authentication to require both a static account password and a one-time passcode (OTP) generated by a physical hardware token fob. Which statement correctly classifies these two authentication controls under standard MFA factor categories?

Cevabı ve açıklamayı göster

Cevap: The static account password is a knowledge factor (something you know), while the hardware token passcode is a possession factor (something you have).

Cevap

The static account password is a knowledge factor (something you know), while the hardware token passcode is a possession factor (something you have).
Multi-Factor Authentication (MFA) enhances security by combining two or more independent credential types: Knowledge (something you know, such as a password or PIN), Possession (something you have, such as a physical hardware token, smart card, or mobile authenticator app), and Inherence (something you are, such as a fingerprint or iris scan). A static password is memorized information (knowledge), whereas a hardware token passcode requires physical ownership of the generating device (possession).

Adım Adım Çözüm

1
Identify the authentication controls presented in the scenario.
Control 1 is a static account password. Control 2 is a temporary passcode generated by a physical hardware token fob.
Categorizing MFA requires identifying the underlying mechanism of each credential.
2
Map each control to standard MFA factor categories: Knowledge (something you know), Possession (something you have), and Inherence (something you are).
The static password relies on memorized secret data (knowledge). The hardware token passcode relies on owning a physical key fob device (possession).
True multi-factor authentication requires using credentials from two or more distinct categories.

Anahtar Kavram

Multi-Factor Authentication (MFA) Factor Categorization
Soru 124Soru

A network administrator is designing an IPv4 security policy and placing Access Control Lists (ACLs) across a corporate router topology. Which two statements accurately describe the operational characteristics and default behaviors of Cisco IPv4 ACLs? (Select two.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Standard IPv4 ACLs inspect only the source IPv4 address of packets and should generally be applied as close to the destination as possible.; Traffic that does not match any explicit permit or deny entry in an ACL is dropped by an invisible implicit deny statement at the end of the list.

Cevap

The correct statements are that standard IPv4 ACLs inspect only the source IPv4 address and should be placed close to the destination, and that unlisted traffic is dropped by the implicit deny statement at the end of the ACL.
Standard IPv4 ACLs evaluate only source IPv4 addresses, making destination-adjacent placement critical to prevent dropping traffic meant for other subnets. Furthermore, every Cisco IPv4 ACL features an unwritten implicit deny clause at the end of its list, which drops any packet that fails to match an explicit entry.

Adım Adım Çözüm

1
Analyze standard IPv4 ACL filtering capabilities and placement guidelines.
Standard IPv4 ACLs filter strictly on source IPv4 addresses. Because they cannot filter on destination IP or ports, placing them close to the destination avoids prematurely dropping traffic intended for other routes.
Correct placement prevents unintended traffic filtering across the network topology.
2
Analyze ACL rule evaluation logic and final default action.
ACL statements are processed sequentially from top to bottom. If no explicit permit or deny rule matches a packet, it hits the implicit deny statement ('deny ip any any') at the end of the ACL and is dropped.
Understanding the implicit deny prevents accidental blocking of legitimate network traffic.

Anahtar Kavram

Standard IPv4 ACL Characteristics and Implicit Deny Behavior
Tahmini Süre:1m 30s
Soru 125Soru

An enterprise security team is evaluating AAA protocol deployments across network devices. The security policy mandates that administrative CLI sessions on core routers must enforce per-command authorization and per-command accounting logs. During testing, the team observes that while RADIUS successfully authenticates incoming user sessions, it fails to perform real-time, per-command authorization checks during an active CLI session. Which architectural characteristic of RADIUS accounts for this limitation?

Cevabı ve açıklamayı göster

Cevap: RADIUS combines authentication and authorization into unified Access-Request and Access-Accept packet exchanges, preventing standalone authorization requests for individual CLI commands.

Cevap

RADIUS combines authentication and authorization within its packet exchanges, making it unable to independently authorize individual CLI commands during an active administration session.
RADIUS is designed primarily for network access control (such as 802.1X and dial-up/VPN access) where authentication and authorization occur simultaneously upon connection. Because RADIUS packages authentication and authorization attributes together inside standard Access-Request and Access-Accept packets, it cannot easily initiate separate, isolated authorization requests for individual CLI commands executed after session establishment. TACACS+, by contrast, completely decouples AAA functions, allowing per-command authorization queries.

Adım Adım Çözüm

1
Analyze the operational requirements for per-command administrative authorization.
Per-command authorization requires a protocol capable of sending separate, real-time authorization requests to the AAA server every time an administrator enters a command at the CLI.
Administrative device access requires granular command control after the initial authentication session is established.
2
Evaluate RADIUS architectural mechanics regarding AAA functional separation.
RADIUS combines authentication and authorization into unified packet exchanges (Access-Request, Access-Accept, Access-Reject).
Because authentication and authorization are coupled, RADIUS is optimized for network access control (e.g., 802.1X, VPNs) rather than per-command administrative authorization.
3
Contrast RADIUS mechanics with TACACS+ to select the correct architectural limitation.
TACACS+ modularly separates Authentication, Authorization, and Accounting, allowing standalone command authorization over TCP port 49 with full payload encryption.
The inability of RADIUS to separate authorization from initial authentication is the exact architectural reason it cannot support per-command authorization.

Anahtar Kavram

AAA Protocol Differences (TACACS+ vs RADIUS Functional Separation)
Soru 126Soru

Match each Cisco Layer 2 security feature or operational state on the left to its corresponding system action or behavior on the right.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Port Security Protect Mode
Port Security Restrict Mode
Dynamic ARP Inspection (DAI)
DHCP Snooping Untrusted Port

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Port Security Protect Mode matches dropping traffic silently without counter increments or log messages. Port Security Restrict Mode matches dropping traffic while incrementing the violation counter and logging. Dynamic ARP Inspection matches validating ARP packets against the DHCP binding database. DHCP Snooping Untrusted Port matches discarding incoming DHCP server packets like DHCPOFFER and DHCPACK.
Each feature is correctly matched to its specific control-plane or data-plane enforcement mechanism: Protect mode drops frames without logging; Restrict mode drops frames with logging and counter increments; Dynamic ARP Inspection verifies ARP packets using the DHCP snooping binding database; untrusted DHCP snooping ports drop inbound server messages (DHCPOFFER/DHCPACK).

Adım Adım Çözüm

1
Analyze Port Security violation modes (Protect vs. Restrict)
Protect mode drops unauthorized MAC traffic silently (no counter increment, no syslog). Restrict mode drops unauthorized traffic, increments the security violation counter, and generates syslog/SNMP alerts.
Differentiating violation modes requires knowing which modes generate alerts and counters versus silent frame drops.
2
Analyze Dynamic ARP Inspection operational requirements
DAI inspects ARP packets on untrusted ports and verifies the MAC-to-IP binding against the switch's DHCP snooping binding table.
DAI relies directly on the DHCP snooping database (or static ARP ACLs) to mitigate ARP poisoning and spoofing attacks.
3
Analyze DHCP Snooping port trust roles
Untrusted ports permit client requests (DHCPDISCOVER/DHCPREQUEST) but drop incoming server responses (DHCPOFFER/DHCPACK).
Preventing rogue DHCP servers requires blocking DHCP server response messages on user-facing untrusted ports.

Anahtar Kavram

Layer 2 Security Mechanisms (Port Security Violation Modes, DAI Operation, DHCP Snooping Trust States)
Soru 127Soru

A network administrator is implementing certificate-based client authentication (EAP-TLS) for 802.1X enterprise wireless access. When an authentication server receives a digital certificate presented by a client device, which two methods or attributes are used by the server to check whether the certificate has been explicitly revoked before its natural expiration date? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Querying an Online Certificate Status Protocol (OCSP) responder via HTTP to obtain real-time certificate status; Downloading and parsing a Certificate Revocation List (CRL) published periodically by the issuing Certificate Authority (CA)

Cevap

The correct methods for checking certificate revocation are querying an Online Certificate Status Protocol (OCSP) responder for real-time status and checking a Certificate Revocation List (CRL) published by the issuing CA.
To verify that a certificate has not been revoked prior to expiration, an authentication server uses either Certificate Revocation Lists (CRLs), which are regularly updated lists of revoked serial numbers published by the CA, or Online Certificate Status Protocol (OCSP), which provides real-time revocation status checks over HTTP.

Adım Adım Çözüm

1
Identify the primary mechanisms used in Public Key Infrastructure (PKI) to track and check revoked digital certificates.
The standard PKI mechanisms for revocation checking are CRLs (time-based list files) and OCSP (real-time protocol queries).
When a private key is compromised or a certificate is prematurely retired, the CA marks it as revoked via CRL or OCSP.
2
Evaluate the function of Certificate Revocation Lists (CRLs).
A CRL contains a list of serial numbers of revoked certificates published periodically to a Certificate Distribution Point (CDP).
Authentication servers download the list from the CDP to verify the client certificate serial number is not listed.
3
Evaluate the function of Online Certificate Status Protocol (OCSP).
OCSP performs an online query to check the revocation status of a specific certificate without downloading a full list.
This allows immediate, real-time revocation verification during dynamic EAP-TLS authentication.

Anahtar Kavram

Digital Certificate Revocation Checking (CRL and OCSP)
Soru 128Soru

An administrator configures the following IPv4 extended named access control list on a Cisco IOS router:

text
ip access-list extended BLOCK_WEB_SERVICES
deny tcp 10.20.30.0 0.0.0.255 host 192.168.100.10 eq 80
deny tcp 10.20.30.0 0.0.0.255 host 192.168.100.10 eq 443

This ACL is applied inbound on interface GigabitEthernet0/0. A host with IP address 10.20.30.15 attempts to send ICMP echo request packets to 192.168.100.10. What occurs when this ICMP traffic reaches the router interface?

Cevabı ve açıklamayı göster

Cevap: The ICMP traffic is dropped because it encounters the implicit deny all statement at the end of the ACL.

Cevap

The ICMP traffic is dropped because it encounters the implicit deny all statement at the end of the ACL.
Cisco IPv4 Access Control Lists evaluate entries sequentially from top to bottom. If a packet does not match any explicit permit or deny entry in the list, it hits the unwritten implicit deny clause ('deny ip any any') at the end of the ACL. Since the ACL only contains explicit deny entries for TCP ports 80 and 443, ICMP packets fail to match those specific lines and are dropped by the implicit deny.

Adım Adım Çözüm

1
Evaluate the first entry (seq 10 / line 1) against the packet.
Packet is ICMP from 10.20.30.15 to 192.168.100.10. Line 1 checks for TCP port 80 traffic. No match occurs.
Protocol mismatch (ICMP vs TCP).
2
Evaluate the second entry (seq 20 / line 2) against the packet.
Line 2 checks for TCP port 443 traffic. No match occurs.
Protocol mismatch (ICMP vs TCP).
3
Evaluate the implicit default behavior at the bottom of the ACL.
Every Cisco IOS IPv4 ACL ends with an unwritten 'deny ip any any' rule. The ICMP packet matches this implicit rule.
Traffic not explicitly permitted is denied by default.

Anahtar Kavram

Every IPv4 ACL in Cisco IOS concludes with an invisible implicit deny statement ('deny ip any any'). To permit non-denied traffic, an explicit permit statement (such as 'permit ip any any') must be added.
Soru 129Soru

A network administrator configures port security on access interface GigabitEthernet0/10 of a Cisco Catalyst switch using the command `switchport port-security mac-address sticky`. Over the next week, several workstations connect to the port, and their MAC addresses are dynamically added to the running configuration. Following an unscheduled power outage and switch reboot, the administrator discovers that the connected workstations are unable to gain access and port security sticky entries are missing from the configuration. What was the root cause of this issue?

Cevabı ve açıklamayı göster

Cevap: The administrator did not save the running configuration to the startup configuration after the sticky MAC addresses were learned.

Cevap

The administrator did not save the running configuration to the startup configuration after the sticky MAC addresses were learned.
When port security is configured with the sticky keyword, dynamically learned MAC addresses are converted into static-like entries and placed directly into the running configuration in RAM. Because RAM is volatile memory, any dynamic sticky entries learned while the switch is operational will be completely lost upon a switch reboot unless the administrator manually executes `copy running-config startup-config` (or `write memory`) to copy the running configuration into non-volatile storage (NVRAM).

Adım Adım Çözüm

1
Analyze how sticky MAC addressing operates in Cisco Port Security.
When `switchport port-security mac-address sticky` is configured, the switch dynamically learns MAC addresses and adds them to the active running configuration file (`running-config`) as static entries.
Understanding where learned sticky addresses are saved during active operation.
2
Evaluate memory persistence across switch reboots.
The `running-config` resides in volatile RAM. If the switch reboots before `copy running-config startup-config` or `write memory` is executed, any dynamically added sticky MAC lines in RAM are lost.
Determining why sticky MAC entries disappeared after the reboot.
3
Identify the required administrative action to preserve sticky MACs.
Saving the running configuration commits the dynamically learned sticky MAC lines to NVRAM (`startup-config`), ensuring persistence across power cycles.
Pinpointing the missing step causing the loss of network access.

Anahtar Kavram

Port Security Sticky MAC Address Persistence
Tahmini Süre:1m 15s
Soru 130Soru

A network administrator is creating an IPv4 extended Access Control List (ACL) on a Cisco IOS router to regulate traffic flowing from internal hosts to the DMZ subnet (172.16.1.0/24172.16.1.0/24). The ACL must enforce the following policy requirements in order of precedence:

1. Allow HTTP traffic from any host in the internal subnet (192.168.10.0/24192.168.10.0/24) to the web server at 172.16.1.50172.16.1.50.
2. Block all other IP traffic from host 192.168.10.15192.168.10.15 to the DMZ subnet (172.16.1.0/24172.16.1.0/24).
3. Allow all remaining IP traffic from the internal subnet (192.168.10.0/24192.168.10.0/24) to the DMZ subnet (172.16.1.0/24172.16.1.0/24).
4. Explicitly deny all other traffic.

Arrange the given ACL statements in the correct top-down execution order to achieve this security policy without unintended traffic drops.

Öğeleri doğru sıraya koymak için sürükleyin

Cevabı ve açıklamayı göster

Cevap

The correct sequential order for the access list statements from top to bottom is: permit tcp 192.168.10.0 0.0.0.255 host 172.16.1.50 eq 80, followed by deny ip host 192.168.10.15 172.16.1.0 0.0.0.255, followed by permit ip 192.168.10.0 0.0.0.255 172.16.1.0 0.0.0.255, and ending with deny ip any any.
Cisco IPv4 Access Control Lists evaluate rules sequentially from top to bottom. Specific exceptions must precede broader policy rules. The rule permitting HTTP traffic from 192.168.10.0/24 to 172.16.1.50 must be placed first so HTTP requests from host 192.168.10.15 are allowed. Next, the statement denying all IP traffic from host 192.168.10.15 to the DMZ network must be placed to filter out non-HTTP traffic from that specific host. Third, the broader subnet permit statement allows other hosts on 192.168.10.0/24 to access the DMZ network. Finally, the explicit deny statement is placed at the bottom.

Adım Adım Çözüm

1
Identify specific host and protocol exemptions.
HTTP traffic (TCP port 80) from host 192.168.10.15 to host 172.16.1.50 must be permitted.
Cisco ACLs process packets sequentially from top to bottom and stop at the first matching statement. If the host deny statement came first, HTTP traffic from 192.168.10.15 would be matched and dropped immediately.
2
Place specific deny statements for targeted hosts after specific permits but before general permits.
Position 'deny ip host 192.168.10.15 172.16.1.0 0.0.0.255' second.
This blocks any non-HTTP traffic from host 192.168.10.15 before reaching the general subnet permit rule.
3
Place general subnet-to-subnet permit statements.
Position 'permit ip 192.168.10.0 0.0.0.255 172.16.1.0 0.0.0.255' third.
This allows all remaining valid hosts on the 192.168.10.0/24 network to communicate with the DMZ network.
4
Add the explicit deny catch-all statement.
Position 'deny ip any any' fourth.
Completes the ACL structure and enforces standard explicit filtering at the end of the access list.

Anahtar Kavram

Access Control List Top-Down Sequential Processing and Rule Specificity
Soru 131Soru

A network administrator is implementing Layer 2 security controls on an access switch, configuring Port Security with sticky MAC address learning alongside DHCP Snooping on edge switch ports. Which two statements correctly describe the operational behavior of these features? (Select two.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Dynamically learned sticky MAC addresses are added directly to the running configuration in RAM.; DHCP server response messages, such as DHCPOFFER and DHCPACK, are dropped when received on an untrusted port.

Cevap

The correct answers state that dynamically learned sticky MAC addresses are appended to the running configuration in RAM, and that DHCP server messages (such as DHCPOFFER and DHCPACK) arriving on untrusted ports are dropped by DHCP Snooping.
When port security sticky learning is configured, learned MAC addresses are converted into static-like MAC entries directly in the running-config in active RAM. Additionally, DHCP Snooping enforces boundary security by designating access interfaces as untrusted by default, dropping any DHCP server messages (such as DHCPACK or DHCPOFFER) that attempt to enter an untrusted interface.

Adım Adım Çözüm

1
Analyze Port Security sticky MAC behavior
Confirm that sticky MAC learning dynamically populates the running configuration in RAM, which requires a manual save to startup configuration to persist across reboots.
Sticky MAC addresses act as static entries in running-config, but RAM is volatile memory.
2
Analyze DHCP Snooping port trust rules
Confirm that untrusted ports are only permitted to send DHCP requests from clients, while server responses (DHCPACK, DHCPOFFER) are intercepted and dropped.
Untrusted ports represent client-facing links, preventing rogue DHCP servers from handing out invalid addresses.

Anahtar Kavram

Port Security Sticky MAC Persistence and DHCP Snooping Trust Verification
Soru 132Soru

An organization is updating its enterprise security standards for administrative access and infrastructure security. Match each security control or PKI concept on the left to its corresponding operational function on the right.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Account Lockout Threshold
Possession Factor
Certificate Signing Request (CSR)
Certificate Revocation List (CRL)

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Account Lockout Threshold matches the control defining maximum failed attempts before disabling an account. Possession Factor matches identity verification using a physical or digital token. Certificate Signing Request (CSR) matches submitting a public key and identity info to a CA. Certificate Revocation List (CRL) matches the periodically published list of revoked certificate serial numbers.
The correct pairings accurately map security terms to their standard definitions. Account Lockout Threshold controls brute-force password attacks by disabling accounts after failed attempts. Possession Factor represents 'something you have' such as a TOTP token app. CSR represents the enrollment request payload sent to a CA containing the public key. CRL represents the list of invalidated certificate serial numbers published by a CA.

Adım Adım Çözüm

1
Analyze the password policy control mechanism.
Identify that Account Lockout Threshold limits failed login attempts to protect administrative accounts from brute-force attacks.
Password security policies enforce lockout rules after a predefined number of incorrect password attempts.
2
Categorize the multi-factor authentication element.
Map Possession Factor to tangible or digital objects like TOTP hardware tokens or smartphone apps.
MFA requires factors from distinct categories: Knowledge (something you know), Possession (something you have), and Inherence (something you are).
3
Evaluate PKI certificate enrollment components.
Match Certificate Signing Request (CSR) to the payload containing identity info and public key sent to a CA.
Endpoints must generate a local keypair and send a CSR to a Certificate Authority to obtain an X.509 certificate.
4
Evaluate PKI certificate revocation mechanisms.
Match Certificate Revocation List (CRL) to the signed file listing revoked certificate serial numbers.
CAs publish CRLs so relying parties can verify whether a certificate was invalidated prior to its scheduled expiration.

Anahtar Kavram

Password Security Policies, Multi-Factor Authentication (MFA) Factors, and Public Key Infrastructure (PKI) Certificate Components
Soru 133Soru

Match each wireless security deployment mode or protocol with its primary cryptographic cipher suite or key exchange mechanism.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

WPA3-Personal
Standard WPA2-Enterprise
WPA3-Enterprise 192-bit Mode
Enhanced Open (OWE)

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

WPA3-Personal matches Simultaneous Authentication of Equals (SAE) using the Dragonfly handshake; Standard WPA2-Enterprise matches AES-CCMP-128 encryption paired with 802.1X/EAP authentication; WPA3-Enterprise 192-bit Mode matches 256-bit AES-GCMP encryption with HMAC-SHA384 key derivation; Enhanced Open (OWE) matches Unauthenticated Diffie-Hellman key exchange providing opportunistic encryption.
Each wireless protocol suite uses distinct cryptographic mechanisms: WPA3-Personal relies on SAE (Dragonfly key exchange) to prevent offline brute-force attacks; standard WPA2-Enterprise uses 802.1X/EAP with AES-CCMP-128 encryption; WPA3-Enterprise 192-bit mode upgrades encryption to 256-bit AES-GCMP and HMAC-SHA384; and Enhanced Open employs OWE with unauthenticated Diffie-Hellman key exchange for open Wi-Fi protection.

Adım Adım Çözüm

1
Analyze WPA3-Personal key management requirements
Identify that WPA3-Personal mandates SAE (Simultaneous Authentication of Equals), replacing static PSK to protect against offline passphrase cracking.
SAE performs a forward-secret Dragonfly handshake during initial association.
2
Analyze standard WPA2-Enterprise default specifications
Identify that WPA2-Enterprise standard deployments use 802.1X with EAP methods for identity verification combined with AES-CCMP-128 for symmetric payload encryption.
AES-CCMP-128 is the default mandatory cipher suite defined in the IEEE 802.11i standard for WPA2.
3
Evaluate high-security WPA3 Enterprise requirements
Identify that WPA3-Enterprise 192-bit security mode specifies 256-bit AES Galois/Counter Mode (GCMP-256) and HMAC-SHA384 key derivation.
The 192-bit security profile aligns with Commercial National Security Algorithm (CNSA) suite standards.
4
Examine open wireless network encryption standards
Identify that Enhanced Open utilizes RFC 8110 Opportunistic Wireless Encryption (OWE) via an unauthenticated Diffie-Hellman key exchange.
OWE delivers pairwise encryption on guest or open SSIDs without requiring password authentication.

Anahtar Kavram

Wireless security standards (WPA2, WPA3, OWE) and their respective authentication, key exchange, and cipher mechanisms.
Soru 134Soru

A network engineer applies the following extended IPv4 access control list inbound on router interface GigabitEthernet0/0/0 to allow web administration access from an operations subnet (172.16.50.0/24172.16.50.0/24) to a database server (10.0.1.50/3210.0.1.50/32):

text
ip access-list extended ADMIN_TO_DB
permit tcp 172.16.50.0 0.0.0.255 host 10.0.1.50 eq 443

Immediately after applying the ACL, administrators report that HTTPS connections to 10.0.1.5010.0.1.50 work as expected, but SSH connections and ICMP echo requests (ping) from the operations subnet to 10.0.1.5010.0.1.50 fail. What is the root cause of this behavior?

Cevabı ve açıklamayı göster

Cevap: The implicit deny statement at the end of the ACL drops all IPv4 traffic that does not match an explicit permit entry.

Cevap

The implicit deny statement at the end of the access control list automatically drops all unlisted IPv4 traffic, including SSH and ICMP.
Every Cisco IOS IPv4 Access Control List ends with an unwritten, invisible entry commonly referred to as the implicit deny clause ('deny ip any any'). Because the ACL contains only a single permit entry for TCP port 443, any non-matching packets—such as SSH (TCP port 22) or ICMP—are caught by this final implicit deny rule and dropped.

Adım Adım Çözüm

1
Analyze the configured ACL statement.
The statement 'permit tcp 172.16.50.0 0.0.0.255 host 10.0.1.50 eq 443' explicitly permits only TCP traffic sourced from 172.16.50.0/24 destined to 10.0.1.50 on destination port 443 (HTTPS).
Extended ACLs check source IP, destination IP, protocol, and port numbers.
2
Evaluate how unlisted traffic (SSH on port 22 and ICMP) is processed.
SSH and ICMP packets do not match the single permit rule configured in the list.
ACL entries are processed sequentially from top to bottom.
3
Apply default Cisco IOS ACL termination logic.
Traffic that fails to match any explicit ACE reaches the end of the ACL and hits the implicit 'deny ip any any' rule, resulting in packet drops.
All Cisco IPv4 ACLs append an invisible deny-all statement at the bottom of the access list.

Anahtar Kavram

ACL Sequential Processing and Implicit Deny Behavior
Tahmini Süre:1m 15s
Soru 135Soru

An administrator configures the following IPv4 extended named access control list on a Cisco IOS router and applies it inbound on interface GigabitEthernet0/0/1:

text
ip access-list extended CORP_SEC
permit tcp 10.1.10.0 0.0.0.255 host 192.168.1.50 eq 22
permit tcp 10.1.10.0 0.0.0.255 192.168.2.0 0.0.0.255 eq 80
permit tcp 10.1.10.0 0.0.0.255 192.168.2.0 0.0.0.255 eq 443

Which two statements accurately describe how network traffic arriving on GigabitEthernet0/0/1 will be filtered by this access control list? (Select two options.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: ICMP echo requests from host 10.1.10.5 to host 192.168.1.50 are dropped due to the implicit deny at the end of the access list.; TCP traffic originating from host 10.1.10.20 destined to host 192.168.2.100 on port 443 is permitted through the interface.

Cevap

ICMP echo requests from host 10.1.10.5 to host 192.168.1.50 are dropped due to the implicit deny at the end of the access list, and TCP traffic originating from host 10.1.10.20 destined to host 192.168.2.100 on port 443 is permitted through the interface.
The correct statements recognize both explicit matching criteria and the role of the implicit deny clause. First, ICMP packets from host 10.1.10.5 to host 192.168.1.50 are dropped because the ACL only permits TCP port 22 to that destination; unmatched ICMP packets trigger the invisible implicit deny at the end of the list. Second, TCP traffic from host 10.1.10.20 to host 192.168.2.100 on port 443 explicitly matches the third entry permitting 10.1.10.0/24 to 192.168.2.0/24 eq 443.

Adım Adım Çözüm

1
Analyze line 1 of the ACL for SSH traffic to host 192.168.1.50
Line 1 permits TCP traffic from 10.1.10.0/24 to host 192.168.1.50 on port 22 (SSH). It does not permit ICMP traffic or SSH traffic to other subnets.
Extended ACL match criteria examine protocol type (TCP), source network (10.1.10.0/24), destination address (host 192.168.1.50), and destination port (22).
2
Analyze lines 2 and 3 of the ACL for HTTP/HTTPS traffic to subnet 192.168.2.0/24
Lines 2 and 3 permit TCP traffic from 10.1.10.0/24 to any host in 192.168.2.0/24 on ports 80 (HTTP) and 443 (HTTPS). Host 192.168.2.100 falls into 192.168.2.0/24, so HTTPS traffic to this host matches line 3 and is permitted.
The wildcard mask 0.0.0.255 on destination 192.168.2.0 specifies the entire /24 network range.
3
Evaluate unlisted traffic types against the end of the ACL
ICMP echo requests from 10.1.10.5 to 192.168.1.50 do not match TCP port 22, 80, or 443 rules. Unmatched traffic hits the unwritten 'deny ip any any' at the end of the ACL and is dropped.
Cisco IOS automatically appends an invisible implicit deny statement at the end of every access control list.

Anahtar Kavram

Extended IPv4 ACL sequential matching and implicit deny processing
Tahmini Süre:1m 30s
Soru 136Soru

A system administrator is configuring an authentication server to support 802.1X wireless client access across campus switch stacks. Which operational characteristic of RADIUS makes it the primary protocol choice for this network access scenario compared to TACACS+?

Cevabı ve açıklamayı göster

Cevap: It combines authentication and authorization into a single protocol process while encrypting only the user password.

Cevap

RADIUS combines authentication and authorization into a single protocol exchange and encrypts only the password field, making it the industry standard for 802.1X network access control.
The correct answer accurately identifies key attributes of RADIUS: it combines authentication and authorization into a unified exchange and encrypts only the password attribute in the request body. This combined model is optimized for network access control applications like 802.1X.

Adım Adım Çözüm

1
Analyze the scenario requirement
The requirement focuses on 802.1X network access control for wireless clients and switch ports.
802.1X architectures rely heavily on RADIUS because network access decisions (Authentication and Authorization) occur simultaneously upon connection.
2
Compare RADIUS functional mechanics with TACACS+
RADIUS operates via UDP (ports 1812/1813), combines authentication and authorization into single transactions, and encrypts only the password attribute.
TACACS+ uses TCP port 49, separates AAA processes independently (allowing per-command authorization for administrator CLI access), and encrypts the entire packet body.
3
Identify the correct option describing RADIUS behavior
Combining authentication and authorization while encrypting only the password is the defining operational behavior of RADIUS.
This functional pairing aligns directly with network access control standards like 802.1X.

Anahtar Kavram

RADIUS vs TACACS+ Protocol Architectural Differences
Soru 137Soru

A network administrator installs a new identity certificate on a Cisco IOS router to secure HTTPS management access. However, when administrative workstations attempt to connect to the router via HTTPS, their web browsers display a security warning stating that the certificate issuer is untrusted. The router's system clock is synchronized via NTP, and the certificate is within its valid date range. What is the root cause of this trust failure?

Cevabı ve açıklamayı göster

Cevap: The client workstations lack the root certificate of the issuing Certificate Authority in their trusted certificate store to validate the chain of trust.

Cevap

The client workstations lack the root certificate of the issuing Certificate Authority in their trusted certificate store to validate the chain of trust.
For a client browser to trust a server's identity certificate, it must validate the certificate signature using the public key of the issuing Certificate Authority (CA). If the CA root certificate (or intermediate CA certificate) is missing from the client's trusted root certificate store, the browser cannot build a valid chain of trust and will display an untrusted certificate warning.

Adım Adım Çözüm

1
Analyze the certificate validation failure symptom
Client browsers reject the router's identity certificate due to an untrusted issuer.
During a TLS handshake, the client verifies the digital signature on the server's certificate against known, trusted Certificate Authorities.
2
Evaluate PKI trust requirements
The client must possess the public key (root certificate) of the CA that signed the identity certificate.
Without the root CA certificate installed in the client's local trusted root store, the browser cannot build a valid chain of trust back to a trusted anchor.

Anahtar Kavram

Public Key Infrastructure Chain of Trust and Root CA Certificate Validation
Soru 138Soru

A network infrastructure team is selecting a centralized AAA protocol to secure administrative CLI access to enterprise switches. The security policy dictates that all communication between the network devices and the AAA server must have its entire packet payload encrypted, and the solution must support granular authorization for individual CLI commands. Which protocol satisfies these security requirements?

Cevabı ve açıklamayı göster

Cevap: TACACS+

Cevap

TACACS+ meets both requirements by encrypting the full packet body and separating authorization from authentication to permit command-level control.
TACACS+ is a AAA protocol operating over TCP port 49. It encrypts the entire body of the packet (all payload data beyond the TACACS+ header) and separates AAA functions, making it ideal for network device administration where granular per-command authorization is required.

Adım Adım Çözüm

1
Analyze the payload encryption requirement.
Full-packet payload encryption is required. TACACS+ encrypts the entire body of the packet, whereas RADIUS only encrypts the password attribute.
Security policy specifies full-packet encryption rather than selective field encryption.
2
Analyze the command authorization requirement.
Granular command-level authorization is required. TACACS+ separates authentication, authorization, and accounting, allowing individual command checks. RADIUS combines authentication and authorization into single attribute-value pairs.
Separation of AAA functions is necessary for per-command authorization.

Anahtar Kavram

TACACS+ vs RADIUS AAA protocol features and encryption mechanisms
Soru 139Soru

An administrator needs to restrict access on a Cisco IOS router so that only traffic from host 192.168.10.15192.168.10.15 can reach the internal web server at 10.1.1.5010.1.1.50 via HTTPS (TCP port 443443). All other traffic originating from the 192.168.10.0/24192.168.10.0/24 network destined to any location must be allowed. Which set of IPv4 access control list statements correctly satisfies these requirements?

Cevabı ve açıklamayı göster

Cevap: ip access-list extended SECURE_ACCESS
permit tcp host 192.168.10.15 host 10.1.1.50 eq 443
deny tcp 192.168.10.0 0.0.0.255 host 10.1.1.50 eq 443
permit ip 192.168.10.0 0.0.0.255 any

Cevap

The extended IPv4 ACL configuration that permits HTTPS traffic from host 192.168.10.15, denies HTTPS traffic from the rest of the 192.168.10.0/24 subnet to host 10.1.1.50, and permits all remaining IPv4 traffic from 192.168.10.0/24.
The correct configuration uses an extended named ACL to specify protocol (TCP) and port numbers (443). By placing the specific host permit line before the broader subnet deny line, the router allows host 192.168.10.15 to connect via HTTPS while blocking other hosts in 192.168.10.0/24 from reaching the web server on port 443. Finally, the trailing permit entry ensures other general IP traffic from the subnet is not dropped by the implicit deny rule.

Adım Adım Çözüm

1
Determine the ACL type required
Extended ACL is required because filtering is based on source address, destination address, and protocol/port (TCP 443).
Standard ACLs can only filter based on source IP address.
2
Order the ACL permit and deny rules from most specific to least specific
First permit host 192.168.10.15 to reach host 10.1.1.50 eq 443, then deny the subnet 192.168.10.0 0.0.0.255 to host 10.1.1.50 eq 443.
Cisco IOS processes ACL entries top-down; matching stops at the first matching entry.
3
Account for the implicit deny clause at the end of the ACL
Add an explicit permit rule 'permit ip 192.168.10.0 0.0.0.255 any'.
Without an explicit permit statement at the end, all other IP traffic from the subnet would be blocked by the invisible implicit deny entry.

Anahtar Kavram

Extended IPv4 Access Control Lists top-down processing and implicit deny behavior
Tahmini Süre:1m 30s
Soru 140Soru

An enterprise network policy mandates Multi-Factor Authentication (MFA) for network administrators establishing SSH sessions to core infrastructure devices. The policy specifically requires combining a 'something you know' factor with a 'something you have' factor. Which authentication combination satisfies this policy requirement?

Cevabı ve açıklamayı göster

Cevap: A static passphrase and a one-time password (OTP) generated by a mobile authenticator app

Cevap

Combining a static passphrase with an OTP generated by a mobile authenticator app satisfies the requirement because it pair a knowledge factor ('something you know') with a possession factor ('something you have').
Multi-Factor Authentication requires using authentication mechanisms from at least two distinct categories: Knowledge (something you know), Possession (something you have), or Inherence (something you are). A static passphrase is a knowledge factor because it relies on memorized secret data, while a mobile authenticator app OTP represents a possession factor because it relies on control of a specific registered physical device.

Adım Adım Çözüm

1
Identify the MFA factor categories required by the security policy
The policy requires one knowledge factor ('something you know') and one possession factor ('something you have').
True MFA requires distinct factor categories to ensure that compromising one mechanism does not compromise the entire authentication process.
2
Categorize the candidate authentication methods presented in each option
A passphrase is knowledge; a mobile authenticator app tied to a physical device is possession. Passwords/PINs are dual knowledge. Hardware keys/smartcards are dual possession. Biometrics are dual inherence.
Classifying each mechanism into its respective MFA category reveals which pair spans two distinct requested categories.
3
Select the pair that combines a knowledge factor and a possession factor
The option combining a static passphrase with a mobile authenticator app OTP is correct.
It fulfills both required factor types.

Anahtar Kavram

Multi-Factor Authentication (MFA) Categorization (Knowledge, Possession, Inherence)
ÖncekiSayfa 7 / 15Sonraki
Security Fundamentals Alıştırma Soruları — Cisco CCNA — Sayfa 7 | Examkin