{"id":22093,"date":"2026-09-25T10:50:44","date_gmt":"2026-09-25T10:50:44","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=22093"},"modified":"2026-09-25T10:50:44","modified_gmt":"2026-09-25T10:50:44","slug":"fortinet-fcp_fmg_ad-7-6-practice-test-questions-and-exam-dumps-part14-q261-280","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/fortinet-fcp_fmg_ad-7-6-practice-test-questions-and-exam-dumps-part14-q261-280\/","title":{"rendered":"Fortinet FCP_FMG_AD-7.6 Practice Test Questions and Exam Dumps Part14 Q261-280"},"content":{"rendered":"

View Full <\/b>Fortinet FCP_FMG_AD-7.6 Exam Dumps<\/b><\/a> and Practice Test Dumps.<\/b><\/h2>\n

 <\/p>\n

Question 261<\/b><\/h3>\n

What is the purpose of the Global Database ADOM?<\/b><\/p>\n

    \n
  1. To manage endpoint devices<\/span><\/li>\n
  2. To store administrator passwords<\/span><\/li>\n
  3. To provide shared policies and objects across ADOMs<\/span><\/li>\n
  4. To replace FortiAnalyzer<\/span><\/li>\n<\/ol>\n

    Correct Answer: 3<\/b><\/p>\n

    Explanation<\/b><\/p>\n

    The Global Database ADOM provides a centralized location for shared policies and objects that can be used across multiple ADOMs. This is useful when an organization needs common configuration elements to be maintained consistently rather than recreated separately in every ADOM. Global policies and objects can simplify administration in larger environments. Administrators should understand the scope of global configurations before making changes because shared elements can affect multiple ADOMs and managed devices.<\/span><\/p>\n

    Question 262<\/b><\/h3>\n

    Which type of policy can be used as a shared policy across multiple ADOMs?<\/b><\/p>\n

      \n
    1. Global policy<\/span><\/li>\n
    2. Local device policy only<\/span><\/li>\n
    3. Endpoint policy<\/span><\/li>\n
    4. Firmware policy<\/span><\/li>\n<\/ol>\n

      Correct Answer: 1<\/b><\/p>\n

      Explanation<\/b><\/p>\n

      Global policies can be used to provide shared policy elements across multiple ADOMs when the FortiManager global database is configured for that purpose. This can reduce duplication and help maintain common security requirements across different administrative domains. Administrators can define shared policies centrally and assign or incorporate them according to the supported global policy workflow. Because changes can affect multiple environments, administrators should review the intended scope before installing global policy changes.<\/span><\/p>\n

      Question 263<\/b><\/h3>\n

      What is a major benefit of shared global objects?<\/b><\/p>\n

        \n
      1. They reduce duplicate object definitions<\/span><\/li>\n
      2. They disable policy installation<\/span><\/li>\n
      3. They replace FortiGate HA<\/span><\/li>\n
      4. They remove all ADOMs<\/span><\/li>\n<\/ol>\n

        Correct Answer: 1<\/b><\/p>\n

        Explanation<\/b><\/p>\n

        Shared global objects allow commonly used configuration elements to be maintained centrally instead of recreated separately in multiple ADOMs. This can reduce duplication and make administration more consistent. When an organization uses the same object definitions across multiple environments, central management can simplify updates and reduce configuration inconsistencies. Administrators should still review object dependencies and scope before modifying shared objects because a change to a global object can affect multiple ADOMs or policy packages.<\/span><\/p>\n

        Question 264<\/b><\/h3>\n

        What does assigning a global policy package to an ADOM accomplish?<\/b><\/p>\n

          \n
        1. Makes the global policy available within that ADOM<\/span><\/li>\n
        2. Deletes the ADOM<\/span><\/li>\n
        3. Changes the FortiGate serial number<\/span><\/li>\n
        4. Disables FortiGuard<\/span><\/li>\n<\/ol>\n

          Correct Answer: 1<\/b><\/p>\n

          Explanation<\/b><\/p>\n

          Assigning a global policy package to an ADOM makes the relevant global policy available for use within that administrative domain. This allows common policy elements to be incorporated into the management workflow for selected ADOMs. The assignment does not replace the ADOM or automatically change unrelated device settings. Administrators should confirm the intended ADOM assignment and review the resulting policy structure before installation to ensure that shared policies are applied to the correct environments.<\/span><\/p>\n

          Question 265<\/b><\/h3>\n

          What can Fabric View display in FortiManager?<\/b><\/p>\n

            \n
          1. Security Fabric relationships and topology<\/span><\/li>\n
          2. Administrator passwords<\/span><\/li>\n
          3. FortiGuard invoices<\/span><\/li>\n
          4. Policy package backups only<\/span><\/li>\n<\/ol>\n

            Correct Answer: 1<\/b><\/p>\n

            Explanation<\/b><\/p>\n

            Fabric View can provide a visual representation of Security Fabric relationships and topology within a Fortinet environment. This can help administrators understand how Fortinet devices are connected and how they relate to one another within the Security Fabric. The view can be useful when reviewing network structure or troubleshooting device relationships. It does not replace configuration management or policy installation functions, but it can provide valuable visibility into the broader managed environment.<\/span><\/p>\n

            Question 266<\/b><\/h3>\n

            What is the purpose of Security Fabric topology information?<\/b><\/p>\n

              \n
            1. To understand relationships between connected Fortinet devices<\/span><\/li>\n
            2. To create administrator accounts<\/span><\/li>\n
            3. To replace ADOM permissions<\/span><\/li>\n
            4. To modify FortiGuard contracts<\/span><\/li>\n<\/ol>\n

              Correct Answer: 1<\/b><\/p>\n

              Explanation<\/b><\/p>\n

              Security Fabric topology information helps administrators understand how connected Fortinet devices relate to one another. This visibility can make it easier to identify device relationships and understand the structure of a Security Fabric deployment. When troubleshooting connectivity or configuration issues, topology information can provide useful context about which devices are connected and how they interact. It is a visibility and management aid rather than a replacement for the underlying device configuration or policy management processes.<\/span><\/p>\n

              Question 267<\/b><\/h3>\n

              Which FortiManager feature can help display the security posture of a Security Fabric?<\/b><\/p>\n

                \n
              1. Security Rating<\/span><\/li>\n
              2. Device Group<\/span><\/li>\n
              3. CLI Script<\/span><\/li>\n
              4. Revision History<\/span><\/li>\n<\/ol>\n

                Correct Answer: 1<\/b><\/p>\n

                Explanation<\/b><\/p>\n

                Security Rating provides information related to the security posture of a Security Fabric environment. It can help administrators identify areas that may require attention and provides a centralized view associated with the security configuration of connected Fortinet devices. Security Rating is different from policy packages and device groups because it focuses on security posture rather than configuration organization. Administrators can use the information as part of broader monitoring and security management activities.<\/span><\/p>\n

                Question 268<\/b><\/h3>\n

                What is the main purpose of FortiManager’s policy workflow?<\/b><\/p>\n

                  \n
                1. To control how policy changes are prepared and deployed<\/span><\/li>\n
                2. To replace FortiGate hardware<\/span><\/li>\n
                3. To create Internet connections<\/span><\/li>\n
                4. To manage administrator email<\/span><\/li>\n<\/ol>\n

                  Correct Answer: 1<\/b><\/p>\n

                  Explanation<\/b><\/p>\n

                  The policy workflow provides a structured process for creating, reviewing, validating, and deploying firewall policy changes. Instead of immediately changing each FortiGate independently, administrators can manage policies centrally and then install approved configurations on selected devices. The workflow can include object management, target selection, validation, installation preview, and deployment. Following a structured workflow reduces accidental changes and makes centralized policy administration easier to control.<\/span><\/p>\n

                  Question 269<\/b><\/h3>\n

                  What should be reviewed before changing a shared global object?<\/b><\/p>\n

                    \n
                  1. Its usage across relevant configurations<\/span><\/li>\n
                  2. The monitor size<\/span><\/li>\n
                  3. The FortiManager hostname only<\/span><\/li>\n
                  4. The number of browser windows<\/span><\/li>\n<\/ol>\n

                    Correct Answer: 1<\/b><\/p>\n

                    Explanation<\/b><\/p>\n

                    Before changing a shared global object, administrators should review where the object is used and understand which configurations may depend on it. Because a global object can be referenced across multiple ADOMs, a modification may affect more than one environment. Reviewing object usage and dependencies helps administrators predict the potential impact of the change. This is especially important for address, service, and other reusable objects that may appear in multiple policy packages.<\/span><\/p>\n

                    Question 270<\/b><\/h3>\n

                    What is an advantage of using a centralized policy package?<\/b><\/p>\n

                      \n
                    1. Consistent policy management across selected devices<\/span><\/li>\n
                    2. Automatic hardware replacement<\/span><\/li>\n
                    3. Removal of all device configurations<\/span><\/li>\n
                    4. Elimination of FortiGuard services<\/span><\/li>\n<\/ol>\n

                      Correct Answer: 1<\/b><\/p>\n

                      Explanation<\/b><\/p>\n

                      A centralized policy package allows administrators to manage related firewall policies from FortiManager and deploy them to selected managed FortiGate devices. This can improve consistency because common policy requirements can be maintained from one management platform. Device-specific differences can be handled through supported mappings or variables where required. Centralized policy management also provides a controlled installation process, allowing administrators to review targets and proposed changes before deployment.<\/span><\/p>\n

                      Question 271<\/b><\/h3>\n

                      Why might an administrator use separate policy packages for different environments?<\/b><\/p>\n

                        \n
                      1. To apply environment-specific policies<\/span><\/li>\n
                      2. To disable ADOMs<\/span><\/li>\n
                      3. To remove object references<\/span><\/li>\n
                      4. To stop FortiManager logging<\/span><\/li>\n<\/ol>\n

                        Correct Answer: 1<\/b><\/p>\n

                        Explanation<\/b><\/p>\n

                        Separate policy packages can be useful when different environments have different security requirements. For example, production, testing, and branch environments may require different firewall policies even though they are managed from the same FortiManager. Using separate packages allows administrators to maintain those differences while still benefiting from centralized management. The package structure should reflect the organization’s operational requirements and should be reviewed regularly to avoid unnecessary duplication or inconsistent policy definitions.<\/span><\/p>\n

                        Question 272<\/b><\/h3>\n

                        What does policy cloning help administrators do?<\/b><\/p>\n

                          \n
                        1. Create a copy of an existing policy package or policy configuration<\/span><\/li>\n
                        2. Repair a damaged hard drive<\/span><\/li>\n
                        3. Replace FortiGate firmware<\/span><\/li>\n
                        4. Create a FortiGuard server<\/span><\/li>\n<\/ol>\n

                          Correct Answer: 1<\/b><\/p>\n

                          Explanation<\/b><\/p>\n

                          Policy cloning allows administrators to create a copy of an existing policy or policy package as a starting point for another configuration. This can save time when a new environment requires a configuration similar to an existing one. After cloning, administrators should review objects, interfaces, targets, and other environment-specific settings before installation. Simply cloning a configuration does not guarantee that it is appropriate for the new target, so validation and review remain important parts of the deployment process.<\/span><\/p>\n

                          Question 273<\/b><\/h3>\n

                          Which setting controls which FortiManager features are visible to administrators?<\/b><\/p>\n

                            \n
                          1. Feature visibility<\/span><\/li>\n
                          2. FGFM keepalive<\/span><\/li>\n
                          3. FortiGuard override<\/span><\/li>\n
                          4. Device discovery<\/span><\/li>\n<\/ol>\n

                            Correct Answer: 1<\/b><\/p>\n

                            Explanation<\/b><\/p>\n

                            Feature visibility controls which configuration features are displayed within the FortiManager interface. Administrators can use it to simplify the management interface by showing features that are relevant to their environment. If a required configuration option is not visible, checking feature visibility can help determine whether the feature has been hidden. Feature visibility does not remove the underlying configuration from the system; it primarily controls the available interface elements presented to administrators.<\/span><\/p>\n

                            Question 274<\/b><\/h3>\n

                            What is the purpose of installation preview?<\/b><\/p>\n

                              \n
                            1. To review proposed changes before installation<\/span><\/li>\n
                            2. To renew device licenses<\/span><\/li>\n
                            3. To create new ADOMs<\/span><\/li>\n
                            4. To monitor physical temperature<\/span><\/li>\n<\/ol>\n

                              Correct Answer: 1<\/b><\/p>\n

                              Explanation<\/b><\/p>\n

                              Installation preview provides administrators with an opportunity to examine proposed configuration changes before they are deployed to managed devices. Reviewing the preview can reveal unexpected modifications, target issues, or configuration differences that require attention. This is particularly valuable in production environments where an incorrect deployment can affect network traffic or security controls. Administrators should use the preview together with validation and target verification to maintain a controlled installation process.<\/span><\/p>\n

                              Question 275<\/b><\/h3>\n

                              What can a duplicate-object review prevent?<\/b><\/p>\n

                                \n
                              1. Unnecessary object duplication and configuration confusion<\/span><\/li>\n
                              2. FortiGate hardware failure<\/span><\/li>\n
                              3. FortiManager license expiration<\/span><\/li>\n
                              4. FGFM communication<\/span><\/li>\n<\/ol>\n

                                Correct Answer: 1<\/b><\/p>\n

                                Explanation<\/b><\/p>\n

                                Reviewing duplicate objects can help reduce unnecessary configuration duplication and make object management clearer. Multiple objects with identical or nearly identical definitions can make policies harder to maintain and may lead to confusion when administrators modify configurations. Before consolidating duplicates, administrators should review references and dependencies to ensure that removing one object will not break existing policies. A controlled cleanup process can improve configuration organization without introducing unexpected policy changes.<\/span><\/p>\n

                                Question 276<\/b><\/h3>\n

                                What should be checked when an interface mapping causes an installation error?<\/b><\/p>\n

                                  \n
                                1. The mapped interfaces and target device<\/span><\/li>\n
                                2. The administrator’s browser<\/span><\/li>\n
                                3. The FortiManager display language<\/span><\/li>\n
                                4. The number of revisions only<\/span><\/li>\n<\/ol>\n

                                  Correct Answer: 1<\/b><\/p>\n

                                  Explanation<\/b><\/p>\n

                                  When interface mapping causes an installation error, administrators should verify that the mapped interfaces actually exist on the target FortiGate and correspond to the intended network roles. Interface names can vary between devices, so a mapping that works for one device may not be valid for another. Reviewing the policy, target device, and interface configuration can reveal incorrect or missing mappings. Correcting the mapping before retrying the installation can resolve the deployment problem.<\/span><\/p>\n

                                  Question 277<\/b><\/h3>\n

                                  What is the purpose of device-specific variables?<\/b><\/p>\n

                                    \n
                                  1. To supply different values to shared configurations<\/span><\/li>\n
                                  2. To disable policy packages<\/span><\/li>\n
                                  3. To create global administrators<\/span><\/li>\n
                                  4. To replace FortiManager databases<\/span><\/li>\n<\/ol>\n

                                    Correct Answer: 1<\/b><\/p>\n

                                    Explanation<\/b><\/p>\n

                                    Device-specific variables allow a common configuration structure to use different values for individual managed devices. This is useful when several FortiGates require similar policies but have different addresses, interfaces, hostnames, or other device-dependent information. Instead of creating an entirely separate configuration for every device, administrators can maintain reusable logic and assign appropriate values. Proper variable assignment should be verified before installation because an incorrect value can result in an invalid or unintended configuration.<\/span><\/p>\n

                                    Question 278<\/b><\/h3>\n

                                    What should be verified when a shared configuration is deployed to several FortiGates?<\/b><\/p>\n

                                      \n
                                    1. Device-specific values and installation targets<\/span><\/li>\n
                                    2. Only the FortiManager hostname<\/span><\/li>\n
                                    3. Browser cache<\/span><\/li>\n
                                    4. FortiGuard invoice number<\/span><\/li>\n<\/ol>\n

                                      Correct Answer: 1<\/b><\/p>\n

                                      Explanation<\/b><\/p>\n

                                      When deploying shared configurations to multiple FortiGates, administrators should verify both the intended installation targets and any device-specific values used by the configuration. Shared policies may depend on variables, interface mappings, or other device-specific information. An incorrect value could cause an installation failure or result in an unintended configuration on one device. Reviewing the installation preview and validation results before deployment provides an additional safeguard against these problems.<\/span><\/p>\n

                                      Question 279<\/b><\/h3>\n

                                      Which action is appropriate after correcting a failed policy configuration?<\/b><\/p>\n

                                        \n
                                      1. Validate the corrected configuration before reinstalling<\/span><\/li>\n
                                      2. Delete the ADOM<\/span><\/li>\n
                                      3. Disable all FortiGuard services<\/span><\/li>\n
                                      4. Remove the target device<\/span><\/li>\n<\/ol>\n

                                        Correct Answer: 1<\/b><\/p>\n

                                        Explanation<\/b><\/p>\n

                                        After correcting a policy configuration that previously failed, administrators should validate the revised configuration before attempting another installation. Validation can identify remaining problems with policies, objects, interfaces, or other dependencies. The installation target should also be confirmed before deployment. Reinstalling without validating the correction may simply reproduce the same failure. A controlled sequence of correction, validation, preview, and installation helps reduce repeated deployment problems.<\/span><\/p>\n

                                        Question 280<\/b><\/h3>\n

                                        Why is controlled policy deployment important?<\/b><\/p>\n

                                          \n
                                        1. It reduces the risk of unintended configuration changes<\/span><\/li>\n
                                        2. It eliminates the need for backups<\/span><\/li>\n
                                        3. It disables FortiManager logging<\/span><\/li>\n
                                        4. It removes all configuration dependencies<\/span><\/li>\n<\/ol>\n

                                          Correct Answer: 1<\/b><\/p>\n

                                          Explanation<\/b><\/p>\n

                                          Controlled policy deployment reduces the risk of accidentally changing the wrong device or deploying an incorrect configuration. Administrators can review policy changes, validate configurations, confirm installation targets, and examine the installation preview before committing changes. This structured approach is especially valuable in environments where multiple FortiGates are managed from one FortiManager. Controlled deployment does not eliminate the need for backups or change management, but it provides important safeguards against configuration errors.<\/span><\/p>\n

                                           <\/p>\n","protected":false},"excerpt":{"rendered":"

                                          View Full Fortinet FCP_FMG_AD-7.6 Exam Dumps and Practice Test Dumps.   Question 261 What is the purpose of the Global Database ADOM? To manage endpoint devices To store administrator passwords To provide shared policies and objects across ADOMs To replace FortiAnalyzer Correct Answer: 3 Explanation The Global Database ADOM provides a centralized location for shared […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1648,1647],"tags":[],"_links":{"self":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/22093"}],"collection":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/comments?post=22093"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/22093\/revisions"}],"predecessor-version":[{"id":22094,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/22093\/revisions\/22094"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=22093"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=22093"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=22093"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}