Fgt is joined in the security fabric

Correct answer is C

I created a firewall object on a root fortigate. Then, on a downstream FG the object appeared, but when I tried to edit it the OK button was missing. Only the return button is present. It doesn't happen like that in Workspace mode. So C is the correct option.

C is Correct B is not correct because "Workspace mode is available only through CLI mode: Pg. 25 in Enterprise_Firewall_7.2_Study_Guide-Online.pdf

When an administrator edits an object in workspace mode, it is locked, preventing other administrators from editing that object. A warning message is shown to let the administrator know that the object is currently being configured in another workspace transaction. Pg. 25 in Enterprise_Firewall_7.2_Study_Guide-Online.pdf

I made a mistake earlier and voted B as that made most sense at the time. After checking in my lab, C is the correct answer. You are indeed presented with only the "return" option on the object on a downstream device when trying to edit a Global fabric object created on the root device.

In workspace mode the "OK" button is present, you get an error message as soon as you click on it. When you create a fabric object on a root device, it will synchronize to the downstream devices (if enable) and you will not be able to modify the object on any downstream devices. The "OK" button will NOT be available on downstream devices.

Page 25 Enabling strict header checking disables all hardware acceleration. This includes NP, SP, and CP processing.

Answer B: Answer: D when check-protocol-header is enabled in strict or loose mode all NPs and CPs are disabled.

tested in lab

A bit tricky from the screenshots, as if B was indeed the correct answer, a warning should be shown that the object is being edited by a different user. A doesn't make much sense, as you wouldn't be able to make changes to either of the objects if you were in read-mode. You can edit and configure downstream Fortigates in a Security Fabric at will. There is nothing in the screenshots signifying that this is a downstream device, or the root device. We you can still configure objects on local devices even if they are managed by FortiManager, and as with question A; if you had logged into a Centrally managed device as read-only, you wouldn't be able to edit any of the objects. I believe the answer is B, as that makes most sense, even though it is difficult to tell from the screenshots themselves.

Answer is C. Tested in Lab

Answer is D, i test in my lab with two user, and you always can modify the address but the other user see the warning

The answer is B page 25

The answer is B