Fortinet Exam NSE7_EFW-7.2 Topic 4 Question 8 Discussion

Actual exam question for Fortinet's NSE7_EFW-7.2 exam

Question #: 8
Topic #: 4

Exhibit.

Refer to the exhibit, which contains a CLI script configuration on fortiManager. An administrator configured the CLI script on FortiManager rut the script tailed to apply any changes to the managed

device after being executed.

What are two reasons why the script did not make any changes to the managed device? (Choose two)

AThe commands that start with the # sign did not run.

BIncomplete commands can cause CLI scripts to fail.

CStatic routes can be added using only TCI scripts.

DCLI scripts must start with #!.

Show Suggested Answer

Suggested Answer: A, B

The commands that start with the # sign did not run because they are treated as comments in the CLI script. Incomplete commands can cause CLI scripts to fail because they are not recognized by the FortiGate device. The other options are incorrect because static routes can be added using CLI or GUI, and CLI scripts do not need to start with #!.Reference:=Configuring custom scripts | FortiManager 7.2.0 - Fortinet Documentation, section ''CLI script syntax''.

by Cristal at Mar 05, 2024, 10:37 PM

Limited Time Offer

25%

Off

Get Premium NSE7_EFW-7.2 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Sue

2 days ago

I think the reason could be because the commands that start with the # sign did not run.

upvoted 0 times

...

Ha, reminds me of the time I accidentally ran a script that deleted the entire config on a device. Talk about a bad day at the office! But yeah, incomplete commands are the enemy when it comes to CLI scripts.

upvoted 0 times

...

Francene

25 days ago

You know, I've seen this happen before when the script wasn't properly tested. We really need to make sure our CLI scripts are airtight before running them on production devices. Otherwise, we end up with situations like this.

upvoted 0 times

Royal

6 days ago

D) Absolutely, ensuring the script starts with #! is a basic but essential step.

upvoted 0 times

...

Barabara

7 days ago

A) I agree, it's important to double-check everything to avoid situations like this.

upvoted 0 times

...

Howard

8 days ago

B) Yes, incomplete commands can definitely cause issues when running CLI scripts.

upvoted 0 times

...

Kenneth

9 days ago

D) CLI scripts must start with #!.

upvoted 0 times

...

Ivory

10 days ago

A) That's a good point. Testing scripts thoroughly is crucial before running them on production devices.

upvoted 0 times

...

Casie

11 days ago

B) Incomplete commands can cause CLI scripts to fail.

upvoted 0 times

...

Melissa

12 days ago

A) The commands that start with the # sign did not run.

upvoted 0 times

...

Daniel

26 days ago

Yeah, I agree that incomplete commands are likely the culprit here. The script looks like it's missing some key information. And the # comments probably didn't help either.

upvoted 0 times

...

Lorean

27 days ago

Hmm, this is an interesting question. I'm a bit unsure about the #! requirement for CLI scripts, but I'm pretty sure incomplete commands can cause issues. What do you all think?

upvoted 0 times

...

Fortinet Exam NSE7_EFW-7.2 Topic 4 Question 8 Discussion

Contribute your Thoughts:

Sue

Hobert

Francene

Royal

Barabara

Howard

Kenneth

Ivory

Casie

Melissa

Daniel

Lorean