{"id":24464,"date":"2026-09-29T07:59:23","date_gmt":"2026-09-29T07:59:23","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=24464"},"modified":"2026-09-29T07:59:23","modified_gmt":"2026-09-29T07:59:23","slug":"servicenow-cis-discovery-practice-test-questions-and-exam-dumps-part9-q161-180","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/servicenow-cis-discovery-practice-test-questions-and-exam-dumps-part9-q161-180\/","title":{"rendered":"ServiceNow CIS-Discovery Practice Test Questions and Exam Dumps Part9 Q161-180"},"content":{"rendered":"

View Full <\/b>ServiceNow CIS-Discovery Exam Dumps<\/b><\/a> and Practice Test Dumps.<\/b><\/h2>\n

 <\/p>\n

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

Which Discovery configuration determines the set of IP addresses that a scheduled Discovery run should scan?<\/b><\/p>\n

    \n
  1. Discovery IP range<\/span><\/li>\n
  2. User Criteria<\/span><\/li>\n
  3. Notification rule<\/span><\/li>\n
  4. Knowledge Base<\/span><\/li>\n<\/ol>\n

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

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

    Discovery IP ranges define the network addresses that a scheduled Discovery activity should target. By configuring appropriate ranges, administrators can control the scope of infrastructure that Discovery examines. This is particularly important in large environments where scanning every possible address would generate unnecessary traffic and processing. IP ranges can be associated with Discovery schedules and used alongside MID Server and Discovery Behavior configuration. User Criteria, notification rules, and Knowledge Bases do not determine the network targets of Discovery. Administrators should regularly review IP ranges as infrastructure changes to ensure that newly added systems are included when appropriate and excluded systems remain outside the intended Discovery scope.<\/span><\/p>\n

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

    Which feature can help distribute Discovery work among multiple MID Servers?<\/b><\/p>\n

      \n
    1. Knowledge Management<\/span><\/li>\n
    2. MID Server selection and configuration<\/span><\/li>\n
    3. Service Catalog<\/span><\/li>\n
    4. User Administration<\/span><\/li>\n<\/ol>\n

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

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

      MID Server selection and configuration can help distribute Discovery work across multiple MID Servers. Organizations commonly use several MID Servers when infrastructure is geographically distributed, separated into security zones, or too large for a single execution point. Appropriate configuration allows Discovery activities to use MID Servers that have the required network access and capabilities. This can improve scalability and reduce connectivity problems. Knowledge Management, Service Catalog, and User Administration do not determine how Discovery work is executed by MID Servers. When multiple MID Servers are available, administrators should also consider server status, capabilities, network reachability, and the requirements of each Discovery activity.<\/span><\/p>\n

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

      What is a major purpose of Discovery identification?<\/b><\/p>\n

        \n
      1. To determine which users can access reports<\/span><\/li>\n
      2. To decide whether discovered data matches an existing CI<\/span><\/li>\n
      3. To schedule recurring Discovery<\/span><\/li>\n
      4. To install MID Server software<\/span><\/li>\n<\/ol>\n

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

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

        Discovery identification determines whether information collected from a target corresponds to an existing configuration item in the CMDB or whether a new CI should be created. Identification relies on configured identification rules and identifying attributes. Accurate identification is essential for preventing duplicate CIs and maintaining reliable relationships between discovered infrastructure and CMDB records. Scheduling controls when Discovery runs, while MID Server installation establishes the execution infrastructure. Report access is unrelated to CI identification. When unexpected duplicate records appear, administrators should examine the identification rules, the identifying values collected from the target, and the Discovery execution details to determine why an existing CI was not correctly matched.<\/span><\/p>\n

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

        Which technology is commonly used by Discovery to access Windows systems remotely?<\/b><\/p>\n

          \n
        1. FTP<\/span><\/li>\n
        2. SMTP<\/span><\/li>\n
        3. WMI<\/span><\/li>\n
        4. IMAP<\/span><\/li>\n<\/ol>\n

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

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

          WMI, or Windows Management Instrumentation, is commonly used by Discovery to collect information from Windows systems. Through appropriate Windows credentials and connectivity, Discovery can retrieve details about hardware, operating-system configuration, software, services, and other supported information. The account used for Discovery must have sufficient permissions for the required operations, and network security controls must permit the necessary communication. FTP is primarily associated with file transfer, while SMTP and IMAP are email protocols. When Windows Discovery fails, administrators should examine credentials, permissions, network connectivity, firewall settings, and relevant Discovery logs to determine whether WMI access is available and functioning as expected.<\/span><\/p>\n

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

          What is a key reason to configure Discovery schedules carefully in a production environment?<\/b><\/p>\n

            \n
          1. To control scan timing, scope, and network impact<\/span><\/li>\n
          2. To eliminate CMDB identification<\/span><\/li>\n
          3. To disable all MID Servers<\/span><\/li>\n
          4. To prevent all infrastructure changes<\/span><\/li>\n<\/ol>\n

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

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

            Discovery schedules should be configured carefully because they determine when Discovery activities execute and what infrastructure is included. Poorly designed schedules can generate unnecessary network traffic, excessive MID Server workload, or scans during sensitive operational periods. Administrators should consider the size of the target range, network capacity, maintenance windows, and the frequency at which infrastructure information needs to be refreshed. Scheduling does not eliminate CMDB identification, disable MID Servers, or prevent infrastructure changes. Instead, it provides a controlled mechanism for keeping discovered configuration information current. Well-planned schedules help balance the need for fresh CMDB data with operational and network considerations.<\/span><\/p>\n

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

            Which Discovery mechanism is designed to provide targeted discovery of an individual device?<\/b><\/p>\n

              \n
            1. Data Import<\/span><\/li>\n
            2. Quick Discovery<\/span><\/li>\n
            3. Transform Map<\/span><\/li>\n
            4. Scheduled Reports<\/span><\/li>\n<\/ol>\n

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

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

              Quick Discovery provides a convenient way to run Discovery against a specific target rather than waiting for a broad scheduled scan. It is useful when administrators need to test connectivity, credentials, classification, or information collection for one known device. This makes Quick Discovery especially valuable during troubleshooting and configuration validation. Data Imports and Transform Maps are used for bringing external data into the platform and transforming it, while scheduled reports provide information for users rather than discovering infrastructure. After validating an individual target through Quick Discovery, administrators can use the results to identify configuration problems before expanding Discovery to larger network ranges.<\/span><\/p>\n

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

              What should an administrator verify if Discovery can reach a server but cannot retrieve required operating-system information?<\/b><\/p>\n

                \n
              1. The Knowledge Base category<\/span><\/li>\n
              2. The Service Catalog approval process<\/span><\/li>\n
              3. Credentials, permissions, and the applicable Discovery mechanism<\/span><\/li>\n
              4. User notification preferences<\/span><\/li>\n<\/ol>\n

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

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

                If Discovery can reach a server but cannot retrieve operating-system information, administrators should investigate credentials, permissions, and the mechanism being used to collect the information. Network reachability alone does not guarantee that Discovery can authenticate or execute the required commands. For example, the account may lack required privileges, a remote management service may be unavailable, or the selected Discovery content may not work correctly with the target configuration. Logs and pattern debugging can provide additional evidence. Knowledge categories, Service Catalog approvals, and notification preferences do not normally affect operating-system information collection. Troubleshooting should therefore focus on authentication and the actual data-collection process.<\/span><\/p>\n

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

                Which Discovery component provides an execution point between the ServiceNow instance and infrastructure targets?<\/b><\/p>\n

                  \n
                1. MID Server<\/span><\/li>\n
                2. CMDB relationship<\/span><\/li>\n
                3. Discovery Schedule<\/span><\/li>\n
                4. Identification Rule<\/span><\/li>\n<\/ol>\n

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

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

                  The MID Server acts as an execution point between the ServiceNow instance and infrastructure that needs to be discovered. It operates within the customer’s network and performs supported Discovery activities against target systems. This architecture allows the ServiceNow instance to coordinate Discovery while the MID Server handles communication with internal infrastructure. The MID Server must be properly configured, available, and capable of reaching the target systems. A CMDB relationship represents an association between configuration items, while a Discovery Schedule controls execution timing and an Identification Rule supports CI matching. Understanding the MID Server’s role is fundamental to designing and troubleshooting ServiceNow Discovery environments.<\/span><\/p>\n

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

                  Why is accurate classification important before detailed Discovery occurs?<\/b><\/p>\n

                    \n
                  1. It determines the appropriate Discovery path for the detected device type<\/span><\/li>\n
                  2. It changes user passwords<\/span><\/li>\n
                  3. It creates Service Catalog requests<\/span><\/li>\n
                  4. It assigns Knowledge article ownership<\/span><\/li>\n<\/ol>\n

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

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

                    Accurate classification helps Discovery determine the appropriate processing path for the detected device or system. Different technologies require different methods, credentials, patterns, probes, and commands to collect detailed information. If a target is classified incorrectly, Discovery may attempt an inappropriate exploration method and fail to collect useful data. Classification therefore provides an important foundation for subsequent Discovery processing. It is separate from identification, which determines the corresponding CMDB CI. User passwords, Service Catalog requests, and Knowledge article ownership are unrelated to Discovery classification. Administrators troubleshooting unexpected Discovery behavior should examine classification results when the wrong type of device appears to be processed.<\/span><\/p>\n

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

                    What can an administrator use to investigate communication or processing messages associated with Discovery activity?<\/b><\/p>\n

                      \n
                    1. ECC Queue and related Discovery logs<\/span><\/li>\n
                    2. Service Catalog cart<\/span><\/li>\n
                    3. Knowledge article editor<\/span><\/li>\n
                    4. User profile<\/span><\/li>\n<\/ol>\n

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

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

                      The ECC Queue and related Discovery logs can provide valuable information when investigating communication and processing associated with Discovery. The ECC Queue supports asynchronous communication between the ServiceNow instance and MID Server and can contain records related to commands, results, and processing. Reviewing relevant entries can help administrators determine whether work was sent to the expected MID Server and whether a response was returned. The Service Catalog cart, Knowledge article editor, and user profile do not provide the same Discovery execution information. When troubleshooting complex failures, administrators can combine ECC information with Discovery status, MID Server logs, and Pattern Designer debugging where applicable.<\/span><\/p>\n

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

                      Which approach can help prevent duplicate CIs when Discovery identifies infrastructure?<\/b><\/p>\n

                        \n
                      1. Disabling all Discovery activities<\/span><\/li>\n
                      2. Using appropriate identification rules and reliable identifying attributes<\/span><\/li>\n
                      3. Removing all CMDB records<\/span><\/li>\n
                      4. Avoiding credential configuration<\/span><\/li>\n<\/ol>\n

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

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

                        Appropriate identification rules and reliable identifying attributes are essential for preventing duplicate CIs during Discovery. Identification compares information collected from the target with existing CMDB records. If the identifying information is missing, inconsistent, or incorrectly configured, Discovery may not recognize an existing CI and may create another record. Administrators should therefore ensure that relevant identifiers are reliably collected and that identification rules are appropriate for the CI class. Disabling Discovery or deleting CMDB records does not solve the underlying identification problem. Avoiding credential configuration would also prevent Discovery from collecting required information. Good identification configuration is a core requirement for maintaining CMDB quality.<\/span><\/p>\n

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

                        What is one benefit of using a MID Server close to the infrastructure being discovered?<\/b><\/p>\n

                          \n
                        1. It can improve access to targets within restricted network environments<\/span><\/li>\n
                        2. It eliminates the need for credentials<\/span><\/li>\n
                        3. It removes the CMDB<\/span><\/li>\n
                        4. It prevents all firewall policies<\/span><\/li>\n<\/ol>\n

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

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

                          Placing a MID Server appropriately within the network can improve its ability to reach infrastructure located behind network boundaries or security controls. This is particularly useful when internal servers, network devices, or restricted zones cannot be reached directly from another network location. The MID Server provides an execution point that can communicate with both the ServiceNow instance and the target environment, subject to organizational firewall and security policies. It does not eliminate credentials, remove the CMDB, or bypass firewall policies. Administrators should design MID Server placement according to network architecture, required protocols, security requirements, and the systems that the MID Server needs to discover.<\/span><\/p>\n

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

                          Which item should be reviewed when a Discovery Pattern requires a command that fails on only some target servers?<\/b><\/p>\n

                            \n
                          1. User homepage settings<\/span><\/li>\n
                          2. Knowledge article permissions<\/span><\/li>\n
                          3. Target-specific operating-system configuration and permissions<\/span><\/li>\n
                          4. Service Catalog categories<\/span><\/li>\n<\/ol>\n

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

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

                            If a pattern command works on some servers but fails on others, administrators should investigate differences in target-specific operating-system configuration and permissions. Servers may run different operating-system versions, have different command availability, use different security policies, or provide different permissions to the Discovery account. The command may therefore succeed in one environment and fail in another. Pattern Designer debugging can help identify the exact step that is failing, while target-side logs and Discovery logs can provide additional information. User homepages, Knowledge permissions, and Service Catalog categories are unrelated to command execution on infrastructure targets. Comparing successful and unsuccessful targets is often an effective troubleshooting technique.<\/span><\/p>\n

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

                            Which Discovery protocol is commonly associated with Linux and UNIX remote access?<\/b><\/p>\n

                              \n
                            1. SSH<\/span><\/li>\n
                            2. SMTP<\/span><\/li>\n
                            3. SNMP only<\/span><\/li>\n
                            4. IMAP<\/span><\/li>\n<\/ol>\n

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

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

                              SSH is commonly used for remote access to Linux and UNIX systems during Discovery. Through SSH, Discovery can authenticate using appropriate credentials and execute supported commands to collect information about the target. The Discovery account needs sufficient permissions for the required operations, and network controls must allow the necessary SSH communication. SNMP may be used for network-management scenarios but is not the standard remote shell mechanism for Linux and UNIX Discovery. SMTP and IMAP are email protocols and do not provide the required infrastructure-management access. When Linux Discovery fails, administrators should verify SSH connectivity, credentials, permissions, firewall rules, and the applicable Discovery content.<\/span><\/p>\n

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

                              What is the primary purpose of a Discovery Behavior?<\/b><\/p>\n

                                \n
                              1. To determine how Discovery work should be executed for applicable targets<\/span><\/li>\n
                              2. To manage Knowledge article approvals<\/span><\/li>\n
                              3. To create user accounts<\/span><\/li>\n
                              4. To configure email templates<\/span><\/li>\n<\/ol>\n

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

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

                                A Discovery Behavior helps define how Discovery work should be executed for applicable targets. In environments with different network requirements or MID Server configurations, behaviors can help control aspects of Discovery execution and determine appropriate processing for particular Discovery activities. This provides administrators with additional control over how Discovery operates across infrastructure environments. Knowledge article approvals, user accounts, and email templates are unrelated to Discovery Behavior configuration. Administrators should understand the relationship between Discovery schedules, behaviors, IP ranges, MID Servers, and capabilities when designing Discovery for larger environments. Correct behavior configuration can help ensure that Discovery jobs use appropriate execution resources.<\/span><\/p>\n

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

                                What should be checked if a Discovery credential authenticates successfully but some attributes remain empty?<\/b><\/p>\n

                                  \n
                                1. Only the user’s profile<\/span><\/li>\n
                                2. The required permissions and the Discovery operation collecting those attributes<\/span><\/li>\n
                                3. Only the Service Catalog<\/span><\/li>\n
                                4. Only Knowledge Management<\/span><\/li>\n<\/ol>\n

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

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

                                  Successful authentication does not necessarily mean that Discovery has sufficient permissions to collect every required attribute. Some information may require additional privileges, specific commands, management interfaces, or services on the target. Administrators should therefore review the permissions assigned to the Discovery account and determine which Discovery operation is responsible for collecting the missing information. Pattern execution details, probe results, sensors, and Discovery logs can help identify where collection stops. User profiles, Service Catalog configuration, and Knowledge Management generally do not affect infrastructure attribute collection. Troubleshooting should focus on the exact attributes that are missing and the mechanism used by Discovery to retrieve them.<\/span><\/p>\n

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

                                  Which CMDB outcome should administrators investigate when multiple records represent the same physical server?<\/b><\/p>\n

                                    \n
                                  1. Duplicate CIs caused by identification or data-quality issues<\/span><\/li>\n
                                  2. Email notification delays<\/span><\/li>\n
                                  3. Knowledge article duplication<\/span><\/li>\n
                                  4. Service Catalog approval failures<\/span><\/li>\n<\/ol>\n

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

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

                                    Multiple CMDB records representing the same physical server indicate a potential CI duplication or data-quality problem. Administrators should investigate identification rules, identifying attributes, Discovery sources, and the information collected from the target. Duplicate records may occur when Discovery cannot match a target to the correct existing CI or when different data sources create overlapping records. Resolving the underlying identification or data-management issue is more effective than simply deleting records without understanding why they were created. Email notifications, Knowledge articles, and Service Catalog approvals are not normally responsible for CI duplication. Maintaining reliable identification logic is essential for a healthy CMDB.<\/span><\/p>\n

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

                                    Which factor should be considered when selecting a MID Server for Discovery?<\/b><\/p>\n

                                      \n
                                    1. The user’s preferred language<\/span><\/li>\n
                                    2. Knowledge article ownership<\/span><\/li>\n
                                    3. Network reachability and required capabilities<\/span><\/li>\n
                                    4. Service Catalog item price<\/span><\/li>\n<\/ol>\n

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

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

                                      Network reachability and required capabilities are important factors when selecting a MID Server for Discovery. The MID Server must be able to communicate with the target systems and have the capabilities required for the Discovery operation. In larger environments, different MID Servers may serve different network segments, security zones, or technologies. Administrators should therefore evaluate the target’s location, routing, firewall rules, MID Server status, and capability configuration. User language, Knowledge article ownership, and Service Catalog pricing do not determine whether a MID Server is suitable for Discovery. Correct selection helps prevent execution failures caused by inappropriate network placement or missing capabilities.<\/span><\/p>\n

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

                                      What is a useful reason to monitor Discovery status regularly?<\/b><\/p>\n

                                        \n
                                      1. To identify failures, incomplete results, and unexpected Discovery behavior<\/span><\/li>\n
                                      2. To replace all CMDB identification rules<\/span><\/li>\n
                                      3. To eliminate network security controls<\/span><\/li>\n
                                      4. To prevent users from logging in<\/span><\/li>\n<\/ol>\n

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

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

                                        Regularly monitoring Discovery status helps administrators identify failures, incomplete results, unexpected classifications, authentication problems, and other issues that could affect CMDB accuracy. Discovery is often scheduled to run repeatedly, so a problem that remains unnoticed can cause configuration information to become increasingly outdated. Monitoring allows administrators to investigate issues involving MID Servers, credentials, target connectivity, patterns, probes, or identification. Discovery status monitoring does not replace identification rules or eliminate network security controls, and it has no purpose related to preventing users from logging in. Consistent monitoring is therefore an important operational practice for maintaining reliable and current Discovery results.<\/span><\/p>\n

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

                                        Which combination provides the strongest foundation for reliable infrastructure Discovery?<\/b><\/p>\n

                                          \n
                                        1. Accurate scope, available MID Servers, valid credentials, appropriate Discovery content, and proper identification<\/span><\/li>\n
                                        2. Only a large IP range<\/span><\/li>\n
                                        3. Only a Service Catalog workflow<\/span><\/li>\n
                                        4. Only Knowledge Management<\/span><\/li>\n<\/ol>\n

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

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

                                          Reliable infrastructure Discovery depends on several components working together. The target scope must be accurate, appropriate MID Servers must be available and able to reach the infrastructure, credentials must provide required access, and suitable Discovery content must collect the necessary information. Identification must then correctly associate discovered information with existing CIs or create appropriate new records. A large IP range alone does not guarantee successful Discovery because network access, authentication, classification, exploration, and identification are also required. Service Catalog workflows and Knowledge Management do not provide the core infrastructure Discovery capabilities. A complete, well-monitored configuration is therefore necessary for producing useful and trustworthy CMDB data.<\/span><\/p>\n

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

                                          View Full ServiceNow CIS-Discovery Exam Dumps and Practice Test Dumps.   Question 161 Which Discovery configuration determines the set of IP addresses that a scheduled Discovery run should scan? Discovery IP range User Criteria Notification rule Knowledge Base Correct Answer: 1 Explanation Discovery IP ranges define the network addresses that a scheduled Discovery activity should […]<\/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\/24464"}],"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=24464"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/24464\/revisions"}],"predecessor-version":[{"id":24465,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/24464\/revisions\/24465"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=24464"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=24464"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=24464"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}