The answer must be C and D.
For A - traffic between interfaces is not allowed by default.
For B - Port1-vlan10 and port-2vlan10 are not in the same broadcast domain since the subnet is different.
fortigate ports are in different broadcast domains. so how port1 and port 2 are in same broadcast domains? ı am not sure abot the answer, but B seems incorrect to me.
broadcast domains are discussed in transparent-mode, no IP is assigned to the interfaces in this mode, much less considering that 10.1.10.1/24 is in the same broadcast domain as 10.0.10.1/24 B is surely incorrect.
A. WRONG Because they are different subnets, this will not work work.
B. WRONG The interfaces can only be a part of the same broadcast domain if the Fortigate is in Transparent mode. If the Fortigate was in transpararent mode, however, the interfaces would not be assigned IP addresses.
C. CORRECT Physical interface is native VLAN.
D. CORRECT In NAT mode, which this obviously is, interfaces can be moved around. And even multi-VDOM VLAN sub-interfaces can belong in different VDOMs.
Fortigate Infrastructure 7.0 Pg 121:
Fortigate Infrastructure 7.0 Pg 134:
Fortigate Infrastructure 7.0 Pg 156
Fortigate Infrastructure 7.0 Pg 160:
A wrong most of all because traffic between interfaces not allowed by default.
And D is correct for the sake of the answer... But in reality, the two vlans couldn't exist on the same vdom unless the subnets matched.
Answer B and C
A and d are wrong:
For A - traffic between interfaces is not allowed by default.
For D - "Each interface (physical or VLAN) can belong to ONLY ONE VDOM." (FortiGate Infrastructure 6.4 page 127
C-D:
B is wrong because a brodcast domain is a datalink layer [Level2], here we are working in NAT mode
A is wrong because traffic between different interface aren't allowed
I agree with aads... "For A - traffic between interfaces is not allowed by default.
For B - Port1-vlan10 and port-2vlan10 are not in the same broadcast domain since the subnet is different."
CD is correct
A is wrong, different interfaces are not allowed by default
B is wrong, because physical interfaces with SAME VLAN do not have to belong to the same broadcast domain. We don't know if they connect to the same switch. Also the IP subnet is different another clue
B & D ----Creating VLAN subinterfaces with the same VLAN ID doesn’t create an internal connection between them. For example,
a VLAN ID of 300 on port1 and VLAN ID of 300 on port2 are allowed, but they aren’t connected. Their relationship is the
same as between any two FortiGate network interfaces.
FortiGate interfaces can’t have overlapping IP addresses, the IP addresses of all interfaces must be on different
subnets. This rule applies to both physical interfaces and to virtual interfaces, such as VLAN subinterfaces.
D: https://kb.fortinet.com/kb/documentLink.do?externalID=FD31639 Example of VLAN setting and VDOM assignment. The same VLANs from another ports at the same VDOM.
Answer B is OK only for transparent mode, not NAT mode (IP addresses = NAT mode for this question). FG Infra 7.0 page 171
A: wrong
B: correct. same vlan ID = same broadcast domain
C: correct: Port1 = Vlan0 = Native Vlan
D: Wrong: cant have 2 vlanID interface in the same VDOM
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.
aads
Highly Voted 4 years agoLionardo
Highly Voted 4 years agomurathtp
4 years agogianmarco
4 years agoNSE421
3 years, 12 months agoMrSaintz
3 years, 4 months agoNicolaeEast
Most Recent 2 years, 8 months agoNicolaeEast
2 years, 8 months agoJuanTrabal
2 years, 9 months agoMetDaci
3 years, 1 month agoSandroAlex
3 years, 1 month agoAJDLM
3 years, 1 month agoAJDLM
2 years, 7 months agoMOSTAFAMETWALLY
3 years, 1 month agomario156090
3 years, 2 months agolrosadini
3 years, 3 months agoRatheeshRavindran
3 years, 3 months agoMrSaintz
3 years, 4 months agoStitch2020
3 years, 3 months agoblahblah1234567890000
3 years, 2 months agoScottXYZ
3 years, 4 months agoAli1982
3 years, 5 months agodamcol
3 years, 5 months agofunirka
3 years, 6 months agoforti_Ctes
3 years, 7 months ago