In an OSPF hubandspoke topology, what needs to be done to ensure that the spoke routers would never be selected as DR and BDR? All spoke routers need to be configured with an OSPF interface priority of 0 (ip ospf priority) so that they will not become the DR/BDR.* All routers must be configured with an OSPF interface priority of 0 (ip ospf priority) to disable the DR/BDR election process. Because nonbroadcast networks do not elect a DR/BDR, nothing needs to be done. One of the spoke routers will need to be configured as the DR by setting the OSPF interface priority higher than 1 (ip ospf priority).

IT Questions BankCategory: CCNP ROUTEIn an OSPF hubandspoke topology, what needs to be done to ensure that the spoke routers would never be selected as DR and BDR? All spoke routers need to be configured with an OSPF interface priority of 0 (ip ospf priority) so that they will not become the DR/BDR.* All routers must be configured with an OSPF interface priority of 0 (ip ospf priority) to disable the DR/BDR election process. Because nonbroadcast networks do not elect a DR/BDR, nothing needs to be done. One of the spoke routers will need to be configured as the DR by setting the OSPF interface priority higher than 1 (ip ospf priority).

Which two statements are correct about OSPF route summarization? (Choose two.)

  • OSPF can perform automatic summarization on major classful network boundaries even if no summarization commands are entered from the CLI.
  • Once OSPF route summarization is configured, the summary route will be advertised even if none of the networks in the address range are in the routing table.
  • Automatic OSPF route summarization is performed by the ABR.
  • The metric of the summary route is equal to the lowest cost network within the summary Correct! address range.
  • The area 51 range 172.0.0.0 255.0.0.0 command identifies area 51 as the area that contains the range of networks to be summarized.

Exam with this question: CCNP ROUTE Chapter 3 Exam Answers (Version 7)

Subscribe
Notify of
guest

0 Comments
Inline Feedbacks
View all comments