static routing question

[KW117]

Can you please tell me if i have answered this question correctly?

[TotallyTodd]

Hi, so you totally need to add a zero to the destination network address such as 172.16.10.0 and also it is saying to use the 192.168.3.0 network as the backup network totally, the correct configuration would totally use the next hop.. so from R1 you will totally put the destination as the 172.16.20.0 255.255.255.0 and the next hop with is the connected interface of the connected Router 3 interface.  [ destination network | subnet-mask | next-hop | using the interfaces within the 192.168.3.0 network totally. 

[STYVES]

Hi, the scenario states that the organization is using RIP to exchange routes. Cisco routers assign the admin distance of 120 to routes learned via RIP. R1 and R3 will prefer the static routes and will start to route the traffic via the directly connected link (192.168.3.0/24). If you intend to keep R2 as the transit between R1 and R3, you will have to assign a higher admin distance to the static routes you are adding. Using the admin distance of 125 ( or any number between 121 and 254) will accomplish the task.
R1 - ip route 172.16.20.0 255.255.255.0 192.168.3.2 125
R3 - ip route 172.16.10.0 255.255.255.0 192.168.3.1 125

[MHM Cisco World]

Correct 

[paul driver]

Hello
The static routes you show, indicate an incorrect next-hop address, They presently pointing towards a subnet address and not a specific host ip address of the directly connect interface between R1-R3 also they lack an administrative distance ( which need to be higher value of  RIPs seed metric  = 120)

it should read:

rtr1
ip route 172.16.20.0 255.255.255.0 172.16.3.2  254

rtr3
ip route 172.16.10.0 255.255.255.0 172.16.3.1  254

Obviously it doesn’t state this but, it would be more applicable to utilize an Offset list to provide a more dynamic failover instead of static routes but I assume that will be for another question

[Joseph W. Doherty]

"Can you please tell me if i have answered this question correctly?"

No.

Both @TotallyTodd and @STYVES show your remote network prefix missing it's last octet and next hop IP.  @STYVES also notes you need to adjust static routed statements higher than RIP's AD.

Interestingly, RIP, I believe, would not work correctly in the shown network because RIP is classful and both edge networks would be considered the same Class B network.

[edit - addendum]

Noticed @paul driver posting after posting mine.  He suggests using a static AD of 254 which cannot be less than any other (non-null) AD, but is not guaranteed to be higher.  He also mentions possibly having the backup as another RIP, which I too had thought to mention, but thinking about RIP is what also led me to the edge network issue (above), which, BTW, shouldn't be a problem for RIP v2.