How many routes received from the BGP peer at 192.168.1.2 are active for this router?

Refer to the Exhibit.

Refer to the command-line output shown in the exhibit. How many routes received from the BGP peer at 192.168.1.2 are active for this router?

A.
3 routes

B.
4 routes

C.
46 routes

D.
53 routes

Explanation:
Looking at the print out, match up the numbers shown with the Peer description

Peer AS InPkt OutPkt OutQ Flags Last Up/Down State | # Active / Received / Accepted / Damped
192.168.1.2 222 26 30 0 2 10.44 46 53 53 4

show bgp summary Output Fields
Field Name
Field Description
Groups
Number of BGP groups.
Peers
Number of BGP peers.
Down peers
Number of down BGP peers.
Table
Name of routing table.
Tot Paths
Total number of paths.
Act Paths
Number of active routes.
Suppressed
Number of routes currently inactive because of damping or other reasons. These routes do not appear in the forwarding table and are not exported by routing protocols.
History
Number of withdrawn routes stored locally to keep track of damping history.
Damp State
Number of routes with a figure of merit greater than zero, but still active because the value has not reached the threshold at which suppression occurs.
Pending
Routes in process by BGP import policy.
Peer
Address of each BGP peer. Each peer has one line of output.
AS
Peer’s AS number.
InPkt
Number of packets received from the peer.
OutPkt
Number of packets sent to the peer.
OutQ
Number of BGP packets that are queued to be transmitted to a particular neighbor. It normally is 0 because the queue usually is emptied quickly.
Flaps
Number of times the BGP session has gone down and then come back up.
Last Up/Down
Last time since the neighbor transitioned to or from the established state.
State|#Active
/Received/Accepted
/Damped
Multipurpose field that displays information about BGP peer sessions. The fields contents depend upon whether a session is established and whether it was established on the main routing device or in a routing instance.
If a peer is not established, the field shows the state of the peer session: Active, Connect, or Idle.
If a BGP session is established on the main routing device, the field shows the number of active, received, accepted, and damped routes that are received from a neighbor and appear in the inet.0 (main) and inet.2 (multicast) routing tables. For example, 8/10/10/2 and 2/4/4/0 indicate the following:
8 active routes, 10 received routes, 10 accepted routes, and 2 damped routes from a BGP peer appear in the inet.0 routing table.
2 active routes, 4 received routes, 4 accepted routes, and no damped routes from a BGP peer appear in the inet.2 routing table.
If a BGP session is established in a routing instance, the field indicates the established (Establ) state, identifies the specific routing table that receives BGP updates, and shows the number of active, received, and damped routes that are received from a neighbor. For example, Establ VPN-AB.inet.0: 2/4/0 indicates the following:
The BGP session is established.
Routes are received in the VPN-AB.inet.0 routing table.
The local routing device has two active routes, four received routes, and no damped routes from a BGP peer.
When a BGP session is established, the peers are exchanging update messages.