View Full Fortinet FCP_FMG_AD-7.6 Exam Dumps and Practice Test Dumps.

 

Question 361

What does the Global Database ADOM provide in FortiManager?

1. A dedicated firmware repository
2. A centralized location for shared policies and objects
3. A replacement for all device databases
4. A separate FortiGuard license server

Correct Answer: 2

Explanation

The Global Database ADOM provides a centralized area where administrators can define shared policies and objects for use across supported ADOMs. This can reduce duplication when the same configuration elements are required in multiple management domains. Global policies and objects should be designed carefully because changes can affect multiple environments. Administrators should understand how global policy packages are assigned and how shared configuration interacts with individual ADOM policies before making production changes.

Question 362

What is a major benefit of using global objects in FortiManager?

1. They can provide shared configuration elements across supported ADOMs
2. They automatically upgrade every FortiGate
3. They eliminate all policy packages
4. They disable local device configuration

Correct Answer: 1

Explanation

Global objects allow supported configuration elements to be shared across multiple ADOMs. This is useful when organizations need common addresses, services, or other objects in several administrative environments. Centralizing common objects can reduce duplication and improve consistency. However, administrators should verify compatibility and dependencies before changing a global object because a modification can affect multiple ADOMs. Global configuration should therefore be managed with the same care as other centrally deployed settings.

Question 363

Which type of policy can be used to apply common rules across multiple ADOM environments through the Global Database?

1. Local device policy
2. Global policy
3. Temporary script
4. Firmware policy

Correct Answer: 2

Explanation

Global policies are designed to provide shared policy configuration across supported ADOM environments through the Global Database. They can be useful for common security requirements that need to be maintained consistently across multiple managed environments. Administrators should understand how global policies are assigned and how they interact with local policy packages before deployment. Careful planning is important because a change to a shared global policy can affect multiple target environments.

Question 364

How can a global policy package become available to an ADOM?

1. By assigning the global policy package to the required ADOM
2. By restarting every FortiGate
3. By deleting the local policy package
4. By disabling the Global Database

Correct Answer: 1

Explanation

A global policy package must be assigned to the appropriate ADOMs before its shared policies can be used in those environments. This assignment establishes which ADOMs consume the global policy configuration. Administrators should verify the assignment carefully because adding or removing an ADOM from a global policy package changes where the shared policy is applicable. After assignment, the resulting configuration should be reviewed before any installation is performed on production devices.

Question 365

What does Fabric View help administrators visualize in a FortiManager environment?

1. Security Fabric topology and related devices
2. Administrator password history
3. Firmware download speeds only
4. Browser connection settings

Correct Answer: 1

Explanation

Fabric View provides a visual representation of supported Security Fabric topology and related managed devices. It can help administrators understand how devices are connected within the Security Fabric and identify the relationships between components. This view can be useful when reviewing network architecture and troubleshooting connectivity or topology-related issues. The displayed information depends on the devices, configuration, and supported Fortinet features available in the environment.

Question 366

What is the purpose of the Security Fabric rating in FortiManager?

1. To indicate aspects of Security Fabric security posture
2. To measure FortiManager storage capacity
3. To assign ADOM names
4. To determine administrator salaries

Correct Answer: 1

Explanation

The Security Fabric rating provides an indication of security posture based on supported Security Fabric checks and configuration conditions. It can help administrators identify areas where security configuration may need attention. The rating should be treated as an assessment of defined security controls rather than a measurement of system performance or storage capacity. Administrators can use the information to investigate identified issues and review whether recommended security configurations are appropriate for their environment.

Question 367

Why might an organization use global policies instead of duplicating identical rules in every ADOM?

1. To centralize common policy requirements
2. To prevent FortiManager from storing objects
3. To remove all local policies
4. To disable device discovery

Correct Answer: 1

Explanation

Global policies can centralize common security requirements that need to apply across multiple supported ADOMs. Without global policies, administrators may need to reproduce similar rules independently in each environment, increasing maintenance effort and the possibility of inconsistent changes. Centralization can simplify management while still allowing ADOM-specific policies where required. Administrators should verify policy order, assignment, and target compatibility because shared rules can have a broad deployment scope.

Question 368

Which object should an administrator review before changing a shared global address object?

1. Its dependencies and references
2. The FortiManager hostname
3. The browser cache
4. The device serial number only

Correct Answer: 1

Explanation

Before modifying a shared global address object, administrators should review its dependencies and references. Because a global object may be used by policies in multiple ADOMs, changing its value can affect more than one environment. Reviewing usage helps determine the potential scope of the change and whether dependent policies remain valid. Administrators should make significant global changes through a controlled workflow and verify affected configurations before installation.

Question 369

What is an important reason to review policy order before installing major changes?

1. Policy order can affect how traffic matches firewall rules
2. Policy order determines FortiManager disk capacity
3. Policy order controls administrator authentication
4. Policy order changes the FortiManager serial number

Correct Answer: 1

Explanation

Firewall policy order can affect which rule matches traffic because policies are evaluated according to their configured sequence and matching conditions. A newly added or modified rule may therefore change traffic handling if its position causes it to match before another policy. Before installing major policy changes, administrators should review policy order and the intended matching behavior. Installation previews and policy validation can provide additional opportunities to identify unexpected changes before deployment.

Question 370

What should an administrator do if a policy installation preview shows an unexpected rule change?

1. Install it immediately
2. Ignore the difference
3. Investigate the change before deployment
4. Delete the entire ADOM

Correct Answer: 3

Explanation

An unexpected change shown in an installation preview should be investigated before deployment. The administrator can review the affected policy, objects, recent revisions, and configuration differences to determine why the change appears. Installing an unexplained change could introduce unintended behavior into the target FortiGate. A controlled review allows the administrator to correct the policy or confirm that the change is intentional before proceeding with production installation.

Question 371

What can configuration revision comparison reveal?

1. Differences between selected configuration states
2. The physical temperature of a FortiGate
3. The administrator’s browser history
4. FortiGuard contract pricing

Correct Answer: 1

Explanation

Configuration revision comparison can reveal differences between selected configuration states. This is useful when administrators need to determine what changed between two points in time or investigate an unexpected modification. Reviewing differences can help identify policy edits, object changes, or other configuration adjustments. Revision comparison is especially valuable in environments with multiple administrators because it provides a historical reference that can support troubleshooting and controlled recovery decisions.

Question 372

A local administrator changes a FortiGate configuration outside FortiManager. What should the administrator expect?

1. Possible configuration drift between the device and FortiManager
2. Automatic creation of a global ADOM
3. Automatic firmware replacement
4. Deletion of all device groups

Correct Answer: 1

Explanation

A local configuration change made directly on a FortiGate can create configuration drift when the resulting device state differs from the configuration maintained by FortiManager. The administrator should compare the device and centralized configurations to determine what changed and whether the local modification should be incorporated. Installing a FortiManager-managed configuration without reviewing the difference could overwrite the local change. Proper synchronization and configuration review help maintain a predictable centralized management state.

Question 373

Which FortiManager information is most useful for determining why a script failed?

1. The script execution result and error information
2. The device wallpaper
3. The browser bookmarks
4. The administrator’s display resolution

Correct Answer: 1

Explanation

Script execution results and error information provide the most direct evidence when investigating a failed CLI script. The administrator can use the output to determine whether the failure resulted from invalid syntax, an unsupported command, an unavailable target, or another condition. Reviewing the target device and FortiOS version can provide additional context. Administrators should correct the identified problem and test the script again rather than repeatedly executing an unchanged script.

Question 374

What is a key consideration when applying the same CLI script to FortiGates running different FortiOS versions?

1. Command and syntax compatibility
2. Browser language settings
3. FortiManager logo configuration
4. Policy icon size

Correct Answer: 1

Explanation

Command and syntax compatibility is an important consideration when applying the same CLI script to FortiGates running different FortiOS versions. Commands can change between releases, and a command supported on one version may be unavailable or behave differently on another. Administrators should verify compatibility before broad deployment and test scripts where appropriate. Using device-specific variables can address value differences, but variables do not automatically solve command syntax incompatibility.

Question 375

What is one purpose of a configuration template in FortiManager?

1. To provide reusable configuration for managed devices
2. To replace all FortiGuard services
3. To monitor administrator login times
4. To delete device databases

Correct Answer: 1

Explanation

Configuration templates provide reusable configuration structures that can be applied to supported managed devices. They help administrators standardize recurring settings without manually rebuilding the same configuration for every FortiGate. Templates can work with device-specific values where supported, allowing a common configuration structure to adapt to individual devices. Administrators should validate template compatibility and variables before deployment because an incorrect template or value can produce configuration errors on target devices.

Question 376

Why are device-specific variables useful in configuration templates?

1. They allow a shared template to use different values for different devices
2. They automatically create new FortiManager appliances
3. They disable policy validation
4. They replace the need for ADOMs

Correct Answer: 1

Explanation

Device-specific variables allow a common configuration template to use different values for individual managed devices. For example, devices may require different addresses or interface-related values while still sharing the same overall configuration structure. This approach reduces the need to maintain separate templates for every device. Administrators should verify that each variable has the correct value and data type before deployment because an incorrect value can cause installation or operational problems.

Question 377

What should be checked when a configuration template fails on only one target device?

1. Device-specific compatibility and variable values
2. The FortiManager logo
3. Other administrators’ browser history
4. Global policy colors

Correct Answer: 1

Explanation

If a configuration template succeeds on several devices but fails on one, administrators should examine that device’s compatibility, FortiOS version, and assigned variable values. The affected FortiGate may have a different interface structure, unsupported feature, or incorrect device-specific value. Comparing the successful and failed targets can help isolate the difference. Reviewing the installation error and template output is also useful before modifying the template or attempting another deployment.

Question 378

What should administrators verify when FortiManager is configured as a local FortiGuard server?

1. Service status, connectivity, licensing, and update availability
2. Browser bookmarks and screen resolution
3. Policy icon colors
4. Administrator profile names only

Correct Answer: 1

Explanation

When FortiManager provides local FortiGuard services, administrators should verify that the relevant services are operational, required licenses or contracts are valid, network connectivity is available, and current update packages are accessible. A failure in any of these areas can prevent managed devices from receiving expected security updates. Reviewing connection status and service information helps isolate the problem. Administrators should also confirm that managed FortiGates are correctly configured to use the intended FortiGuard distribution path.

Question 379

What can cause a FortiGuard update request to fail when a server override is configured?

1. An incorrect or unreachable override server address
2. A valid policy package name
3. A completed configuration revision
4. A correct device group assignment

Correct Answer: 1

Explanation

An incorrect or unreachable override server address can prevent a FortiGate from contacting the intended FortiGuard service. When server override is used, administrators should verify the configured address, routing, firewall policies, DNS requirements where applicable, and the availability of the destination service. Connection status and relevant diagnostic information can help determine whether the problem is related to the override configuration or another part of the network path.

Question 380

What is the purpose of reviewing system resource usage during FortiManager troubleshooting?

1. To identify possible CPU, memory, or storage-related problems
2. To create new ADOMs automatically
3. To change policy ordering
4. To assign global policies

Correct Answer: 1

Explanation

Reviewing system resource usage helps administrators determine whether CPU, memory, or storage constraints are contributing to FortiManager problems. High resource consumption can affect system responsiveness and may be associated with specific processes or workloads. Administrators should review resource statistics together with process status, logs, and other diagnostic information. This approach helps distinguish resource-related problems from configuration or connectivity issues and provides a clearer basis for further troubleshooting.