Fortinet FCP_FMG_AD-7.4 Exam Dumps

Option B: 192.168.1.0/24 is the correct answer. In FortiManager, when a firewall address object is defined and used across multiple policy packages without any Per-Device Mapping, the default value configured in the object definition (192.168.1.0/255.255.255.0) is applied to all devices. The exhibit shows that the address object LOCAL_SUBNET has a default IP/netmask of 192.168.1.0/24. Therefore, FortiManager will use this default value for any FortiGate device that does not have a specific Per-Device Mapping configured.

Explanation of Incorrect Options:

Option A: FortiManager generates an error for each FortiGate without a per-device mapping defined for that object is incorrect because FortiManager does not generate an error when a Per-Device Mapping is not set. Instead, it uses the default value provided in the object definition.

Option C: 192.168.1.0/28 is incorrect because the default value is 192.168.1.0/24, as seen in the exhibit, not /28.

Option D: FortiManager replaces the address object to none is incorrect because FortiManager does not replace address objects to 'none' when a Per-Device Mapping is missing; it uses the default value instead.

FortiManager Reference:

Refer to the FortiManager 7.4 Administration Guide, specifically in sections related to 'Address Object Management' and 'Per-Device Mapping,' which detail the behavior of address objects without specific device mappings.

The configuration shown in the exhibit sets the workspace-mode to normal. The workspace mode in FortiManager defines how configuration changes and administrative tasks are handled, specifically regarding locking and collaboration in ADOMs (Administrative Domains).

Understanding the workspace modes:

Normal Mode: In this mode, only one administrator at a time can lock and edit an ADOM. The changes made by one administrator must be completed and saved before another administrator can make changes. It prevents concurrent read-write access within the same ADOM.

Workflow Mode: This mode allows multiple administrators to work on different tasks within the same ADOM, but changes still need to be approved before being committed.

Explanation of Options:

A . You can validate administrator login attempts through external servers.

This option is unrelated to the workspace mode. External authentication servers can be used for administrator logins, but that is a different configuration setting (not related to workspace-mode).

B . The same administrator can lock more than one ADOM at the same time.

This is true. In Normal mode, an administrator can lock multiple ADOMs, meaning they can work on more than one ADOM simultaneously, but each ADOM can only be accessed by one administrator at a time for read-write purposes.

C . Two or more administrators can make configuration changes at the same time, in the same ADOM.

This is false. In Normal mode, only one administrator can have read-write access to an ADOM at a time. If another administrator attempts to make changes, they must wait until the ADOM is unlocked by the first administrator.

D . Concurrent read-write access to an ADOM is disabled.

This is true. In Normal mode, concurrent read-write access is disabled. This means only one administrator at a time can make changes to an ADOM. Other administrators can view the ADOM in read-only mode but cannot make changes until the ADOM is unlocked.

The statement that is true about the policy lock feature on FortiManager is:

A . Policy locking is available in workspace normal mode.

In FortiManager, when working in 'workspace-mode normal,' policies can be locked by administrators to prevent other administrators from editing them simultaneously. This ensures that only one administrator makes changes at any given time, reducing conflicts or mistakes due to concurrent modifications.

Statements B, C, and D are incorrect because:

B is incorrect since locking a policy does not override a locked ADOM. The ADOM lock takes precedence.

C is incorrect because when a policy is locked, it does not necessarily mean the ADOM is locked.

D is incorrect because administrators in the approval group cannot work concurrently on a locked policy; the policy lock prevents concurrent modifications.

FortiManager Reference:

Refer to FortiManager 7.4 Administrator Guide: Policy and Objects > Policy Locking to understand how the policy lock feature functions in different workspace modes.

When you move a device to a new ADOM, the shared policy packages do not transfer automatically. You would need to manually configure or assign the necessary policy packages in the new ADOM.

Ungraceful closed sessions will keep the ADOM in a locked state until the administrator session times out.

In normal workspace mode, if an administrator closes the session without unlocking the ADOM properly, the ADOM remains locked until the session times out.

The same administrator can lock more than one ADOM at the same time.

In normal workspace mode, an administrator can lock more than one ADOM simultaneously for editing. Each ADOM operates independently in terms of locking and editing.