What is the problem?

Refer to the Exhibit.
— Exhibit –user@r2# run show route 100.1.1.0/24 detail
inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
100.1.1.0/24 (1 entry, 1 announced)
*Static PreferencE. 5
Next hop typE. Reject
Address: 0x8f7b5a4
Next-hop reference count: 2
StatE.
Local AS: 65001
AgE. 59
Task: RT
Announcement bits (1): 2-KRT

AS path: 65005 I
user@r2# show protocols bgp
group ibgp {
type external;
export to-bgp;
neighbor 10.1.2.1 {
local-address 10.1.2.2;
family inet {
unicast;
}
family inet6 {
unicast;
}
peer-as 65005;
}
}
user@r2# run show bgp summary
Groups: 1 Peers: 1 Down peers: 0
Table Tot Paths Act Paths Suppressed History Damp State Pending
inet6.0
0 0 0 0 0 0
inet.0
0 0 0 0 0 0
Peer AS InPkt OutPkt OutQ Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped…
10.1.2.1 65005 31 31 0 0 12:08 Establ
inet6.0: 0/0/0/0

inet.0: 0/0/0/
user@r2# show policy-options
policy-statement to-bgp {
from protocol static;
then accept;
}
user@r2# run show route advertising-protocol bgp 10.1.2.1
[edit]
user@r2#
— Exhibit –Referring to the exhibit, router r2 does not advertise the static route to peer 10.1.2.1.
What is the problem?

A.
The export policy is incorrect.

B.
The static route has Next hop typE. Reject.

C.
The export policy should be applied under the [edit protocols bgp group ibgp neighbor 10.1.2.1]
hierarchy.

D.
An AS path loop is detected.

Explanation: