Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Fortinet Exam NSE6_FML-7.2 Topic 5 Question 38 Discussion

Actual exam question for Fortinet's NSE6_FML-7.2 exam
Question #: 38
Topic #: 5
[All NSE6_FML-7.2 Questions]

Refer to the exhibits, which display a topology diagram (Topology) and two FortiMail device configurations (FML1 Configuration and FML2 Configuration).

What is the expected outcome of SMTP sessions sourced from FML1 and destined for FML2?

Show Suggested Answer Hide Answer
Suggested Answer: B, C

Contribute your Thoughts:

Raylene
2 days ago
I bet the question writer is just trying to confuse us with all these TLS, STARTTLS, and SMTPS acronyms. It's like they're speaking a whole different language! If only email security came with subtitles.
upvoted 0 times
...
Hermila
4 days ago
D is the way to go! I mean, come on, who doesn't love a good ol' SMTPS session? It's like a secret handshake for email nerds.
upvoted 0 times
...
Dorsey
9 days ago
I'm going with C. Even though SMTPS is enabled, the STARTTLS command might be rejected by FML2 since the configurations don't seem to match up perfectly.
upvoted 0 times
...
Vi
13 days ago
Hmm, I'm not sure. The topology diagram shows that the devices are connected through a firewall, which could potentially block the SMTPS traffic. I'm leaning towards B or C.
upvoted 0 times
...
Keneth
15 days ago
Why do you think so?
upvoted 0 times
...
Carri
16 days ago
I think the correct answer is D. The configuration shows that both FML1 and FML2 have SMTPS enabled, so they should be able to establish a secure SMTP session.
upvoted 0 times
...
Tyisha
16 days ago
I disagree, I believe it will be option B.
upvoted 0 times
...
Keneth
18 days ago
I think the expected outcome is option D.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77