{"id":20296,"date":"2026-09-23T12:26:50","date_gmt":"2026-09-23T12:26:50","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=20296"},"modified":"2026-09-23T12:26:50","modified_gmt":"2026-09-23T12:26:50","slug":"fortinet-nse7_soc_ar-7-6-practice-test-questions-and-exam-dumps-part5-q81-100","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/fortinet-nse7_soc_ar-7-6-practice-test-questions-and-exam-dumps-part5-q81-100\/","title":{"rendered":"Fortinet NSE7_SOC_AR-7.6 Practice Test Questions and Exam Dumps Part5 Q81-100"},"content":{"rendered":"

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


\n<\/b>Q81. During incident triage, why is determining whether an affected account has privileged access important?<\/b><\/p>\n

    \n
  1. <\/b> Privileged accounts cannot be compromised<\/span><\/li>\n
  2. <\/b> Privileged users generate fewer security events<\/span><\/li>\n
  3. <\/b> Compromise of a privileged account can provide an attacker with broader access and increase potential impact<\/span><\/li>\n
  4. <\/b> Privilege level determines FortiSIEM storage capacity<\/span><\/li>\n<\/ol>\n

    Correct Answer: 3. Compromise of a privileged account can provide an attacker with broader access and increase potential impact<\/b><\/p>\n

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

    Account privilege is an important element of incident context. If a compromised identity has administrative or elevated permissions, an attacker may be able to access additional systems, disable security controls, modify accounts, or perform actions that ordinary users cannot. This can increase both incident severity and containment urgency. Privileged accounts are not immune to compromise and may generate the same kinds of authentication and activity events as other identities. SOC analysts should combine privilege level with asset criticality, observed behavior, attack scope, and threat confidence when prioritizing investigation and response.<\/span><\/p>\n

    Q82. What is the primary purpose of containment during incident response?<\/b><\/p>\n

      \n
    1. <\/b> To limit the attacker\u2019s ability to continue causing damage or spreading while investigation and remediation proceed<\/span><\/li>\n
    2. <\/b> To erase all forensic evidence immediately<\/span><\/li>\n
    3. <\/b> To close the incident before determining scope<\/span><\/li>\n
    4. <\/b> To disable all security monitoring<\/span><\/li>\n<\/ol>\n

      Correct Answer: 1. To limit the attacker\u2019s ability to continue causing damage or spreading while investigation and remediation proceed<\/b><\/p>\n

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

      Containment attempts to reduce ongoing risk while responders continue investigation and prepare remediation. Actions can include isolating an endpoint, disabling a compromised account, blocking malicious infrastructure, or restricting access to affected services. The exact action should be proportionate to the confidence and impact of the incident. Containment should not unnecessarily destroy evidence or end the investigation. FortiSOAR can help orchestrate containment through connectors, but architects should consider approvals, asset criticality, reversibility, and the risk of disrupting legitimate business operations before automating high-impact actions.<\/span><\/p>\n

      Q83. A SOC analyst observes a user account performing directory reconnaissance immediately after an unusual login. What is the BEST next step?<\/b><\/p>\n

        \n
      1. <\/b> Assume directory queries are always legitimate<\/span><\/li>\n
      2. <\/b> Delete the account immediately without investigation<\/span><\/li>\n
      3. <\/b> Ignore the behavior because no malware was detected<\/span><\/li>\n
      4. <\/b> Correlate the login with subsequent user, host, process, and network activity to determine whether it reflects adversary discovery behavior<\/span><\/li>\n<\/ol>\n

        Correct Answer: 4. Correlate the login with subsequent user, host, process, and network activity to determine whether it reflects adversary discovery behavior<\/b><\/p>\n

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

        Directory queries can be legitimate administrative activity or part of adversary discovery after credential compromise. The correct approach is to establish context. Analysts should determine where the login originated, whether the device is expected, which process performed the queries, what objects were searched, and whether the account then accessed additional systems. Looking at a sequence of behaviors provides much stronger evidence than treating one event in isolation. Fortinet\u2019s SOC Concepts and Frameworks domain specifically expects candidates to analyze incidents and identify adversary behavior.<\/span><\/p>\n

        Q84. Why should a SOC distinguish between an indicator of compromise and the broader behavior surrounding it?<\/b><\/p>\n

          \n
        1. <\/b> Indicators are always false positives<\/span><\/li>\n
        2. <\/b> A single indicator may change or be reused, while behavior can reveal a larger attack pattern and additional affected systems<\/span><\/li>\n
        3. <\/b> Behavioral analysis eliminates the need for indicators<\/span><\/li>\n
        4. <\/b> Indicators apply only to FortiSOAR<\/span><\/li>\n<\/ol>\n

          Correct Answer: 2. A single indicator may change or be reused, while behavior can reveal a larger attack pattern and additional affected systems<\/b><\/p>\n

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

          Indicators such as hashes, domains, and IP addresses are useful, but they can be short-lived, shared, or replaced rapidly by attackers. Behavioral context can reveal what the adversary is trying to accomplish and connect related events even when individual indicators change. For example, suspicious credential use followed by host discovery and remote access can remain meaningful even if the attacker rotates infrastructure. Analysts should use both indicators and behavioral evidence rather than treating them as competing approaches. This improves detection, scoping, hunting, and future rule development.<\/span><\/p>\n

          Q85. What is the BEST reason to include asset criticality in a FortiSIEM incident rule or triage process?<\/b><\/p>\n

            \n
          1. <\/b> It can help prioritize incidents involving systems whose compromise would have greater business impact<\/span><\/li>\n
          2. <\/b> Criticality determines whether an event can be parsed<\/span><\/li>\n
          3. <\/b> Asset criticality changes log timestamps<\/span><\/li>\n
          4. <\/b> High-value systems cannot produce false positives<\/span><\/li>\n<\/ol>\n

            Correct Answer: 1. It can help prioritize incidents involving systems whose compromise would have greater business impact<\/b><\/p>\n

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

            Not every event has the same business significance. Suspicious activity involving a domain controller, payment application, production database, or executive workstation may require more urgent investigation than similar behavior on a low-risk lab system. Asset criticality helps add business context to technical detections and supports more rational prioritization. It does not prove that an incident is malicious, and high-value assets can still generate benign events. Mature SOC processes combine detection confidence, asset importance, incident scope, and adversary behavior when determining severity and response priority.<\/span><\/p>\n

            Q86. A FortiSIEM rule should detect repeated account lockouts affecting multiple users from one source. Which correlation approach is MOST appropriate?<\/b><\/p>\n

              \n
            1. <\/b> Group only by destination application name<\/span><\/li>\n
            2. <\/b> Trigger on every successful login<\/span><\/li>\n
            3. <\/b> Group lockout events by source, count affected users, and apply an appropriate time window<\/span><\/li>\n
            4. <\/b> Remove all user information from the rule<\/span><\/li>\n<\/ol>\n

              Correct Answer: 3. Group lockout events by source, count affected users, and apply an appropriate time window<\/b><\/p>\n

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

              The suspicious pattern depends on one source causing lockouts across multiple accounts. The rule should therefore correlate events using the source as a key, count distinct affected users, and evaluate the behavior within a meaningful time window. This can help identify password-spraying or similar activity while reducing noise from isolated user mistakes. A rule that ignores source and user relationships would lose the behavioral pattern. Fortinet explicitly includes configuring FortiSIEM incident rules among the current exam objectives.<\/span><\/p>\n

              Q87. What is the benefit of using a distinct count in a FortiSIEM correlation use case?<\/b><\/p>\n

                \n
              1. <\/b> It deletes duplicate events permanently<\/span><\/li>\n
              2. <\/b> It can measure how many unique values, such as users or hosts, are involved rather than counting every event equally<\/span><\/li>\n
              3. <\/b> It prevents events from being normalized<\/span><\/li>\n
              4. <\/b> It replaces correlation time windows<\/span><\/li>\n<\/ol>\n

                Correct Answer: 2. It can measure how many unique values, such as users or hosts, are involved rather than counting every event equally<\/b><\/p>\n

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

                A normal event count tells analysts how many events occurred, but a distinct count can answer questions such as how many different accounts, hosts, or destinations were involved. This is useful for detecting patterns such as one source targeting many users or one account accessing many systems. Distinct counting adds behavioral meaning that raw event volume may not provide. It does not delete events and does not replace the need for appropriate grouping or time windows. Correlation logic should be designed around the security behavior the SOC actually wants to detect.<\/span><\/p>\n

                Q88. A FortiSIEM search returns too many events because the analyst used OR between several broad conditions. What should the analyst consider?<\/b><\/p>\n

                  \n
                1. <\/b> Disable event collection<\/span><\/li>\n
                2. <\/b> Remove all time filtering<\/span><\/li>\n
                3. <\/b> Delete the incident rule<\/span><\/li>\n
                4. <\/b> Refine the Boolean logic and use more specific filters to reduce irrelevant matches<\/span><\/li>\n<\/ol>\n

                  Correct Answer: 4. Refine the Boolean logic and use more specific filters to reduce irrelevant matches<\/b><\/p>\n

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

                  OR broadens a query because an event can match any of the listed conditions. When several broad criteria are joined with OR, the result set can become very large and contain many unrelated events. The analyst should revisit the investigation goal and combine appropriate AND conditions, entity filters, event types, and time ranges to improve precision. The query should remain broad enough to preserve relevant evidence but focused enough to be operationally useful. Fortinet explicitly tests the ability to build FortiSIEM event-log queries.<\/span><\/p>\n

                  Q89. Why is it important to validate timestamps when building an incident timeline from multiple log sources?<\/b><\/p>\n

                    \n
                  1. <\/b> Different systems may have clock or timezone differences that can make event sequence appear incorrect<\/span><\/li>\n
                  2. <\/b> Timestamps are used only for storage billing<\/span><\/li>\n
                  3. <\/b> All security products always use identical time settings<\/span><\/li>\n
                  4. <\/b> Correct timestamps eliminate the need for correlation<\/span><\/li>\n<\/ol>\n

                    Correct Answer: 3. Different systems may have clock or timezone differences that can make event sequence appear incorrect<\/b><\/p>\n

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

                    Incident timelines depend on accurate sequencing. If systems use different time zones or have clock drift, events can appear to occur in the wrong order, potentially misleading analysts about initial access, execution, lateral movement, or response activity. Analysts should understand how timestamps are normalized and verify suspicious discrepancies when correlating data from multiple products. Accurate timing supports correlation rules, threat hunting, and incident reconstruction. It does not eliminate the need for other context, but poor time synchronization can significantly reduce the reliability of an investigation.<\/span><\/p>\n

                    Q90. A suspicious event appears only once and involves a noncritical test host. What should determine whether the SOC escalates it?<\/b><\/p>\n

                      \n
                    1. <\/b> A balanced assessment of evidence, behavior, threat context, asset value, and potential impact<\/span><\/li>\n
                    2. <\/b> The fact that every alert must automatically become critical<\/span><\/li>\n
                    3. <\/b> Whether the host has the longest hostname<\/span><\/li>\n
                    4. <\/b> Whether the event occurred during the day<\/span><\/li>\n<\/ol>\n

                      Correct Answer: 1. A balanced assessment of evidence, behavior, threat context, asset value, and potential impact<\/b><\/p>\n

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

                      Escalation should be evidence-driven. A single event on a low-value test system may still be important if it represents a high-confidence exploit or a broader campaign, while a noisy low-confidence alert may not justify immediate escalation. Analysts should consider the detection source, adversary behavior, asset importance, scope, threat intelligence, and possible business consequences. No single contextual factor should be treated as absolute proof. Consistent triage criteria help a SOC focus limited analyst resources on incidents that are most likely to create meaningful risk.<\/span><\/p>\n

                      Q91. What is the primary purpose of creating a queue dedicated to high-severity FortiSOAR incidents?<\/b><\/p>\n

                        \n
                      1. <\/b> To delete low-severity incidents automatically<\/span><\/li>\n
                      2. <\/b> To organize urgent work so appropriate analysts can identify and handle it quickly<\/span><\/li>\n
                      3. <\/b> To increase FortiSIEM event ingestion<\/span><\/li>\n
                      4. <\/b> To change connector credentials<\/span><\/li>\n<\/ol>\n

                        Correct Answer: 4. To organize urgent work so appropriate analysts can identify and handle it quickly<\/b><\/p>\n

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

                        Queues provide operational organization for records requiring attention. A dedicated high-severity queue can make urgent incidents visible to the appropriate team and support prioritization, ownership, escalation, and shift-based workload handling. The queue does not have to delete or ignore lower-severity incidents; those records can follow their own processes. Queues are part of FortiSOAR workload management rather than SIEM ingestion or connector authentication. Fortinet\u2019s current exam specifically includes creating queues and shifts for workload management.<\/span><\/p>\n

                        Q92. Why are shifts useful in a 24×7 SOC using FortiSOAR?<\/b><\/p>\n

                          \n
                        1. <\/b> They determine threat-intelligence reputation scores<\/span><\/li>\n
                        2. <\/b> They ensure every analyst works continuously<\/span><\/li>\n
                        3. <\/b> They help route workload according to which personnel or teams are currently available<\/span><\/li>\n
                        4. <\/b> They replace incident ownership<\/span><\/li>\n<\/ol>\n

                          Correct Answer: 2. They help route workload according to which personnel or teams are currently available<\/b><\/p>\n

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

                          Continuous SOC operations require work to move between teams as people begin and end scheduled duty periods. Shift information can help workload processes route incidents to personnel who are actually available and support smooth handoffs between teams. Shifts complement ownership, queues, and escalation procedures rather than replacing them. They also do not influence threat-intelligence scores. Fortinet specifically includes queues and shifts as a required skill within SOAR Incident Handling and Threat Hunting.<\/span><\/p>\n

                          Q93. What is a key benefit of using a war room for a complex FortiSOAR incident?<\/b><\/p>\n

                            \n
                          1. <\/b> It centralizes collaboration and preserves investigation context for everyone working on the case<\/span><\/li>\n
                          2. <\/b> It automatically eradicates malware<\/span><\/li>\n
                          3. <\/b> It replaces all connectors<\/span><\/li>\n
                          4. <\/b> It prevents the incident from being escalated<\/span><\/li>\n<\/ol>\n

                            Correct Answer: 1. It centralizes collaboration and preserves investigation context for everyone working on the case<\/b><\/p>\n

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

                            Complex incidents may involve malware analysts, identity teams, network responders, and management. A war room provides a shared workspace where investigation details, findings, decisions, and response activities can remain associated with the case. This reduces fragmented communication and supports continuity when analysts hand work between shifts. A war room does not automatically perform containment or eradicate malware, and it does not replace integrations. Fortinet explicitly identifies use of war rooms for incident handling as a current exam objective.<\/span><\/p>\n

                            Q94. A FortiSOAR playbook should enrich a file hash only when the hash field is populated. What is the BEST design?<\/b><\/p>\n

                              \n
                            1. <\/b> Call the connector unconditionally<\/span><\/li>\n
                            2. <\/b> Use conditional logic to verify that the hash value exists before performing enrichment<\/span><\/li>\n
                            3. <\/b> Delete incidents with empty hashes<\/span><\/li>\n
                            4. <\/b> Disable connector authentication<\/span><\/li>\n<\/ol>\n

                              Correct Answer: 4. Use conditional logic to verify that the hash value exists before performing enrichment<\/b><\/p>\n

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

                              A connector action should receive valid required input. If a file-hash field is empty, sending the request anyway can produce unnecessary errors or invalid queries. Conditional logic can verify that the field contains an appropriate value before the playbook proceeds to enrichment. If the hash is absent, the workflow can skip the action or follow another branch. This makes automation more resilient and prevents avoidable connector failures. Fortinet\u2019s exam includes configuring playbooks, connectors, and troubleshooting workflow behavior, all of which require careful handling of inputs.<\/span><\/p>\n

                              Q95. Why should a FortiSOAR playbook normalize an indicator before sending it to an external reputation service?<\/b><\/p>\n

                                \n
                              1. <\/b> Normalization can ensure the value is in the format expected by the connector and reduce avoidable lookup failures<\/span><\/li>\n
                              2. <\/b> Normalization makes every indicator malicious<\/span><\/li>\n
                              3. <\/b> It prevents any future changes to the indicator<\/span><\/li>\n
                              4. <\/b> It eliminates the need for connectors<\/span><\/li>\n<\/ol>\n

                                Correct Answer: 2. Normalization can ensure the value is in the format expected by the connector and reduce avoidable lookup failures<\/b><\/p>\n

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

                                External services often require data in specific formats. A URL may need consistent casing or parsing, a hash may need whitespace removed, or an address may need to be extracted from a larger string. Jinja expressions and filters can normalize input before the connector call so the external service receives clean data. Normalization improves reliability but does not change whether an indicator is actually malicious. Fortinet explicitly includes Jinja-based data manipulation and connector configuration in the current playbook development domain.<\/span><\/p>\n

                                Q96. A connector test succeeds manually, but the same connector action fails inside a playbook. What should be investigated FIRST?<\/b><\/p>\n

                                  \n
                                1. <\/b> The runtime values and parameters passed from the playbook to the connector action<\/span><\/li>\n
                                2. <\/b> FortiSIEM database retention<\/span><\/li>\n
                                3. <\/b> Analyst shift schedules<\/span><\/li>\n
                                4. <\/b> Whether the war room contains comments<\/span><\/li>\n<\/ol>\n

                                  Correct Answer: 3. The runtime values and parameters passed from the playbook to the connector action<\/b><\/p>\n

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

                                  If the connector itself works during a manual test, the problem likely lies in how the playbook is calling it. The administrator should inspect the variables, field mappings, Jinja transformations, required parameters, and data types passed during execution. A missing identifier or malformed value can cause the connector action to fail even though credentials and network reachability are correct. Playbook history and step-level outputs are particularly useful for this analysis. Fortinet explicitly tests debugging and troubleshooting of FortiSOAR playbooks.<\/span><\/p>\n

                                  Q97. What is the advantage of breaking a complex response workflow into logical playbook stages?<\/b><\/p>\n

                                    \n
                                  1. <\/b> It can improve readability, testing, troubleshooting, and control over automation decisions<\/span><\/li>\n
                                  2. <\/b> It guarantees that no external API will fail<\/span><\/li>\n
                                  3. <\/b> It eliminates the need for incident records<\/span><\/li>\n
                                  4. <\/b> It prevents analysts from viewing workflow results<\/span><\/li>\n<\/ol>\n

                                    Correct Answer: 4. It can improve readability, testing, troubleshooting, and control over automation decisions<\/b><\/p>\n

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

                                    Complex automation is easier to maintain when divided into logical stages such as validation, enrichment, decision, containment, recovery, and notification. This allows developers to test components independently, understand dependencies, and isolate failures more quickly. Clear stages also make approval points and error handling easier to design. Modular workflow design does not guarantee external systems will always respond successfully, so connector and exception handling remain necessary. Well-structured playbooks are easier for future administrators to understand and modify safely.<\/span><\/p>\n

                                    Q98. A Jinja expression references a field that may not exist in every incident. What should the playbook designer consider?<\/b><\/p>\n

                                      \n
                                    1. <\/b> Always assume the field exists<\/span><\/li>\n
                                    2. <\/b> Include logic that safely handles missing or null values<\/span><\/li>\n
                                    3. <\/b> Delete records without that field<\/span><\/li>\n
                                    4. <\/b> Disable the connector using the expression<\/span><\/li>\n<\/ol>\n

                                      Correct Answer: 2. Include logic that safely handles missing or null values<\/b><\/p>\n

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

                                      Automation must account for incomplete or variable record data. If a Jinja expression assumes a field always exists, the playbook may fail when an incident lacks that value. Defensive workflow design checks for missing or null data and chooses an appropriate alternative path, default value, or skipped action. This makes the playbook more reliable across different incident types. Fortinet includes Jinja filters and playbook troubleshooting as exam objectives, so candidates should understand that data structure and availability directly affect execution behavior.<\/span><\/p>\n

                                      Q99. A playbook automatically blocks an IP address, but the block remains after the investigation proves the address was benign. What design improvement would help?<\/b><\/p>\n

                                        \n
                                      1. <\/b> Add a controlled recovery or rollback process for reversing containment when appropriate<\/span><\/li>\n
                                      2. <\/b> Permanently block every investigated IP<\/span><\/li>\n
                                      3. <\/b> Remove incident documentation<\/span><\/li>\n
                                      4. <\/b> Disable playbook history<\/span><\/li>\n<\/ol>\n

                                        Correct Answer: 1. Add a controlled recovery or rollback process for reversing containment when appropriate<\/b><\/p>\n

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

                                        Containment can be necessary during an incident, but response design should also consider how to restore legitimate access after the threat has been resolved or a decision changes. A controlled rollback can remove a block, release a host from quarantine, or restore an account while preserving an audit trail. Fortinet\u2019s Security Operations Architect course explicitly includes releasing compromised hosts from quarantine after recovery. Designing for restoration reduces the long-term business impact of false positives or temporary containment actions and makes automated response safer.<\/span><\/p>\n

                                        Q100. What is the BEST reason to review playbook history after a high-severity automated response completes?<\/b><\/p>\n

                                          \n
                                        1. <\/b> To verify which actions executed, review outcomes, and preserve an audit trail for troubleshooting and incident review<\/span><\/li>\n
                                        2. <\/b> To erase evidence of automation<\/span><\/li>\n
                                        3. <\/b> To disable future playbook runs<\/span><\/li>\n
                                        4. <\/b> To reduce FortiSIEM event volume<\/span><\/li>\n<\/ol>\n

                                          Correct Answer: 3. To verify which actions executed, review outcomes, and preserve an audit trail for troubleshooting and incident review<\/b><\/p>\n

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

                                          Playbook history provides visibility into what the automation actually did. After a significant response, analysts and administrators can review execution paths, connector actions, conditions, results, failures, and timing. This supports incident documentation, troubleshooting, governance, and post-incident analysis. It is especially important when automation performs disruptive actions such as blocking infrastructure or isolating hosts. Fortinet\u2019s current Security Operations Architect training explicitly includes managing playbook history logs. History should be preserved as operational evidence rather than deleted after successful execution.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

                                          View Full Fortinet NSE7_SOC_AR-7.6 Exam Dumps and Practice Test Dumps. Q81. During incident triage, why is determining whether an affected account has privileged access important? Privileged accounts cannot be compromised Privileged users generate fewer security events Compromise of a privileged account can provide an attacker with broader access and increase potential impact Privilege level determines […]<\/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\/20296"}],"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=20296"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/20296\/revisions"}],"predecessor-version":[{"id":20297,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/20296\/revisions\/20297"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=20296"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=20296"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=20296"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}