lines 3,6, and 7 are wrong. When deploying FWB on AWS it is recommended to use DHCP. So, you will not assgin ip address and gateway information. The gateway also will be obtained through dhcp.
NSE 6 FWB Guide clearly says (page 74): "If you’re deploying in a cloud, such as Amazon Web Services, use DHCP instead of a static IP address." But the line where IP address is set is not in the list of options.
So if we follow the example in page 73 of the guide, the answer is, as suggested also by dzako: lines 6 and 9.
Has anyone read the question where it indicates that it is a Fweb in AWS. and in AWS Cloud environments it is only Reverse Proxy.
therefore 2 and 3 are incorrect
Answer C:
FWBVM # config system interface
FWBVM (interface) #
edit add/edit a table value
delete delete a table value
purge clear all table value
get get dynamic and system information
show show configuration
end end and save last config
AnswerA:
FWBVM # config system settings
FWBVM (settings) #
set modify value
unset set to default value
get get dynamic and system information
show show configuration
abort end and discard last config
end end and save last config
FWBVM (settings) # set
enable-cache-flush enable/disable system cache flush
enable-debug-log enable/disable system debug log
enable-file-upload enable/disable GUI file upload
enable-machine-learning-debug enable/disable machine learning debug
opmode operation mode
stop-guimonitor enable/disable GUI monitor
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
dzako
Highly Voted 4 years, 8 months agohrolrh
Most Recent 3 years, 3 months agoAbdelilahkammache
3 years, 5 months agoBalkancruiser
3 years, 9 months agorkalvarado
3 years, 12 months agoadminnat
4 years agonibnib
4 years, 1 month agokazmisyed
4 years, 1 month ago