Given the following policy: policy-statementlimit-cust { from { route-filter 10.0.0.0/8 orlonger reject; route-filter 10.0.55.0/24 orlonger; route-filter 10.0.0.0/16 orlonger accept; route-filter 0.0.0.0/0 through 0.0.0.0/32 { metric 5; accept; } } then { metric 10; accept; } } What happens to the route 10.0.56.0/24?

The route 10.0.56.0/24 does not match the first term (10.0.0.0/8). It also does not match the second term (10.0.55.0/24) because 10.0.56 is not 10.0.55. It does match the third term 10.0.0.0/16 orlonger, which has an 'accept' action but no metric modification. Therefore, the route is accepted without the metric 10 from the 'then' clause being applied. The 'then' clause only applies to routes accepted by the fourth term (the default). Option D is incorrect because metric 10 only applies to routes caught by the catch-all filter.