| 1: | How does OSPF bind the flooding of topology information? |
| 2: | What is the rule of thumb to consider when designing around summarization of topology information and summarization of reachability information? |
| 3: | What is the general rule of thumb on dealing with complexity in an OSPF network design? |
| 4: | What are some of the advantages of placing the ABRs in a three-layer hierarchy at the edge of the network core? |
| 5: | What are the disadvantages of placing the ABRs in a three-layer hierarchical network design at the edge of the core? |
| 6: | What is the most flexible and generally most successful way to place ABRs in a three-layer hierarchical network? |
| 7: | In general, where is the best place to put ABRs in a two-layer hierarchical network? When should you vary from this rule of thumb? |
| 8: | What are the types of stub areas, and what routing information do they block at the ABR? |
| 9: | When should you use stub areas? |
| 10: | Where can you aggregate (summarize) routing information in an OSPF network? |
| 11: | What types of routes can you filter in an OSPF network? |
| 12: | If two OSPF processes that are running on the same router attempt to inject a route to the same destination into the local routing table, which route is installed? |
| 13: | What mechanism can you use to reduce flooding in a full mesh topology? |
