{"id":20302,"date":"2026-09-23T12:28:02","date_gmt":"2026-09-23T12:28:02","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=20302"},"modified":"2026-09-23T12:28:02","modified_gmt":"2026-09-23T12:28:02","slug":"fortinet-nse7_soc_ar-7-6-practice-test-questions-and-exam-dumps-part8-q141-160","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/fortinet-nse7_soc_ar-7-6-practice-test-questions-and-exam-dumps-part8-q141-160\/","title":{"rendered":"Fortinet NSE7_SOC_AR-7.6 Practice Test Questions and Exam Dumps Part8 Q141-160"},"content":{"rendered":"

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


\n<\/b>Q141. What is the primary value of using the MITRE ATT&CK framework during a SOC investigation?<\/b><\/p>\n

    \n
  1. <\/b> It automatically attributes an attack to a specific threat actor<\/span><\/li>\n
  2. <\/b> It replaces the need for event collection<\/span><\/li>\n
  3. <\/b> It assigns incident owners in FortiSOAR<\/span><\/li>\n
  4. <\/b> It provides a structured way to describe adversary tactics and techniques observed during an attack<\/span><\/li>\n<\/ol>\n

    Correct Answer: 4. It provides a structured way to describe adversary tactics and techniques observed during an attack<\/b><\/p>\n

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

    MITRE ATT&CK provides a common framework for describing adversary behavior using tactics and techniques. SOC analysts can map observed activity such as credential access, discovery, persistence, or lateral movement to known ATT&CK concepts. This makes investigations easier to communicate and can reveal which parts of an attack sequence have already been observed and which techniques may deserve additional hunting. ATT&CK does not automatically identify the attacker or remove the need for telemetry. Fortinet\u2019s current Security Operations Architect training explicitly includes the MITRE ATT&CK Enterprise Matrix as part of SOC concepts and security frameworks.<\/span><\/p>\n

    Q142. What does the Cyber Kill Chain primarily help a SOC analyst understand?<\/b><\/p>\n

      \n
    1. <\/b> The progression of an attack through recognizable stages from preparation through objective completion<\/span><\/li>\n
    2. <\/b> The number of FortiSOAR connectors installed<\/span><\/li>\n
    3. <\/b> The number of analysts assigned to each shift<\/span><\/li>\n
    4. <\/b> The storage capacity of FortiSIEM<\/span><\/li>\n<\/ol>\n

      Correct Answer: 1. The progression of an attack through recognizable stages from preparation through objective completion<\/b><\/p>\n

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

      The Cyber Kill Chain provides a high-level model for understanding how an attack can progress through stages such as reconnaissance, delivery, exploitation, installation, command and control, and actions on objectives. Analysts can use this model to organize observed activity and consider what may have occurred before or after a detected event. It complements frameworks such as MITRE ATT&CK rather than replacing detailed event analysis. Fortinet\u2019s Security Operations Architect course specifically includes the Cyber Kill Chain within its SOC concepts curriculum.<\/span><\/p>\n

      Q143. Which action BEST represents attack-surface reduction?<\/b><\/p>\n

        \n
      1. <\/b> Increasing the number of exposed administrative services<\/span><\/li>\n
      2. <\/b> Allowing all users local administrator privileges<\/span><\/li>\n
      3. <\/b> Removing unnecessary services, reducing excessive privileges, and closing unused exposure points<\/span><\/li>\n
      4. <\/b> Disabling security logging<\/span><\/li>\n<\/ol>\n

        Correct Answer: 3. Removing unnecessary services, reducing excessive privileges, and closing unused exposure points<\/b><\/p>\n

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

        Attack-surface reduction lowers the number of opportunities available to an adversary. Examples include disabling unused services, patching vulnerable software, removing unnecessary Internet exposure, restricting privileges, and enforcing stronger access controls. The objective is to make compromise more difficult and limit what an attacker can reach if one control fails. Increasing administrative exposure or turning off logging does the opposite by increasing risk or reducing visibility. Fortinet\u2019s current Security Operations Architect training explicitly includes identifying and reducing the attack surface as a SOC architecture and framework objective.<\/span><\/p>\n

        Q144. What is the BEST distinction between prevention and detection controls in a SOC architecture?<\/b><\/p>\n

          \n
        1. <\/b> Detection controls always block attacks automatically<\/span><\/li>\n
        2. <\/b> Prevention attempts to stop unwanted activity, while detection identifies activity that may have occurred or bypassed preventive controls<\/span><\/li>\n
        3. <\/b> Prevention is handled only by FortiSOAR<\/span><\/li>\n
        4. <\/b> Detection eliminates the need for response<\/span><\/li>\n<\/ol>\n

          Correct Answer: 2. Prevention attempts to stop unwanted activity, while detection identifies activity that may have occurred or bypassed preventive controls<\/b><\/p>\n

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

          Preventive controls are intended to stop malicious or unauthorized activity before it succeeds, while detection controls identify suspicious behavior that occurs despite, around, or beyond those preventive measures. Mature SOC architecture uses both because no preventive technology can block every attack. Detection then supports investigation, containment, and response. FortiSIEM contributes heavily to visibility and detection, while FortiSOAR can orchestrate response. Detection does not automatically imply blocking, and neither technology eliminates the need for analysts, processes, or layered security controls.<\/span><\/p>\n

          Q145. Why is data-source coverage important when designing a FortiSIEM deployment?<\/b><\/p>\n

            \n
          1. <\/b> Missing telemetry can create visibility gaps that prevent rules and investigations from seeing relevant attacker activity<\/span><\/li>\n
          2. <\/b> More data automatically means every detection is accurate<\/span><\/li>\n
          3. <\/b> FortiSIEM can detect any behavior even without relevant logs<\/span><\/li>\n
          4. <\/b> Data sources matter only after an incident is closed<\/span><\/li>\n<\/ol>\n

            Correct Answer: 1. Missing telemetry can create visibility gaps that prevent rules and investigations from seeing relevant attacker activity<\/b><\/p>\n

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

            Detection quality depends on the availability of relevant data. If authentication, endpoint, DNS, firewall, cloud, or application telemetry is missing, a correlation rule may not receive the evidence needed to identify suspicious behavior. Investigators may also be unable to reconstruct an attack accurately. More data is not automatically better; useful coverage should be balanced with parsing, normalization, retention, and operational relevance. Fortinet\u2019s current course specifically includes identifying and configuring data sources and configuring data ingestion as part of Security Operations Architect training.<\/span><\/p>\n

            Q146. A newly added security device is sending logs to FortiSIEM, but useful fields are not appearing correctly in searches. What should be investigated FIRST?<\/b><\/p>\n

              \n
            1. <\/b> Analyst shift configuration<\/span><\/li>\n
            2. <\/b> FortiSOAR incident ownership<\/span><\/li>\n
            3. <\/b> War-room permissions<\/span><\/li>\n
            4. <\/b> Parsing and normalization of the incoming event data<\/span><\/li>\n<\/ol>\n

              Correct Answer: 4. Parsing and normalization of the incoming event data<\/b><\/p>\n

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

              Receiving raw logs does not guarantee that FortiSIEM can use their information effectively. The platform must parse important values and map them into meaningful normalized fields that can be searched, correlated, and displayed consistently. If usernames, source addresses, event types, or other values are missing or incorrect, detection rules and investigations may behave unexpectedly. Workforce and war-room settings are unrelated to event-field extraction. Fortinet\u2019s Security Operations Architect course includes data-source configuration and ingestion because reliable telemetry is foundational to SIEM detection and investigation.<\/span><\/p>\n

              Q147. Why should a SOC validate that a newly onboarded log source is producing expected events before relying on it in a correlation rule?<\/b><\/p>\n

                \n
              1. <\/b> To confirm that the source, parsing, fields, and event flow provide the evidence the rule expects<\/span><\/li>\n
              2. <\/b> To make FortiSOAR connectors unnecessary<\/span><\/li>\n
              3. <\/b> To increase the severity of all incidents<\/span><\/li>\n
              4. <\/b> To prevent FortiSIEM from storing events<\/span><\/li>\n<\/ol>\n

                Correct Answer: 2. To confirm that the source, parsing, fields, and event flow provide the evidence the rule expects<\/b><\/p>\n

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

                A correlation rule can only operate correctly when its required data is actually available and normalized as expected. Before relying on a new source, administrators should verify that events are arriving consistently, timestamps are useful, important fields are populated, and the expected event types can be queried. Otherwise, the SOC may assume it has detection coverage that does not really exist. Validation also helps identify filtering or ingestion problems early. Data onboarding is therefore not complete simply because packets or raw logs reach FortiSIEM.<\/span><\/p>\n

                Q148. What is the primary purpose of the preparation phase in a structured incident-response process?<\/b><\/p>\n

                  \n
                1. <\/b> To eradicate malware before any incident occurs<\/span><\/li>\n
                2. <\/b> To close incidents automatically<\/span><\/li>\n
                3. <\/b> To establish people, tools, procedures, communications, and capabilities needed before incidents occur<\/span><\/li>\n
                4. <\/b> To disable all detection rules until an attack is confirmed<\/span><\/li>\n<\/ol>\n

                  Correct Answer: 3. To establish people, tools, procedures, communications, and capabilities needed before incidents occur<\/b><\/p>\n

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

                  Preparation ensures that the organization is ready to respond effectively when an incident occurs. This includes documented processes, trained personnel, communication paths, detection and response tools, access to required systems, escalation procedures, and appropriate technical controls. Without preparation, responders can lose valuable time determining responsibilities or obtaining access during an active incident. Fortinet\u2019s Security Operations Architect course specifically includes the NIST SP 800-61 incident-handling process, where preparation is a foundational concept.<\/span><\/p>\n

                  Q149. After containment, what is the main objective of eradication?<\/b><\/p>\n

                    \n
                  1. <\/b> Remove the attacker\u2019s artifacts and address the cause or mechanisms that enabled continued compromise<\/span><\/li>\n
                  2. <\/b> Delete every security log<\/span><\/li>\n
                  3. <\/b> Restore the system before removing malicious artifacts<\/span><\/li>\n
                  4. <\/b> Stop all monitoring of the affected asset<\/span><\/li>\n<\/ol>\n

                    Correct Answer: 2. Remove the attacker\u2019s artifacts and address the cause or mechanisms that enabled continued compromise<\/b><\/p>\n

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

                    Containment limits immediate damage, while eradication removes the elements that allowed the compromise to persist. This may include removing malware, unauthorized accounts, malicious scheduled tasks, persistence mechanisms, or other artifacts and addressing vulnerabilities that enabled the attack. Recovery should occur only after responders have reasonable confidence that the threat has been removed. Fortinet\u2019s current Security Operations Architect training includes eradicating artifacts from compromised hosts as part of its incident-handling and SOAR response workflow.<\/span><\/p>\n

                    Q150. Why should recovery include increased monitoring of a previously compromised host?<\/b><\/p>\n

                      \n
                    1. <\/b> To ensure the system can never fail again<\/span><\/li>\n
                    2. <\/b> To reduce available logs<\/span><\/li>\n
                    3. <\/b> To avoid validating remediation<\/span><\/li>\n
                    4. <\/b> To detect signs that the threat remains, returns, or that remediation was incomplete<\/span><\/li>\n<\/ol>\n

                      Correct Answer: 4. To detect signs that the threat remains, returns, or that remediation was incomplete<\/b><\/p>\n

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

                      Returning a system to service does not automatically prove that every malicious artifact or access path has been removed. Increased monitoring during recovery helps confirm that the host behaves normally and that suspicious connections, processes, accounts, or persistence mechanisms do not reappear. This is particularly important after significant compromises. Recovery should also verify business functionality and may include removing the host from quarantine only after defined criteria are met. Fortinet\u2019s course explicitly includes releasing compromised hosts from quarantine after recovery.<\/span><\/p>\n

                      Q151. What is the BEST description of reactive threat hunting?<\/b><\/p>\n

                        \n
                      1. <\/b> Hunting that begins from a known alert, incident, indicator, or observed suspicious behavior<\/span><\/li>\n
                      2. <\/b> Hunting performed only when no incident exists<\/span><\/li>\n
                      3. <\/b> A process that never uses SIEM queries<\/span><\/li>\n
                      4. <\/b> An automated containment action<\/span><\/li>\n<\/ol>\n

                        Correct Answer: 1. Hunting that begins from a known alert, incident, indicator, or observed suspicious behavior<\/b><\/p>\n

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

                        Reactive hunting starts with a lead that already exists, such as an incident, malicious indicator, user report, or suspicious behavior. The hunter then searches for related activity, additional affected systems, earlier attack stages, or evidence that the known problem is broader than initially understood. Proactive hunting instead begins from a hypothesis or threat model without requiring an existing alert. Fortinet\u2019s current Security Operations Architect course explicitly covers both reactive and proactive threat-hunting processes and the generation of hunting hypotheses.<\/span><\/p>\n

                        Q152. Which scenario BEST represents proactive threat hunting?<\/b><\/p>\n

                          \n
                        1. <\/b> An analyst investigates an incident after malware is detected<\/span><\/li>\n
                        2. <\/b> A playbook blocks a confirmed malicious IP<\/span><\/li>\n
                        3. <\/b> A hunter tests a hypothesis about credential misuse even though no specific alert has triggered<\/span><\/li>\n
                        4. <\/b> A queue routes an existing incident to Tier 2<\/span><\/li>\n<\/ol>\n

                          Correct Answer: 3. A hunter tests a hypothesis about credential misuse even though no specific alert has triggered<\/b><\/p>\n

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

                          Proactive threat hunting searches for attacker behavior before an existing alert necessarily identifies it. The hunter might hypothesize that stolen credentials are being used in unusual ways and then examine authentication, endpoint, and network telemetry for evidence. If suspicious behavior is discovered, the hunt can generate incidents or inspire new detection rules. Investigating an existing alert is reactive, while playbook containment and queue routing are response and workload functions. Fortinet explicitly includes proactive and reactive hunting within its Security Operations Architect training.<\/span><\/p>\n

                          Q153. Why is it useful to convert a successful threat-hunting finding into a new FortiSIEM detection rule when appropriate?<\/b><\/p>\n

                            \n
                          1. <\/b> It can transform a manually discovered pattern into repeatable continuous detection<\/span><\/li>\n
                          2. <\/b> It guarantees no false positives will occur<\/span><\/li>\n
                          3. <\/b> It removes the need for future threat hunting<\/span><\/li>\n
                          4. <\/b> It prevents FortiSOAR from receiving incidents<\/span><\/li>\n<\/ol>\n

                            Correct Answer: 4. It can transform a manually discovered pattern into repeatable continuous detection<\/b><\/p>\n

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

                            Threat hunts can uncover behavior that existing detections missed. If the behavior can be expressed reliably using available telemetry, creating or improving a FortiSIEM rule allows the SOC to monitor for the pattern continuously rather than rediscovering it manually each time. The detection should still be validated and tuned because a hunting observation does not guarantee a production rule will be noise-free. Threat hunting and automated detection complement each other: hunting discovers new possibilities, while rules provide repeatable monitoring at scale.<\/span><\/p>\n

                            Q154. When FortiSIEM incidents are ingested into FortiSOAR, what is a key operational benefit?<\/b><\/p>\n

                              \n
                            1. <\/b> FortiSIEM no longer needs to collect events<\/span><\/li>\n
                            2. <\/b> FortiSOAR can manage, enrich, assign, collaborate on, and automate response to the detected incident<\/span><\/li>\n
                            3. <\/b> Every FortiSIEM incident becomes malicious automatically<\/span><\/li>\n
                            4. <\/b> Incident evidence is deleted from FortiSIEM<\/span><\/li>\n<\/ol>\n

                              Correct Answer: 2. FortiSOAR can manage, enrich, assign, collaborate on, and automate response to the detected incident<\/b><\/p>\n

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

                              FortiSIEM and FortiSOAR perform complementary functions. FortiSIEM provides detection and analytical context from correlated event data, while FortiSOAR can orchestrate downstream incident handling. Once a relevant incident enters FortiSOAR, workflows can enrich indicators, assign ownership, create tasks, support collaboration, trigger approvals, and perform approved containment actions through connectors. The integration does not imply every incident is confirmed malicious and does not eliminate FortiSIEM\u2019s event-analysis role. Fortinet\u2019s current course explicitly includes ingesting FortiSIEM incidents into FortiSOAR for handling.<\/span><\/p>\n

                              Q155. What does escalating a FortiSOAR alert into an incident accomplish?<\/b><\/p>\n

                                \n
                              1. <\/b> It promotes activity that requires formal case handling and investigation into an incident workflow<\/span><\/li>\n
                              2. <\/b> It deletes the original evidence<\/span><\/li>\n
                              3. <\/b> It automatically closes all related alerts<\/span><\/li>\n
                              4. <\/b> It disables playbook execution<\/span><\/li>\n<\/ol>\n

                                Correct Answer: 1. It promotes activity that requires formal case handling and investigation into an incident workflow<\/b><\/p>\n

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

                                Not every alert needs the same level of case management. When an alert has sufficient significance, confidence, or context, escalating it to an incident allows the SOC to apply formal ownership, tasks, investigation, collaboration, severity, and response processes. The escalation does not mean the activity is unquestionably malicious; further analysis may still be required. Fortinet\u2019s current Security Operations Architect course explicitly includes escalating FortiSOAR alerts into incidents as part of the incident-handling workflow.<\/span><\/p>\n

                                Q156. Why should automation requirements be defined before building a FortiSOAR playbook?<\/b><\/p>\n

                                  \n
                                1. <\/b> To identify triggers, required data, decisions, integrations, approvals, actions, and expected outcomes before implementation<\/span><\/li>\n
                                2. <\/b> To ensure every step is fully automated<\/span><\/li>\n
                                3. <\/b> To eliminate the need for testing<\/span><\/li>\n
                                4. <\/b> To avoid documenting the workflow<\/span><\/li>\n<\/ol>\n

                                  Correct Answer: 3. To identify triggers, required data, decisions, integrations, approvals, actions, and expected outcomes before implementation<\/b><\/p>\n

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

                                  Automation works best when the desired process is understood before technical implementation begins. Requirements should define what starts the workflow, which information is required, what decisions must be made, which connectors are needed, where human approval is appropriate, and what should happen on success or failure. Without this design work, playbooks can automate an unclear or unsafe process. Fortinet\u2019s Security Operations Architect course explicitly includes describing automation requirements and playbook steps before implementing response workflows.<\/span><\/p>\n

                                  Q157. A playbook queries FortiSandbox for a file-hash rating. What is the main purpose of this step?<\/b><\/p>\n

                                    \n
                                  1. <\/b> To replace the file on the endpoint<\/span><\/li>\n
                                  2. <\/b> To obtain additional security context about the file that can inform later playbook decisions<\/span><\/li>\n
                                  3. <\/b> To assign a SOC shift<\/span><\/li>\n
                                  4. <\/b> To create a FortiSIEM parser<\/span><\/li>\n<\/ol>\n

                                    Correct Answer: 2. To obtain additional security context about the file that can inform later playbook decisions<\/b><\/p>\n

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

                                    A hash-rating lookup is an enrichment action. The playbook provides the file hash to FortiSandbox and retrieves available reputation or analysis context. That information can then influence later steps, such as escalating the incident, requesting analyst approval, isolating a host, or continuing investigation. A rating should be interpreted in context rather than treated as unquestionable proof. Fortinet\u2019s current Security Operations Architect training specifically includes configuring a playbook to retrieve a hash rating from FortiSandbox.<\/span><\/p>\n

                                    Q158. A FortiSOAR playbook must disable a compromised user account in Windows Active Directory. What component enables this action?<\/b><\/p>\n

                                      \n
                                    1. <\/b> A FortiSIEM event query only<\/span><\/li>\n
                                    2. <\/b> A war-room note<\/span><\/li>\n
                                    3. <\/b> A queue<\/span><\/li>\n
                                    4. <\/b> An appropriately configured FortiSOAR connector with permission to perform the directory action<\/span><\/li>\n<\/ol>\n

                                      Correct Answer: 4. An appropriately configured FortiSOAR connector with permission to perform the directory action<\/b><\/p>\n

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

                                      FortiSOAR uses connectors to interact with external products and services. To disable a user account in Windows Active Directory, the relevant connector must be configured with network reachability, suitable credentials, and sufficient permissions for the requested operation. The action can then be included in a playbook, potentially behind conditional logic or manual approval because account disabling can be disruptive. Fortinet\u2019s current course specifically includes containment on Windows Active Directory using FortiSOAR connectors.<\/span><\/p>\n

                                      Q159. Why might a FortiSOAR playbook use FortiClient EMS during endpoint containment?<\/b><\/p>\n

                                        \n
                                      1. <\/b> To perform an approved endpoint-control action such as quarantine or isolation through the integration<\/span><\/li>\n
                                      2. <\/b> To create a FortiSIEM log parser<\/span><\/li>\n
                                      3. <\/b> To schedule analyst shifts<\/span><\/li>\n
                                      4. <\/b> To replace threat hunting<\/span><\/li>\n<\/ol>\n

                                        Correct Answer: 1. To perform an approved endpoint-control action such as quarantine or isolation through the integration<\/b><\/p>\n

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

                                        FortiClient EMS can participate in endpoint containment workflows when FortiSOAR uses the appropriate connector and credentials. A playbook can orchestrate endpoint-related response actions after detection and validation, reducing the time needed for manual intervention. High-impact actions should still include suitable safeguards, such as confidence checks, asset context, approvals, and recovery procedures. Fortinet\u2019s current Security Operations Architect training explicitly includes performing containment using FortiClient EMS and other Fortinet products through FortiSOAR connectors.<\/span><\/p>\n

                                        Q160. What is the MAIN reason to retain FortiSOAR playbook history logs after an incident is resolved?<\/b><\/p>\n

                                          \n
                                        1. <\/b> To make future connector errors impossible<\/span><\/li>\n
                                        2. <\/b> To replace incident documentation<\/span><\/li>\n
                                        3. <\/b> To support audit, troubleshooting, validation of automated actions, and post-incident review<\/span><\/li>\n
                                        4. <\/b> To stop future playbook executions<\/span><\/li>\n<\/ol>\n

                                          Correct Answer: 3. To support audit, troubleshooting, validation of automated actions, and post-incident review<\/b><\/p>\n

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

                                          Playbook history provides a record of how automation actually executed. It can show which steps ran, which branches were followed, what actions succeeded or failed, and when those actions occurred. This is valuable for auditing high-impact containment, troubleshooting unexpected behavior, and reviewing incident-response effectiveness after closure. History complements incident documentation rather than replacing it. Fortinet\u2019s current Security Operations Architect course explicitly includes managing playbook history logs as part of playbook development and operations.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

                                          View Full Fortinet NSE7_SOC_AR-7.6 Exam Dumps and Practice Test Dumps. Q141. What is the primary value of using the MITRE ATT&CK framework during a SOC investigation? It automatically attributes an attack to a specific threat actor It replaces the need for event collection It assigns incident owners in FortiSOAR It provides a structured way to […]<\/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\/20302"}],"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=20302"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/20302\/revisions"}],"predecessor-version":[{"id":20303,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/20302\/revisions\/20303"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=20302"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=20302"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=20302"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}