The parts you can't see in the picture will be as follows. peer-as 65514: local-as 65514; neighbor 192.168.0.1;

See what's missing from "java70", B and D are correct. In most cases, the local-address statement is not required for the BGP session to establish correctly, as the router will select the appropriate source IP address based on its routing table and configured interfaces. However, there are some scenarios where specifying a specific local IP address may be necessary, such as when there are multiple interfaces with the same IP address or when using a loopback interface as the source address for BGP sessions. Therefore, while it is not required, configuring the local-address statement can provide additional control over the BGP session's source IP address and may be necessary in some specific scenarios.

A - If there is no type default is external C - if you are using loopback you need to use multi-hop in external BGP

"i.e. because it has "multihop" defined it must be an external bgp and there is other config outside the screenshot that shows a peer-as" Hi Takigama, I see that multihop can be config along with type internal, why you said: "because it has "multihop" defined it must be an external bgp"?

it feels like part of the question is missing... the configuration as it is written wouldnt commit as the DEFAULT is type external, if its type external peer-as must be configured... junos wont let you commit that config unless you either specify a peer as or a type... unless you dont define a neighbor, in which case, this config would commit and achieve nothing.. but without either "type internal" or a "peer as" its almost impossible to answer the question without actual assupmtions.. i.e. because it has "multihop" defined it must be an external bgp and there is other config outside the screenshot that shows a peer-as

The answer would be A & C To commit the config either we need "peer-as" for eBGP session or "type internal" for iBGP session. As none of the config there; I assume it's IBGP session due to multihop command as the local-address is loopback. Question 28 will have some clue.

The type external command is kinda optional , a bgp config can be set without specifing type external , anyway the configuration shown cannot be commited because no peer-as was issued , unless no type internal is shown i can assume that an eBGP session is in place to be build , also the multihop statement is a good indicator

the major difference between the iBGP and eBGP is the AS Number. in iBGP you don't need to add the AS number while in eBGP you must add. so B and D are correct.

- By default the EBGP connection is established between immediately connected devices located in two different ASs because the time-to-live (TTL) value of the EBGP packets is equal to 1. If an EBGP peer is more than one hop away, a multihop BGP session must be established. Correct answers are A & C

I think, B and D are correct because peering IP is loopback_address, which basically used in IBGP, and multihop statement isnot required because underlying IGP will provide reachability between the peering IP.

I belive A & B is correct because of the multihop statement in the configuration And multihop does require local address to be specified

Think question is good one, you need to think a little-bit more.