The correct answer is B. Only the database can initiate communication.

From the exhibit:

ip nat inside source static 10.1.2.100 interface GigabitEthernet0/1

Inside local (DB): 10.1.2.100

Inside global (translated IP): 10.50.250.1 (Gi0/1 interface)

NAT type: Static NAT

Static NAT creates a permanent one-to-one mapping between inside local and inside global IP.

It allows bidirectional communication, but only if traffic is properly addressed.

The server initiates the connection

The server expects the DB to appear as 10.50.250.0/24 (translated network)

The server sends traffic to 10.50.250.1 (inside global IP).

The router translates:

Destination → 10.1.2.100 (DB) ✔️

DB receives the request and responds.

Return traffic is translated back to 10.50.250.1 ✔️

However:

The NAT rule only defines source translation for traffic originating from inside (DB).

It does not fully support proper session handling when initiated from outside unless routing/NAT symmetry is correct.

In this topology, the expectation and flow mismatch causes only inside-initiated sessions to work reliably.

The database (inside) can initiate connections outward using NAT ✔️

The server (outside) initiating may fail due to NAT direction and expectation mismatch ❌

A. Only the server can initiate communication Incorrect — NAT favors inside-initiated traffic.

C. No communication possible Incorrect — inside-initiated traffic still works.

D. Both can initiate communication Incorrect — would only be true with correct bidirectional NAT design.

Static NAT = bidirectional mapping, BUT

Always check:

Who initiates traffic

Which side is inside vs outside

Whether NAT rules match expected traffic flow

Exam trick:

If NAT is configured as inside source , it primarily supports inside → outside initiation.