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 NSE7_PBC-7.2 Topic 3 Question 30 Discussion

Actual exam question for Fortinet's NSE7_PBC-7.2 exam
Question #: 30
Topic #: 3
[All NSE7_PBC-7.2 Questions]

Refer to the exhibit.

You are troubleshooting a FortiGate HA floating IP issue with Microsoft Azure. After the failover, the new primary

device does not have the previous primary device floating IP

address.

Show Suggested Answer Hide Answer
Suggested Answer: D

In this scenario, the issue is caused by the Azure service principle account not having a contributor role. This is required for the FortiGate HA floating IP to work properly. Without this role, the new primary device will not have the previous primary device floating IP address after failover.Reference: Fortinet Public Cloud Security knowledge source documents or study guide.

https://docs.fortinet.com/product/fortigate-public-cloud/7.2


Contribute your Thoughts:

Mona
28 days ago
This is a tricky one. I'm going to go with E. The Azure service principle account needs the right permissions to handle the floating IP.
upvoted 0 times
Kaycee
22 hours ago
Could it also be related to the client secret credential being wrong?
upvoted 0 times
...
Hyman
13 days ago
I agree with you. Without the right permissions, the floating IP won't work properly.
upvoted 0 times
...
Darnell
17 days ago
I think E is the correct option. The Azure service principle account must have a contributor role.
upvoted 0 times
...
Lisandra
21 days ago
I agree, without the right permissions, the floating IP won't function properly.
upvoted 0 times
...
Markus
24 days ago
I think E is the correct answer too. The Azure service principle account needs the contributor role for this to work.
upvoted 0 times
...
...
Zita
1 months ago
D seems like a reasonable option too. The error could be caused by credential time expiration. But I'm leaning towards E as the correct answer.
upvoted 0 times
...
Stephane
1 months ago
Haha, what if the issue is that the IT guy forgot to plug in the ethernet cable? Just kidding, but I'd guess E is the right answer.
upvoted 0 times
Freeman
9 days ago
User 2: I agree, but I think E makes more sense in this scenario.
upvoted 0 times
...
Kristofer
1 months ago
User 1: Haha, that would be a funny mistake!
upvoted 0 times
...
...
Micheline
2 months ago
Hmm, I'm not sure. Could it be B? Maybe the FortiGate port4 doesn't have internet access, preventing the floating IP from being updated.
upvoted 0 times
Tennie
12 days ago
D) The error is caused by credential time expiration.
upvoted 0 times
...
Desmond
15 days ago
C) A wrong client secret credential is used
upvoted 0 times
...
Emmett
23 days ago
Hmm, I'm not sure. Could it be B? Maybe the FortiGate port4 doesn't have internet access, preventing the floating IP from being updated.
upvoted 0 times
...
Lajuana
26 days ago
B) FortiGate port4 does not have internet access.
upvoted 0 times
...
Lorrie
28 days ago
A) What could be the possible issue With this scenario?
upvoted 0 times
...
Abel
29 days ago
B) FortiGate port4 does not have internet access.
upvoted 0 times
...
Johnna
1 months ago
A) What could be the possible issue With this scenario?
upvoted 0 times
...
...
Antonio
2 months ago
I believe the Azure service principle account must have a contributor role for the floating IP to work properly.
upvoted 0 times
...
Rodolfo
2 months ago
I think the correct answer is E. The Azure service principle account must have a contributor role to manage the floating IP address properly.
upvoted 0 times
Alayna
20 days ago
B) FortiGate port4 does not have internet access.
upvoted 0 times
...
Ashlee
24 days ago
C) A wrong client secret credential is used
upvoted 0 times
...
Nina
26 days ago
E) The Azure service principle account must have a contributor role.
upvoted 0 times
...
Roxane
27 days ago
A) What could be the possible issue With this scenario?
upvoted 0 times
...
...
Aaron
2 months ago
I agree with Rozella, using the wrong client secret credential could cause the floating IP issue.
upvoted 0 times
...
Rozella
2 months ago
I think the possible issue could be a wrong client secret credential.
upvoted 0 times
...

Save Cancel