The correct answer is missing the outside interface (for example g0/0) in the overload statement.

The "correct" answer is missing "lldp run" which is done globally. Without this command lldp will not run.

Please review the answer and correct accordingly.

Thanks!
James

"What is used to identify spurious DHCP servers?"

Answser should be DHCPOFFER

Not DHCPDISCOVER.

Please verify and correct accordingly.

Thanks,
James

Please review this question.

The answer I believe should be:

✔ Correct choice:
Responds to a request for IP address to domain name resolution to the DNS server.

Why the other options are incorrect

• “Serves requests over destination port 53.”
  ? This describes a technical detail of DNS transport (DNS typically uses port 53), not the lookup operation itself.
  
• “DNS server pings the destination to verify that it is available.”
  ❌ DNS does not ping hosts or check availability.
  
• “DNS server forwards the client to an alternate IP address when the primary IP is down.”
  ❌ This describes load balancing or failover behavior, not the fundamental DNS lookup process.
  Thanks,JJ

Just wanted to get on here and say I passed   If you have any doubts, don't. Howtopass will definitely help. I used Jeremy's IT Lab, his exams, and Boson exsim as well before this site. Failed the first time. Scores weren't terrible but a lot of questions for a first time taker was confusing af. Just make sure to read through the explanations, and use google or chatgpt if you need further clarification.

Also, for first time takers: I got 4 labs and 64 questions for both exams.

For the EIGRP neighborship issues, 

It is mainly due to Default class dropping all the remaining matched traffic (like ARP)

Existing Config for Class-default :

class class-default
  police 8000 1500 1500 conform-action drop exceed-action drop


Updated Config :
class class-default
  police 8000 1500 1500 conform-action transmit exceed-action drop

I think this approach might be better than allowing "arp traffic" on CoPP-Critical Class Map

Hello, When I loaded this lab in packet tracer and followed all the instructions/commands exactly, packet tracer still says configuration is incomplete when doing "check results".

Can you please check, shouldn't the answer be "Check and resolve reachability between WLC and NTP server"

The alert mentions about lag between DNA Center & WLC, 

if there was an issue between NTP Server & DNA Center, then there would have been multiple alerts from all other devices too regarding the time lag, but the exhibit only shows WLC issue.

Also, assuming from the exhibit, if you look at bottom left, the Top 10 issues is selected and alert is P2, So it's probably a device(WLC) issue.

The DNA & NTP reachability would cause P1

Please review, I think the correct answer should be 

Define a delay timer under track 1

For example :
track 1 ip sla 1 reachability
delay down 10 up 10



Changing the threshold(RTT) to 1500 ms won't solve the issue

Please review, the correct option should be 

"Police the pir for BGP, conform-action transmit, and exceed action transmit"

to avoid dropping the BGP packets, which is causing the BGP flapping/re-calculations