Redistribution of static routes to EIGRP

I have learnt an interesting fact about redistribution into EIGRP process. If you want to redistribute static route as INTERNAL to EIGRP, you should use simple network x.x.x.x command instead of redistribute static. EIGRP treats static routes to interface as a connected networks, so it works pretty well!

Propagation of default route into EIGRP domain

Two main options exist:
1. Configure static default route and then redistribute it into EIGRP;
2. Configure default-network command that should point toward the network connected to gateway router (for example, it could be it's WAN subnet or just loopback host route). This command could be configured at the Enterprise edge router that have default route or full routing table. All routers in EIGRP domain will mark this newly learnt network as "candidate default". The most easily understandable explanation for me is that we should mark network as default if we know that when packet from anywhere of the inside network reach the router connected to this network it will know how to further forward this packet.

EIGRP Citation

About routers going Active and querying their neighbors.

From the CCNP ROUTE Cert Guide:

If a router receives an EIGRP Query for a prefix/prefix length, does not have an exactly matching (both prefix and prefix length) route, but does have a summary route that includes the prefix/prefix length, that router immediately sends an EIGRP Reply and does not flood the Query to its own neighbors.