Refer to the exhibit. A prefix list is created to filter routes inbound to an EIGRP process except for network 10 prefixes. After the prefix list is applied, no network 10 prefixes are visible in the routing table from EIGRP. Which configuration resolves the issue?
The prefix list configuration is an ordered list, and the sequence of entries is important. In the original configuration, all routes are denied before the permit rule for the 10.0.0.0/8 network is reached. By adding the statement 'ip prefix-list EIGRP seq 5 permit 10.0.0.0/8 ge 9' before the deny statement, network 10 prefixes are explicitly allowed before any other routes are denied. This ensures that network 10 prefixes can be seen in the EIGRP routes. Additionally, allowing prefix lengths greater than /8 ('ge 9') ensures that all subnets of the 10.0.0.0/8 network are permitted.
"ip prefix-list EIGRP seq 5 permit 10.0.0.0/8" is correct. A prefix-list is an ordered list. "permit 10.0.0.0/8" needs to come before "deny 0.0.0.0/0 le 32" (deny everything), otherwise the "10" network is matched by the deny statement and thus, it gets to be filtered. "sequence 5" places the "permit 10.0.0.0/8" before "deny 0.0.0.0/0 le 32".
https://networklessons.com/eigrp/how-to-configure-prefix-list-on-cisco-router
To add to this answer, the second problem resolved in answer D is the acceptance of prefix lengths greater than /8. As it stood, sequence 20 was only accepting the prefix "10.0.0.0/8" and nothing else. The keyword "ge 9" allows the prefix statement to accept prefix lengths between /8 and /32. Alternatively it could have been "le 32"
D is corerct