Refer to the Exhibit.

In the exhibit, R5 is exporting the RIP network prefixes into OSPF. You want to limit the number of LSAs sent to Area 2.2.2.2, but you want to ensure that all routers in other areas will have routes to all networks contained in the LSAs sent by the routers in Area 2.2.2.2.
Which configuration change will enable this scenario?

A.
Configure Area 2.2.2.2 as a stub area.

B.
Configure Area 2.2.2.2 as a not-so-stubby area.

C.
Configure an area range on R3.

D.
Configure an export filter for OSPF on R3.

Explanation:
Not-so-stubby area

A not-so-stubby area (NSSA) is a type of stub area that can import autonomous system external routes and send them to other areas, but still cannot receive AS-external routes from other areas. NSSA is an extension of the stub area feature that allows the injection of external routes in a limited fashion into the stub area. A case study simulates an NSSA getting around the Stub Area problem of not being able to import external addresses. It visualizes the following activities: the ASBR imports external addresses with a type 7 LSA, the ABR converts a type 7 LSA to type 5 and floods it to other areas, the ABR acts as an “ASBR” for other areas. The ABR’s do not take type 5 LSA’s and then convert to type 7 LSA’s for the area.