— Exhibit —
policy-options {
policy-statement accept-static {
from protocol static;
then accept;
}
}
— Exhibit —
Refer to the Exhibit.
The policy shown in the exhibit is deployed on a router and used as the only BGP export policy.
The router is sending only one BGP route to its peers. However, when you run the CLI command
test policy accept-static 0.0.0.0/0, the policy matches thousands of routes.
Which statement explains this discrepancy?
A.
All policies have an implicit then accept final term.
B.
The default policy for BGP is to reject all routes.
C.
The default policy for the test policy command is to accept all routes.
D.
The test policy command always shows all routes, regardless of whether they match the policy,
when you use the 0.0.0.0/0 argument.
Explanation:
http://www.juniper.net/documentation/en_US/junos11.4/topics/concept/policy-routing-policies-tests.html
After you have created a routing policy, you can use the test policy command to ensure that the policy produces the results that you expect before applying the policy in a live environment. This command determines whether the routes specified in your routing policy are accepted or rejected. The default action of the test policy command is accept.
Note: The default policy of the test policy command accepts all routes from all protocols. Test output can be misleading when you are evaluating protocol-specific conditions.
For example, if you define a policy for BGP that accepts routes of a specified prefix and apply it to BGP as an export policy, BGP routes that match the prefix are advertised to BGP peers. However, if you test the same policy using the test policy command, the test output might indicate that non-BGP routes have been accepted.