{"id":20310,"date":"2026-09-23T12:31:34","date_gmt":"2026-09-23T12:31:34","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=20310"},"modified":"2026-09-23T12:31:34","modified_gmt":"2026-09-23T12:31:34","slug":"fortinet-nse7_soc_ar-7-6-practice-test-questions-and-exam-dumps-part12-q221-240","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/fortinet-nse7_soc_ar-7-6-practice-test-questions-and-exam-dumps-part12-q221-240\/","title":{"rendered":"Fortinet NSE7_SOC_AR-7.6 Practice Test Questions and Exam Dumps Part12 Q221-240"},"content":{"rendered":"

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


\n<\/b>Q221. Why is event-source health monitoring important in a FortiSIEM deployment?<\/b><\/p>\n

    \n
  1. <\/b> It automatically corrects every parsing error<\/span><\/li>\n
  2. <\/b> It helps identify collection gaps that could reduce detection and investigation visibility<\/span><\/li>\n
  3. <\/b> It changes FortiSOAR incident severity<\/span><\/li>\n
  4. <\/b> It eliminates the need for correlation rules<\/span><\/li>\n<\/ol>\n

    Correct Answer: 2. It helps identify collection gaps that could reduce detection and investigation visibility<\/b><\/p>\n

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

    A SIEM depends on continuous, reliable telemetry. If a firewall, identity system, endpoint platform, or other critical source stops sending events, detection rules may miss malicious behavior and investigators may have incomplete timelines. Monitoring source health allows administrators to identify missing or delayed data before the gap becomes a larger security problem. Restoring collection may involve checking device configuration, network connectivity, collectors, parsers, or ingestion services. Source-health monitoring does not replace correlation rules or automatically repair every issue; its purpose is to reveal whether expected security evidence is actually available.<\/span><\/p>\n

    Q222. What is the BEST reason to assign standardized categories to security incidents across a SOC?<\/b><\/p>\n

      \n
    1. <\/b> Categories guarantee identical response times<\/span><\/li>\n
    2. <\/b> Categories eliminate the need for severity<\/span><\/li>\n
    3. <\/b> Categories prevent false positives<\/span><\/li>\n
    4. <\/b> Consistent categories improve routing, reporting, metrics, and selection of appropriate response procedures<\/span><\/li>\n<\/ol>\n

      Correct Answer: 4. Consistent categories improve routing, reporting, metrics, and selection of appropriate response procedures<\/b><\/p>\n

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

      Consistent categorization helps a SOC organize incidents such as phishing, malware, unauthorized access, credential compromise, or data loss using a shared vocabulary. Categories can support queue assignment, reporting, trend analysis, playbook selection, and escalation procedures. They do not replace severity because two incidents in the same category can have very different business impact. Categories also do not guarantee that detections are accurate. The goal is operational consistency so analysts, managers, and automation can interpret cases similarly and apply appropriate handling processes.<\/span><\/p>\n

      Q223. A SOC notices an increase in phishing incidents that all use different sender addresses but the same behavior. What is the BEST detection-improvement strategy?<\/b><\/p>\n

        \n
      1. <\/b> Focus on shared behavioral characteristics rather than relying only on individual sender indicators<\/span><\/li>\n
      2. <\/b> Block only the first sender address<\/span><\/li>\n
      3. <\/b> Stop collecting email-security events<\/span><\/li>\n
      4. <\/b> Treat every email from an unknown sender as malicious<\/span><\/li>\n<\/ol>\n

        Correct Answer: 1. Focus on shared behavioral characteristics rather than relying only on individual sender indicators<\/b><\/p>\n

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

        Attackers can easily rotate sender addresses, domains, URLs, and other indicators. Behavioral characteristics\u2014such as attachment execution patterns, credential-harvesting workflows, suspicious redirects, or common post-delivery activity\u2014can provide more durable detection opportunities. Indicators remain useful, but a rule based only on one sender can become obsolete quickly. Analysts should identify what the incidents have in common and determine whether those characteristics can be represented using available telemetry. This approach improves resilience against simple attacker infrastructure changes while avoiding an overly broad rule that flags all unfamiliar senders.<\/span><\/p>\n

        Q224. What is the primary benefit of correlating identity information with endpoint and network events?<\/b><\/p>\n

          \n
        1. <\/b> It automatically blocks the user<\/span><\/li>\n
        2. <\/b> It proves the endpoint is compromised<\/span><\/li>\n
        3. <\/b> It helps connect actions to a specific account and establish whether behavior is expected or suspicious<\/span><\/li>\n
        4. <\/b> It eliminates the need for timestamps<\/span><\/li>\n<\/ol>\n

          Correct Answer: 3. It helps connect actions to a specific account and establish whether behavior is expected or suspicious<\/b><\/p>\n

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

          Identity context can make technical events far more meaningful. A remote connection may be normal for an administrator but suspicious for an account that normally performs only local office tasks. By correlating users with endpoints, source addresses, applications, privileges, and network destinations, analysts can better distinguish legitimate activity from account compromise or misuse. Identity correlation does not automatically prove compromise and should be combined with timing, asset importance, and behavioral evidence. Accurate timestamps remain essential for reconstructing the sequence of user actions.<\/span><\/p>\n

          Q225. What is the BEST reason to define clear escalation criteria for FortiSIEM incidents?<\/b><\/p>\n

            \n
          1. <\/b> To ensure incidents meeting specific risk or complexity conditions are transferred to the appropriate response level<\/span><\/li>\n
          2. <\/b> To ensure every incident becomes Critical<\/span><\/li>\n
          3. <\/b> To prevent analysts from closing benign incidents<\/span><\/li>\n
          4. <\/b> To disable FortiSOAR automation<\/span><\/li>\n<\/ol>\n

            Correct Answer: 1. To ensure incidents meeting specific risk or complexity conditions are transferred to the appropriate response level<\/b><\/p>\n

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

            Escalation criteria help analysts decide when a case requires senior expertise, another technical team, management attention, or a specialized response process. Criteria may include asset criticality, confirmed compromise, privileged-account involvement, incident scope, regulatory concerns, or containment requirements. Without clear standards, similar incidents may be handled inconsistently. Escalation does not mean every case becomes critical; it means work is transferred when the situation exceeds the responsibility or capability of the current handling level. Consistent criteria support both human workflows and SOAR automation.<\/span><\/p>\n

            Q226. A FortiSIEM rule detects 100 failed logins from one application service account every night during a scheduled job. What is the BEST tuning approach?<\/b><\/p>\n

              \n
            1. <\/b> Disable all authentication monitoring<\/span><\/li>\n
            2. <\/b> Delete the service account<\/span><\/li>\n
            3. <\/b> Mark all failed-login incidents as benign permanently<\/span><\/li>\n
            4. <\/b> Create a narrowly scoped exception for the verified scheduled behavior while preserving detection outside that context<\/span><\/li>\n<\/ol>\n

              Correct Answer: 4. Create a narrowly scoped exception for the verified scheduled behavior while preserving detection outside that context<\/b><\/p>\n

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

              A known service process may legitimately generate repeated authentication failures because of a configuration issue or expected workflow. Once the SOC verifies the behavior, the rule can be tuned using specific account, source, application, schedule, or other reliable context. The exception should be as narrow as practical so similar failures from other sources remain detectable. Broadly disabling authentication monitoring would create a serious blind spot. Rule tuning should reduce predictable noise while retaining the original security intent of the detection.<\/span><\/p>\n

              Q227. Which query refinement would BEST help an analyst investigate suspicious activity involving only privileged accounts?<\/b><\/p>\n

                \n
              1. <\/b> Remove the time range<\/span><\/li>\n
              2. <\/b> Add identity or group criteria that restrict results to privileged users<\/span><\/li>\n
              3. <\/b> Search only low-severity events<\/span><\/li>\n
              4. <\/b> Exclude all authentication events<\/span><\/li>\n<\/ol>\n

                Correct Answer: 2. Add identity or group criteria that restrict results to privileged users<\/b><\/p>\n

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

                If the investigation specifically concerns privileged identities, query criteria should reflect that scope. Filtering by account group, role, naming convention, or another reliable privileged-user attribute can dramatically reduce unrelated events while preserving relevant evidence. The analyst can combine this with time, source, destination, event type, and asset filters. Removing useful time constraints or excluding authentication activity could hide important evidence. FortiSIEM queries are most effective when each filter directly supports the investigative question being asked.<\/span><\/p>\n

                Q228. Why should a SOC compare incident trends over time instead of reviewing only individual cases?<\/b><\/p>\n

                  \n
                1. <\/b> Trend analysis automatically identifies the attacker<\/span><\/li>\n
                2. <\/b> It eliminates the need for incident details<\/span><\/li>\n
                3. <\/b> Trends can reveal recurring attack patterns, noisy detections, and areas where controls or processes need improvement<\/span><\/li>\n
                4. <\/b> Historical incidents should always be reopened<\/span><\/li>\n<\/ol>\n

                  Correct Answer: 3. Trends can reveal recurring attack patterns, noisy detections, and areas where controls or processes need improvement<\/b><\/p>\n

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

                  Individual incidents explain specific events, but trend analysis can reveal broader operational patterns. An increasing number of credential attacks may indicate a changing threat, while repeated benign incidents from one application may show that a detection needs tuning. Trends can also reveal which business units, assets, or attack techniques generate the most workload. This information supports detection engineering, staffing, awareness, and architecture decisions. Trend analysis complements detailed case review; it does not replace the evidence required to understand any particular incident.<\/span><\/p>\n

                  Q229. What is a key benefit of preserving the original FortiSIEM incident context when the case is handled in FortiSOAR?<\/b><\/p>\n

                    \n
                  1. <\/b> It allows SOAR analysts and playbooks to use the detection evidence that led to the case<\/span><\/li>\n
                  2. <\/b> It removes the need to query FortiSIEM ever again<\/span><\/li>\n
                  3. <\/b> It guarantees automated containment is safe<\/span><\/li>\n
                  4. <\/b> It prevents any additional enrichment<\/span><\/li>\n<\/ol>\n

                    Correct Answer: 4. It allows SOAR analysts and playbooks to use the detection evidence that led to the case<\/b><\/p>\n

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

                    When FortiSIEM detections feed FortiSOAR, retaining the relevant source context helps analysts understand why the incident exists and gives playbooks useful fields for enrichment or decisions. Important information can include users, hosts, indicators, timestamps, rule details, severity, and related events. SOAR can then add further context rather than starting from an empty record. Preserving original evidence does not remove the need for deeper SIEM queries when the investigation expands, and it does not make automated response inherently safe.<\/span><\/p>\n

                    Q230. A threat hunter sees one unusual remote-service login but no other suspicious behavior. What is the BEST next action?<\/b><\/p>\n

                      \n
                    1. <\/b> Declare a confirmed compromise immediately<\/span><\/li>\n
                    2. <\/b> Pivot on the user, source, destination, and time to search for supporting or contradicting evidence<\/span><\/li>\n
                    3. <\/b> Delete the event<\/span><\/li>\n
                    4. <\/b> Disable the remote service organization-wide<\/span><\/li>\n<\/ol>\n

                      Correct Answer: 2. Pivot on the user, source, destination, and time to search for supporting or contradicting evidence<\/b><\/p>\n

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

                      One unusual event is a useful lead but rarely sufficient for a confident conclusion. The hunter should pivot to related authentication events, endpoint activity, network sessions, privilege use, and historical behavior around the same account and systems. Additional evidence may reveal lateral movement, credential abuse, or a legitimate administrative explanation. Threat hunting is hypothesis-driven and should actively search for evidence that both supports and challenges the initial suspicion. Immediate disruptive containment without context may affect legitimate operations unnecessarily.<\/span><\/p>\n

                      Q231. What is the PRIMARY reason to distinguish between a hypothesis and a confirmed finding during threat hunting?<\/b><\/p>\n

                        \n
                      1. <\/b> A hypothesis is a proposition being tested, while a finding is supported by collected evidence<\/span><\/li>\n
                      2. <\/b> A hypothesis is always malicious<\/span><\/li>\n
                      3. <\/b> Findings never require validation<\/span><\/li>\n
                      4. <\/b> Hypotheses cannot be changed<\/span><\/li>\n<\/ol>\n

                        Correct Answer: 1. A hypothesis is a proposition being tested, while a finding is supported by collected evidence<\/b><\/p>\n

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

                        A threat-hunting hypothesis gives the analyst a structured idea to test, such as whether stolen credentials are being used for remote access. It should not be treated as fact. A finding emerges only after available evidence supports a meaningful conclusion. Maintaining this distinction helps reduce confirmation bias and improves the quality of documented results. A hypothesis can be refined, rejected, or replaced as new evidence appears. Fortinet explicitly includes analyzing threat-hunting processes and data in the current exam scope.<\/span><\/p>\n

                        Q232. What is the BEST reason to record unsuccessful threat hunts?<\/b><\/p>\n

                          \n
                        1. <\/b> They should never be recorded<\/span><\/li>\n
                        2. <\/b> Only hunts that find malware are useful<\/span><\/li>\n
                        3. <\/b> Negative results can document what was tested, identify telemetry gaps, and prevent unnecessary duplication of work<\/span><\/li>\n
                        4. <\/b> Unsuccessful hunts automatically become incidents<\/span><\/li>\n<\/ol>\n

                          Correct Answer: 3. Negative results can document what was tested, identify telemetry gaps, and prevent unnecessary duplication of work<\/b><\/p>\n

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

                          A hunt that does not discover confirmed malicious activity can still provide value. It documents which hypothesis was tested, which data sources were reviewed, which queries were used, and whether visibility limitations prevented a strong conclusion. Other analysts can then avoid repeating identical work without new evidence and may refine the hunt later. Negative results can also identify missing telemetry or opportunities for improved detection. Threat hunting is a process of disciplined investigation, not a requirement to discover an attacker every time.<\/span><\/p>\n

                          Q233. A FortiSOAR queue contains incidents from several business units. What is the BEST reason to add routing criteria based on business ownership?<\/b><\/p>\n

                            \n
                          1. <\/b> To send cases to the analysts or teams responsible for the affected environment<\/span><\/li>\n
                          2. <\/b> To hide incidents from management<\/span><\/li>\n
                          3. <\/b> To prevent playbooks from running<\/span><\/li>\n
                          4. <\/b> To change FortiSIEM parsing<\/span><\/li>\n<\/ol>\n

                            Correct Answer: 2. To send cases to the analysts or teams responsible for the affected environment<\/b><\/p>\n

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

                            Large organizations often divide operational responsibility by business unit, region, technology, or customer. Routing criteria can direct an incident to the team that understands the affected systems and has authority to investigate or remediate them. This can reduce handoffs and shorten response time. Routing should still account for severity and specialized expertise when needed. FortiSOAR queues and shifts are specifically included in the Security Operations Architect objectives because workload organization is a central part of effective incident handling.<\/span><\/p>\n

                            Q234. Why is a war room especially useful when an incident involves both technical responders and business stakeholders?<\/b><\/p>\n

                              \n
                            1. <\/b> It automatically remediates every affected system<\/span><\/li>\n
                            2. <\/b> It replaces tasks and incident records<\/span><\/li>\n
                            3. <\/b> It centralizes communication and investigation context so participants can coordinate using shared information<\/span><\/li>\n
                            4. <\/b> It disables connectors during discussion<\/span><\/li>\n<\/ol>\n

                              Correct Answer: 1. It centralizes communication and investigation context so participants can coordinate using shared information<\/b><\/p>\n

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

                              Major incidents often require technical responders to work with application owners, management, legal, communications, or other stakeholders. A war room provides a shared incident-focused space where findings, decisions, questions, and response updates can remain connected to the case. This reduces fragmented communication and supports continuity across shifts. It does not replace technical evidence, tasks, or automation. Fortinet explicitly includes using war rooms for incident handling in the current exam objectives.<\/span><\/p>\n

                              Q235. A playbook should enrich an indicator only if no recent enrichment result is already stored. What is the BEST reason for this design?<\/b><\/p>\n

                                \n
                              1. <\/b> To avoid unnecessary external API calls while reusing sufficiently current information<\/span><\/li>\n
                              2. <\/b> To prevent all future enrichment<\/span><\/li>\n
                              3. <\/b> To remove the indicator from the incident<\/span><\/li>\n
                              4. <\/b> To make every connector read-only<\/span><\/li>\n<\/ol>\n

                                Correct Answer: 4. To avoid unnecessary external API calls while reusing sufficiently current information<\/b><\/p>\n

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

                                Repeated enrichment of the same indicator can waste API quota, increase playbook time, and create unnecessary dependency on an external service. If a trustworthy and sufficiently recent result is already stored, the playbook can use that value according to defined freshness criteria. However, the design must consider how quickly the intelligence can change; old reputation information may no longer be reliable. Conditional logic can therefore balance current context with integration efficiency. This type of workflow design is particularly useful when external services impose rate limits.<\/span><\/p>\n

                                Q236. Why should a FortiSOAR playbook distinguish between connector authentication failure and network timeout?<\/b><\/p>\n

                                  \n
                                1. <\/b> They represent different root causes and often require different remediation paths<\/span><\/li>\n
                                2. <\/b> Both errors always mean the password is wrong<\/span><\/li>\n
                                3. <\/b> Network timeouts can be fixed by changing incident severity<\/span><\/li>\n
                                4. <\/b> Error type is irrelevant if the action fails<\/span><\/li>\n<\/ol>\n

                                  Correct Answer: 3. They represent different root causes and often require different remediation paths<\/b><\/p>\n

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

                                  An authentication failure suggests incorrect, expired, revoked, or unauthorized credentials. A timeout more commonly indicates network reachability, DNS, firewall, service availability, or performance problems. Treating every failure the same can waste troubleshooting effort and produce ineffective retry behavior. Playbooks and connector diagnostics should preserve enough error context for administrators to identify the likely failure domain. Fortinet explicitly includes configuring connectors and debugging FortiSOAR playbooks in the current exam objectives.<\/span><\/p>\n

                                  Q237. A connector returns a list of dictionaries, and the playbook needs the <\/b>rating<\/b> field from each item. What capability is MOST appropriate?<\/b><\/p>\n

                                    \n
                                  1. <\/b> Jinja-based iteration or filtering to extract the required values<\/span><\/li>\n
                                  2. <\/b> A FortiSIEM retention change<\/span><\/li>\n
                                  3. <\/b> Analyst reassignment<\/span><\/li>\n
                                  4. <\/b> Disabling the connector<\/span><\/li>\n<\/ol>\n

                                    Correct Answer: 1. Jinja-based iteration or filtering to extract the required values<\/b><\/p>\n

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

                                    Structured connector output often contains lists, dictionaries, nested fields, or combinations of all three. Jinja expressions and filters can transform these structures into the exact values required by later playbook actions. In this example, the workflow can extract each item’s <\/span>rating<\/span> value and then combine, compare, or store the results as needed. Understanding actual runtime data types is important because incorrect assumptions can cause conditions or connector mappings to fail. Fortinet explicitly includes manipulating data using Jinja filters in the exam blueprint.<\/span><\/p>\n

                                    Q238. A playbook update causes an unexpected containment action during testing. What should the developer do FIRST?<\/b><\/p>\n

                                      \n
                                    1. <\/b> Deploy the change broadly to gather more examples<\/span><\/li>\n
                                    2. <\/b> Review execution history, trigger logic, conditions, and runtime data to identify why the containment branch was reached<\/span><\/li>\n
                                    3. <\/b> Delete the test incident and ignore the result<\/span><\/li>\n
                                    4. <\/b> Remove all approval steps<\/span><\/li>\n<\/ol>\n

                                      Correct Answer: 4. Review execution history, trigger logic, conditions, and runtime data to identify why the containment branch was reached<\/b><\/p>\n

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

                                      An unexpected high-impact action is a strong indication that the workflow logic needs investigation before production deployment. The developer should trace the playbook execution, inspect condition values, confirm the trigger, examine Jinja transformations, and review connector inputs. Testing should remain controlled until the cause is understood and corrected. Deleting the evidence or deploying more broadly would increase risk. Fortinet specifically includes playbook debugging and troubleshooting as an exam objective, making execution-history analysis an important practical skill.<\/span><\/p>\n

                                      Q239. What is the MAIN benefit of adding an analyst notification when an automated containment step fails?<\/b><\/p>\n

                                        \n
                                      1. <\/b> It ensures a human knows the expected response did not occur and can take alternative action<\/span><\/li>\n
                                      2. <\/b> It guarantees the connector will recover automatically<\/span><\/li>\n
                                      3. <\/b> It removes the need for playbook history<\/span><\/li>\n
                                      4. <\/b> It marks the incident resolved<\/span><\/li>\n<\/ol>\n

                                        Correct Answer: 3. It ensures a human knows the expected response did not occur and can take alternative action<\/b><\/p>\n

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

                                        Containment failures can create dangerous assumptions if analysts believe an endpoint, account, or network indicator was successfully restricted when it was not. A notification or task makes the failure visible so someone can investigate or perform a manual response. The alert should include enough context to explain what failed and which asset remains exposed. Notification does not repair the connector by itself, but it prevents silent failure. Resilient SOAR workflows should explicitly handle important error conditions instead of continuing as though every action succeeded.<\/span><\/p>\n

                                        Q240. What is the BEST criterion for deciding whether to fully automate a repetitive SOC response action?<\/b><\/p>\n

                                          \n
                                        1. <\/b> The action is technically possible<\/span><\/li>\n
                                        2. <\/b> The action occurs frequently<\/span><\/li>\n
                                        3. <\/b> The process is well understood, the decision criteria are reliable, and the business impact of incorrect execution is acceptably controlled<\/span><\/li>\n
                                        4. <\/b> An analyst dislikes performing it manually<\/span><\/li>\n<\/ol>\n

                                          Correct Answer: 2. The process is well understood, the decision criteria are reliable, and the business impact of incorrect execution is acceptably controlled<\/b><\/p>\n

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

                                          Frequency alone does not make an action suitable for full automation. Architects should consider how deterministic the decision is, whether required data is reliable, how disruptive the action could be, whether rollback is available, and whether human approval remains necessary. Low-risk enrichment is often easier to automate fully than disabling privileged accounts or isolating production systems. FortiSOAR is intended to improve speed and consistency, but automation should be proportional to risk. Fortinet\u2019s training explicitly covers defining automation requirements, playbook steps, enrichment, containment, recovery, and history management.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

                                          View Full Fortinet NSE7_SOC_AR-7.6 Exam Dumps and Practice Test Dumps. Q221. Why is event-source health monitoring important in a FortiSIEM deployment? It automatically corrects every parsing error It helps identify collection gaps that could reduce detection and investigation visibility It changes FortiSOAR incident severity It eliminates the need for correlation rules Correct Answer: 2. It […]<\/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\/20310"}],"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=20310"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/20310\/revisions"}],"predecessor-version":[{"id":20311,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/20310\/revisions\/20311"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=20310"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=20310"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=20310"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}