You just installed a new Web server in the DMZ that must be reachable from the Internet. You
create a manual Static NAT rule as follows:
SourcE. Any || Destination: web_public_IP || ServicE. Any || Translated SourcE. original ||
Translated Destination: web_private_IP || ServicE. Original
“web_public_IP? is the node object that represents the new Web server’s public IP address.
“web_private_IP? is the node object that represents the new Web site’s private IP address. You
enable all settings from Global Properties > NAT.
When you try to browse the Web server from the Internet you see the error “page cannot be
displayed?. Which of the following is NOT a possible reason?
A.
There is no Security Policy defined that allows HTTP traffic to the protected Web server.
B. There is no ARP table entry for the protected Web server’s public IP address.
C.
There is no route defined on the Security Gateway for the public IP address to the Web server’s
private IP address.
D.
There is no NAT rule translating the source IP address of packets coming from the protected
Web server.
D)
0
0
Why Say D)?
0
0
Because question asks which is NOT a possible reason, and static NAT rule has been described in the question. Source IP of web server does not need translation when “you try to browse the Web server from the Internet”, and destination NAT rule is handling the traffic in and out….
0
0
It is A. NAT will not work without policy allowing http to the web server.
0
0
The question is: Which of the following is NOT a possible reason?
A is possible and therefore not the answer.
IMHO D, but not sure.
0
0
Should be C. If all NAT settings are selected, you have enabled “Translate on client side” so you don’t need a route in the gateway for the public address for it to work.
0
0
Rafa is right. C is the answer.
A.B,D could be the possible reasons.
0
0
I enjoy this site – its so usefull and helpfull.|
csgo skins canada http://artistfactorynetwork.com/classifieds/10478/152/nba-2k16-mt-sport-vs-the-golden
0
0
C is the answer, once you select translation on client side in global properties, there is no need to have a static route for the packets reaching the natted IP to reach the private address.
All other options are possible reasons for why the access didn’t work.
0
0
D) got this answer in tests now
0
0
C is the answer
A) a rule is necessary
B) arp entry is necessary for manual nat
D) bidirectional nat is not activated in manual nat. When the server reply to the request, the reply need to have its source IP address translated to go to the internet.
0
0
Humm… thinking better, D is the correct answer.
0
0