Certification795 problems· 7 reviewed

CCNP Enterprise

795 incident response problems that help with CCNP Enterprise prep.

All problems (795)

NETWORK-1369A pfSense HA pair syncs cleanly and one package VPN remains brokenAn HA firewall upgrade looks successful and later one package-managed VPN fails only after failover to the secondary node.NetworkAdvanced14 minPro NETWORK-1359A pfSense HA sync reports success and one package VPN never returns on the...A pfSense HA sync reports success and one package VPN never returns on the... focuses on Identity And Access and asks the reader to isolate the key signal in netgate. HA success on the base firewall does not guarantee package-owned...NetworkAdvanced14 minPro NETWORK-1381A QUIC-enabled edge works for browsers and the enterprise proxy breaks API...A QUIC-enabled edge works for browsers and the enterprise proxy breaks API... focuses on incident-response and asks the reader to isolate the key signal in NGINX. Protocol negotiation bugs can hide in header mutation behavior that differs...NetworkAdvanced14 minPro NETWORK-1427A recovery VLAN works on one MLAG peer and not the otherA recovery VLAN works on one MLAG peer and not the other focuses on l2-switching and asks the reader to isolate the key signal in Arista. Operational recovery workflows can diverge from steady-state configuration symmetry in MLAG...NetworkAdvanced14 minPro NETWORK-1437A recovery VLAN works on one MLAG peer and not the otherA recovery VLAN works on one MLAG peer and not the other focuses on l2-switching and asks the reader to isolate the key signal in Arista. Redundancy bugs can hide in differences between recovery procedures rather than in the steady...NetworkAdvanced14 minPro NETWORK-1447A recovery VLAN works on one MLAG peer and not the otherHosts on orphan ports recover after one failure mode and stay isolated after another.NetworkAdvanced14 minPro NETWORK-1417A recovery VLAN works on one side of an MLAG pair and not the otherA recovery VLAN works on one side of an MLAG pair and not the other focuses on l2-switching and asks the reader to isolate the key signal in Arista. Redundancy bugs can hide in operational boot-path differences even when the running co...NetworkAdvanced14 minPro NETWORK-1385A recursive resolver forwards correctly and DNSSEC validation fails only for...A recursive resolver forwards correctly and DNSSEC validation fails only... focuses on reverse-proxy-security and asks the reader to isolate the key signal in Linux. Suffix exceptions can accidentally route one domain around the trust guaran...NetworkAdvanced14 minPro NETWORK-1407A storage recovery VLAN restores half the serversA storage recovery VLAN restores half the servers focuses on l2-switching and asks the reader to isolate the key signal in Arista. MLAG recovery problems often come from asymmetry between peers, not from the peer-link itself failing.NetworkAdvanced14 minPro NETWORK-1395A validating resolver answers quickly and one internal zone fails DNSSECA validating resolver answers quickly and one internal zone fails DNSSEC focuses on reverse-proxy-security and asks the reader to isolate the key signal in Linux. High-availability DNS exceptions can quietly weaken validati...NetworkAdvanced14 minPro NETWORK-1452An EVPN type-5 route is learned and never installedExternal prefixes never appear in forwarding after adding a second vendor into an EVPN fabric.NetworkAdvanced14 minPro NETWORK-1431An HTTP/3 edge rollout passes smoke tests and breaks origin authAn HTTP/3 edge rollout passes smoke tests and breaks origin auth focuses on edge-routing and asks the reader to isolate the key signal in NGINX. Protocol upgrades can change the signed representation of request metadata even when t...NetworkAdvanced14 minPro NETWORK-1411An HTTP/3 edge rollout passes smoke tests and signed origin requests failAn HTTP/3 edge rollout passes smoke tests and signed origin requests fail focuses on edge-routing and asks the reader to isolate the key signal in NGINX. Protocol upgrades can quietly change the byte representation of values used for o...NetworkAdvanced14 minPro NETWORK-1401An HTTP/3 listener works for browsers and breaks signed backend authAn HTTP/3 listener works for browsers and breaks signed backend auth focuses on edge-routing and asks the reader to isolate the key signal in NGINX. Protocol upgrades can subtly change how edge layers normalize authority information be...NetworkAdvanced14 minPro NETWORK-1421An HTTP/3 rollout succeeds and signed origin requests failAn HTTP/3 rollout succeeds and signed origin requests fail focuses on edge-routing and asks the reader to isolate the key signal in NGINX. Protocol upgrades can change the exact bytes used for origin auth even when the logical host looks identical.NetworkAdvanced14 minPro NETWORK-1365An NGINX reverse proxy fronting OpenSearch serves queries and bulk ingest...An NGINX reverse proxy fronting OpenSearch serves queries and bulk ingest... focuses on protocol-interoperability and asks the reader to isolate the key signal in NGINX. Healthy read traffic does not prove high-volume write routes kept the sam...NetworkAdvanced14 minPro NETWORK-1319A BFD-assisted failover never triggers the backup routeA network adds ACL hardening and later one redundant path stops failing over quickly despite healthy-looking interface counters.NetworkAdvanced15 minPro NETWORK-1432A BGP failback never restores the preferred ISPA BGP failback never restores the preferred ISP focuses on bgp and asks the reader to isolate the key signal in Cisco. BGP failback bugs often come from attribute handling on reflected paths rather than from neighbor health.NetworkAdvanced15 minPro NETWORK-1422A BGP failback never restores the primary ISPA BGP failback never restores the primary ISP focuses on bgp and asks the reader to isolate the key signal in Cisco. BGP preference bugs often come from attribute handling on reflection rather than from neighbor health.NetworkAdvanced15 minPro NETWORK-1412A BGP failover never restores the preferred ISPA BGP failover never restores the preferred ISP focuses on bgp and asks the reader to isolate the key signal in Cisco. BGP recovery bugs often come from attribute loss during reflection rather than from neighbor reachability itself.NetworkAdvanced15 minPro