{"id":21635,"date":"2026-09-25T06:37:24","date_gmt":"2026-09-25T06:37:24","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=21635"},"modified":"2026-09-25T06:37:24","modified_gmt":"2026-09-25T06:37:24","slug":"fortinet-nse5_fwb_ad-8-0-practice-test-questions-and-exam-dumps-part-8-q141-160","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/fortinet-nse5_fwb_ad-8-0-practice-test-questions-and-exam-dumps-part-8-q141-160\/","title":{"rendered":"Fortinet NSE5_FWB_AD-8.0 Practice Test Questions and Exam Dumps Part 8 Q141-160"},"content":{"rendered":"

View Full <\/b>Fortinet NSE5_FWB_AD-8.0 Exam Dumps<\/b><\/a> and Practice Test Dumps<\/b><\/h2>\n

 <\/p>\n

Question 141. A FortiWeb administrator needs to ensure that a protected web application can identify requests for multiple domains hosted on the same FortiWeb appliance. Which HTTP request field is primarily used for hostname-based matching?<\/b><\/p>\n

    \n
  1. <\/b> Host header<\/span><\/li>\n
  2. <\/b> Content-Length header<\/span><\/li>\n
  3. <\/b> User-Agent header<\/span><\/li>\n
  4. <\/b> Accept-Encoding header<\/span><\/li>\n<\/ol>\n

    Correct Answer: 1. Host header<\/b><\/p>\n

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

    The HTTP Host header identifies the hostname requested by the client and is commonly used when FortiWeb needs to distinguish between multiple virtual hosts or applications. For example, requests for portal.example.com and shop.example.com can be associated with different server policies or backend resources based on hostname matching. Content-Length describes the size of the request body, User-Agent identifies the client software, and Accept-Encoding describes supported response compression methods. Administrators should verify Host header matching together with virtual server and server policy configuration when troubleshooting requests that appear to reach an unexpected application or backend resource.<\/span><\/p>\n

    Question 142. An application requires a maximum request-body size because extremely large requests could consume excessive resources. Which FortiWeb control should the administrator configure?<\/b><\/p>\n

      \n
    1. <\/b> Geographic access control<\/span><\/li>\n
    2. <\/b> Request size limitation<\/span><\/li>\n
    3. <\/b> Session persistence<\/span><\/li>\n
    4. <\/b> API discovery<\/span><\/li>\n<\/ol>\n

      Correct Answer: 2. Request size limitation<\/b><\/p>\n

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

      A request size limitation allows FortiWeb to restrict the amount of data accepted in an incoming HTTP request. This can help protect applications from oversized requests that may consume excessive memory, processing resources, or bandwidth. The appropriate limit depends on the application’s legitimate requirements, especially if it supports file uploads or APIs with larger payloads. Geographic access control restricts traffic based on location, session persistence controls backend affinity, and API discovery identifies API endpoints. Administrators should establish the limit based on documented application behavior and monitor rejected requests after deployment to determine whether legitimate traffic is being affected.<\/span><\/p>\n

      Question 143. A FortiWeb administrator wants to reduce the number of requests that reach a backend application by serving previously generated responses when appropriate. Which feature should be considered?<\/b><\/p>\n

        \n
      1. <\/b> Command injection protection<\/span><\/li>\n
      2. <\/b> HTTP caching<\/span><\/li>\n
      3. <\/b> Bot mitigation<\/span><\/li>\n
      4. <\/b> Certificate validation<\/span><\/li>\n<\/ol>\n

        Correct Answer: 2. HTTP caching<\/b><\/p>\n

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

        HTTP caching allows eligible responses to be stored and reused for subsequent requests, reducing the need to repeatedly retrieve the same content from backend servers. This can improve application delivery efficiency and reduce backend processing for cacheable resources. Caching must be configured carefully because dynamic or user-specific content should not be served incorrectly to another client. Command injection protection detects malicious operating-system command attempts, bot mitigation addresses automated traffic, and certificate validation supports secure TLS communication. Administrators should identify which application resources are safe to cache and define appropriate cache behavior based on response headers, content characteristics, and application requirements.<\/span><\/p>\n

        Question 144. A web application is receiving requests containing unexpected database operators and query syntax in user-controlled parameters. Which FortiWeb security mechanism should be investigated?<\/b><\/p>\n

          \n
        1. <\/b> SQL injection protection<\/span><\/li>\n
        2. <\/b> HTTP caching<\/span><\/li>\n
        3. <\/b> Server health monitoring<\/span><\/li>\n
        4. <\/b> URL redirection<\/span><\/li>\n<\/ol>\n

          Correct Answer: 1. SQL injection protection<\/b><\/p>\n

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

          SQL injection protection is intended to identify attempts to manipulate backend database queries through malicious application input. Attackers may insert SQL operators, commands, or specially crafted strings into parameters, forms, cookies, or other request components. FortiWeb can inspect these requests using WAF security mechanisms and apply the configured action. HTTP caching does not provide database attack detection, health monitoring checks backend availability, and URL redirection changes where clients are sent. Administrators should investigate the event details and matched protection rule when legitimate requests are blocked, because some applications may legitimately process special characters or query-like data.<\/span><\/p>\n

          Question 145. An organization wants to identify weaknesses in a web application by actively testing its exposed resources. Which FortiWeb feature is designed for this purpose?<\/b><\/p>\n

            \n
          1. <\/b> Server pool persistence<\/span><\/li>\n
          2. <\/b> Web vulnerability scanning<\/span><\/li>\n
          3. <\/b> HTTP method restriction<\/span><\/li>\n
          4. <\/b> Cookie security<\/span><\/li>\n<\/ol>\n

            Correct Answer: 2. Web vulnerability scanning<\/b><\/p>\n

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

            Web vulnerability scanning is designed to assess web applications for security weaknesses that may be exploitable. It can help administrators identify vulnerabilities in exposed application resources and prioritize remediation. This assessment function is different from normal WAF enforcement, which evaluates live requests and applies configured security policies. Server pool persistence manages backend affinity, HTTP method restriction controls allowed request methods, and cookie security addresses session-related cookie protections. Administrators should perform vulnerability scanning in accordance with the organization’s testing procedures and carefully review findings before taking action. Findings should be validated and remediated through appropriate application development and security processes.<\/span><\/p>\n

            Question 146. A company wants FortiWeb to reject requests originating from a known malicious IP address before the request reaches the application server. Which control is most appropriate?<\/b><\/p>\n

              \n
            1. <\/b> IP-based access control<\/span><\/li>\n
            2. <\/b> HTTP response caching<\/span><\/li>\n
            3. <\/b> Server health check<\/span><\/li>\n
            4. <\/b> TLS backend re-encryption<\/span><\/li>\n<\/ol>\n

              Correct Answer: 1. IP-based access control<\/b><\/p>\n

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

              IP-based access control allows FortiWeb to permit or deny traffic according to source IP information. A known malicious address can therefore be denied before the request is forwarded to the protected backend application. This can provide an immediate control for identified unwanted sources. HTTP caching manages application responses, health checks determine backend availability, and TLS re-encryption secures the connection between FortiWeb and an HTTPS backend. Administrators should remember that IP-based blocking is only one layer of defense because attackers may change addresses or operate through distributed infrastructure. Security logs should be reviewed to confirm that the intended traffic is being blocked.<\/span><\/p>\n

              Question 147. A FortiWeb administrator needs to prevent an application from accepting TRACE requests because the application does not use that method. Which setting should be configured?<\/b><\/p>\n

                \n
              1. <\/b> HTTP method restriction<\/span><\/li>\n
              2. <\/b> API discovery<\/span><\/li>\n
              3. <\/b> Server health check<\/span><\/li>\n
              4. <\/b> HTTP caching<\/span><\/li>\n<\/ol>\n

                Correct Answer: 1. HTTP method restriction<\/b><\/p>\n

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

                HTTP method restriction allows administrators to define which HTTP methods an application is permitted to receive. If an application does not require TRACE, the administrator can exclude it from the allowed method set. Restricting unnecessary methods can reduce the attack surface and prevent unsupported operations from reaching the backend. API discovery identifies API endpoints, health checks monitor server availability, and caching manages responses. Before applying the restriction, the administrator should verify the application’s complete request workflow because APIs or administrative interfaces may legitimately require methods that are not used by the main web interface. Logs can help identify unexpected legitimate method usage.<\/span><\/p>\n

                Question 148. A company wants to protect a public-facing API from malformed parameters and unexpected request structures. Which FortiWeb capability should be investigated?<\/b><\/p>\n

                  \n
                1. <\/b> API protection and request validation<\/span><\/li>\n
                2. <\/b> HTTP caching only<\/span><\/li>\n
                3. <\/b> Server health checking only<\/span><\/li>\n
                4. <\/b> Geographic load balancing only<\/span><\/li>\n<\/ol>\n

                  Correct Answer: 1. API protection and request validation<\/b><\/p>\n

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

                  API protection and request validation can help enforce expected characteristics of API traffic and reject requests that do not conform to the application’s defined requirements. This is particularly useful for APIs because attackers may manipulate parameters, methods, payloads, or request structures to bypass application controls. HTTP caching is focused on response delivery, while health checking evaluates backend availability. Geographic load balancing distributes traffic rather than validating API requests. Administrators should establish API security policies based on documented API behavior and test legitimate requests carefully. Effective API protection should complement secure authentication, authorization, input validation, and application development practices.<\/span><\/p>\n

                  Question 149. A FortiWeb administrator wants to keep clients connected to the same backend server during a session even when traffic is distributed across several servers. Which feature should be enabled?<\/b><\/p>\n

                    \n
                  1. <\/b> URL rewriting<\/span><\/li>\n
                  2. <\/b> Session persistence<\/span><\/li>\n
                  3. <\/b> Web vulnerability scanning<\/span><\/li>\n
                  4. <\/b> Geographic access control<\/span><\/li>\n<\/ol>\n

                    Correct Answer: 2. Session persistence<\/b><\/p>\n

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

                    Session persistence maintains an association between a client session and a backend server when FortiWeb is distributing traffic across multiple servers. This can be necessary when application session data is stored locally on one backend rather than in a shared session repository. Without persistence, a subsequent request could be routed to another server that does not have the original session state. URL rewriting modifies request URLs, vulnerability scanning identifies application weaknesses, and geographic access control restricts clients based on location. Administrators should select persistence settings that match the application’s session mechanism and verify behavior during backend failure to ensure that availability and user sessions are handled as expected.<\/span><\/p>\n

                    Question 150. A security team wants to detect automated clients abusing a login endpoint with repeated requests. Which FortiWeb feature should be investigated first?<\/b><\/p>\n

                      \n
                    1. <\/b> Bot management and mitigation<\/span><\/li>\n
                    2. <\/b> HTTP response caching<\/span><\/li>\n
                    3. <\/b> Backend certificate validation<\/span><\/li>\n
                    4. <\/b> URL rewriting<\/span><\/li>\n<\/ol>\n

                      Correct Answer: 1. Bot management and mitigation<\/b><\/p>\n

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

                      Bot management and mitigation can help identify automated clients and apply controls against unwanted automation. Login endpoints are common targets for automated credential attacks, password spraying, and other abusive request patterns. FortiWeb can use bot-related detection and enforcement capabilities to distinguish suspicious automated activity from legitimate clients, depending on configuration. HTTP caching does not identify bots, certificate validation secures TLS relationships, and URL rewriting changes request paths. Administrators should account for legitimate automation such as monitoring services, approved integrations, and API clients. Bot controls can also be combined with rate limiting and authentication protections to provide broader defense against automated abuse.<\/span><\/p>\n

                      Question 151. A backend web server is available, but FortiWeb continues sending traffic to it even though application requests are failing. Which configuration should be reviewed to determine whether FortiWeb can detect the failure?<\/b><\/p>\n

                        \n
                      1. <\/b> Health-check configuration<\/span><\/li>\n
                      2. <\/b> HTTP cache expiration<\/span><\/li>\n
                      3. <\/b> Cookie security<\/span><\/li>\n
                      4. <\/b> URL redirection<\/span><\/li>\n<\/ol>\n

                        Correct Answer: 1. Health-check configuration<\/b><\/p>\n

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

                        Health checks determine whether FortiWeb considers a backend server available for traffic. If a basic connectivity check succeeds while the application itself is failing, the configured health-check method may not be testing the appropriate application behavior. Administrators should review the health-check type, target resource, expected response, interval, timeout, and failure threshold. HTTP cache expiration affects cached responses, cookie security protects session cookies, and URL redirection changes client request destinations. A more appropriate health check may be needed to verify that the required application service is functioning rather than merely confirming that a network connection can be established.<\/span><\/p>\n

                        Question 152. An organization wants to restrict access to an application according to the geographic location associated with source IP addresses. Which FortiWeb feature should be used?<\/b><\/p>\n

                          \n
                        1. <\/b> API discovery<\/span><\/li>\n
                        2. <\/b> Geographic IP access control<\/span><\/li>\n
                        3. <\/b> HTTP method restriction<\/span><\/li>\n
                        4. <\/b> Server pool load balancing<\/span><\/li>\n<\/ol>\n

                          Correct Answer: 2. Geographic IP access control<\/b><\/p>\n

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

                          Geographic IP access control can permit or deny traffic based on the country or region associated with a source IP address. This can be used when an application has geographic access requirements or when administrators need to reduce exposure from selected locations. The accuracy of geographic filtering depends on the underlying IP geolocation information, so it should be treated as one layer of a broader security strategy. API discovery identifies APIs, HTTP method restrictions control request methods, and server pool load balancing distributes traffic among backend servers. Administrators should verify legitimate user locations and monitor policy results before applying broad geographic restrictions.<\/span><\/p>\n

                          Question 153. A FortiWeb administrator wants to protect an application against attempts to execute operating-system commands through HTTP parameters. Which WAF protection is directly relevant?<\/b><\/p>\n

                            \n
                          1. <\/b> Command injection protection<\/span><\/li>\n
                          2. <\/b> HTTP caching<\/span><\/li>\n
                          3. <\/b> Session persistence<\/span><\/li>\n
                          4. <\/b> Server load balancing<\/span><\/li>\n<\/ol>\n

                            Correct Answer: 1. Command injection protection<\/b><\/p>\n

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

                            Command injection protection is designed to identify malicious input intended to cause an application or backend operating system to execute unintended commands. Such attacks can use request parameters, form fields, headers, or other user-controlled values. FortiWeb can inspect these request components using WAF security controls and apply the configured enforcement action. HTTP caching and session persistence do not inspect command syntax, while load balancing determines which backend receives a request. Administrators should investigate matched security events when tuning this protection because legitimate applications can sometimes accept characters that resemble command syntax. Protection should be combined with secure application input validation and operating-system controls.<\/span><\/p>\n

                            Question 154. A company wants to make security event information from FortiWeb available to its central SIEM platform. What should the administrator configure?<\/b><\/p>\n

                              \n
                            1. <\/b> Centralized log forwarding<\/span><\/li>\n
                            2. <\/b> HTTP method restriction<\/span><\/li>\n
                            3. <\/b> Server pool persistence<\/span><\/li>\n
                            4. <\/b> URL rewriting<\/span><\/li>\n<\/ol>\n

                              Correct Answer: 1. Centralized log forwarding<\/b><\/p>\n

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

                              Centralized log forwarding allows FortiWeb to send relevant events and log information to an external logging or SIEM system. This gives security teams a centralized location for monitoring, correlation, investigation, and long-term analysis. Administrators should configure the appropriate destination and determine which event types and severity levels should be forwarded. HTTP method restriction controls application request methods, server persistence affects backend routing, and URL rewriting modifies request paths. After configuring forwarding, administrators should verify that events arrive successfully and contain the expected timestamps, source information, action, and security details. Appropriate log retention and access controls should also be considered.<\/span><\/p>\n

                              Question 155. A protected application uses HTTPS on the client side, and the organization requires FortiWeb to use HTTPS when communicating with the backend. What should be configured?<\/b><\/p>\n

                                \n
                              1. <\/b> Client TLS termination with backend HTTPS<\/span><\/li>\n
                              2. <\/b> HTTP-only backend communication<\/span><\/li>\n
                              3. <\/b> DNS filtering without encryption<\/span><\/li>\n
                              4. <\/b> Browser-side caching<\/span><\/li>\n<\/ol>\n

                                Correct Answer: 1. Client TLS termination with backend HTTPS<\/b><\/p>\n

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

                                FortiWeb can terminate the client’s HTTPS session, inspect the decrypted application traffic, and then establish a separate HTTPS connection to the backend server. This provides encryption on both sides of FortiWeb while preserving the ability to inspect application-layer traffic. The backend HTTPS configuration requires appropriate certificate and trust settings. Using HTTP between FortiWeb and the backend would leave that network segment unencrypted. DNS filtering and browser caching do not provide the required transport security. Administrators should verify the client-facing certificate, backend certificate validation, supported TLS settings, and connectivity when troubleshooting encrypted reverse-proxy deployments.<\/span><\/p>\n

                                Question 156. A security administrator suspects that legitimate application traffic is being blocked by a WAF rule. Which action should be performed before changing the security policy?<\/b><\/p>\n

                                  \n
                                1. <\/b> Review the security event and identify the matched rule<\/span><\/li>\n
                                2. <\/b> Disable all WAF protections<\/span><\/li>\n
                                3. <\/b> Remove the application from FortiWeb<\/span><\/li>\n
                                4. <\/b> Delete all backend servers<\/span><\/li>\n<\/ol>\n

                                  Correct Answer: 1. Review the security event and identify the matched rule<\/b><\/p>\n

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

                                  The administrator should first determine which security control caused the request to be blocked. FortiWeb security events and logs can provide information about the matched rule, request characteristics, and enforcement action. Reviewing this evidence helps distinguish a genuine attack from a false positive. Disabling all WAF protections would remove important security controls without identifying the cause, while removing backend resources does not address the policy decision. Once the triggering rule is identified, the administrator can evaluate whether a narrowly scoped exception or policy adjustment is justified. Any change should then be tested with both legitimate and malicious traffic.<\/span><\/p>\n

                                  Question 157. A web application has an administrative path that should never be accessible from the public Internet. Which FortiWeb configuration can enforce this requirement?<\/b><\/p>\n

                                    \n
                                  1. <\/b> URL access control with an appropriate source restriction<\/span><\/li>\n
                                  2. <\/b> HTTP response caching<\/span><\/li>\n
                                  3. <\/b> Server health checks<\/span><\/li>\n
                                  4. <\/b> API discovery only<\/span><\/li>\n<\/ol>\n

                                    Correct Answer: 1. URL access control with an appropriate source restriction<\/b><\/p>\n

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

                                    URL access control can identify the administrative path, while a source restriction can limit which clients are permitted to access it. This provides targeted protection for sensitive application resources. Depending on the environment, administrators may restrict access to approved management networks or other trusted sources. Caching does not provide authorization, health checks monitor backend availability, and API discovery provides API visibility. Administrators should ensure that the protected path is correctly identified and that legitimate administrative access requirements are accounted for. Logging denied requests can provide visibility into attempted access from unauthorized sources and help verify that the policy is operating as intended.<\/span><\/p>\n

                                    Question 158. A company wants to reduce the impact of excessive request rates against a resource-intensive application endpoint while continuing to permit normal users. Which feature should be configured?<\/b><\/p>\n

                                      \n
                                    1. <\/b> Certificate renewal<\/span><\/li>\n
                                    2. <\/b> Rate limiting<\/span><\/li>\n
                                    3. <\/b> Web vulnerability scanning<\/span><\/li>\n
                                    4. <\/b> URL rewriting<\/span><\/li>\n<\/ol>\n

                                      Correct Answer: 2. Rate limiting<\/b><\/p>\n

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

                                      Rate limiting can restrict excessive request activity while allowing requests that remain within defined thresholds. This is useful for resource-intensive endpoints that could otherwise be overwhelmed by abusive or unexpectedly high request rates. Administrators should establish thresholds based on observed normal traffic and consider different requirements for users, APIs, and trusted automation. Certificate renewal manages TLS credentials, vulnerability scanning identifies application weaknesses, and URL rewriting changes request paths. Rate limiting can complement DoS protection and bot mitigation, but administrators should monitor blocked or throttled requests after deployment to ensure that legitimate traffic is not unnecessarily affected.<\/span><\/p>\n

                                      Question 159. A FortiWeb administrator needs to determine whether a request is being processed by the intended virtual server and server policy. Which information should be compared with the policy configuration?<\/b><\/p>\n

                                        \n
                                      1. <\/b> Request destination, Host header, and other matching attributes<\/span><\/li>\n
                                      2. <\/b> Only the backend server’s disk usage<\/span><\/li>\n
                                      3. <\/b> Only the browser’s installed extensions<\/span><\/li>\n
                                      4. <\/b> Only the HTTP response cache age<\/span><\/li>\n<\/ol>\n

                                        Correct Answer: 1. Request destination, Host header, and other matching attributes<\/b><\/p>\n

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

                                        FortiWeb policy selection depends on request characteristics and the configured matching conditions. Administrators troubleshooting unexpected policy behavior should compare the request’s destination, Host header, protocol, and other relevant attributes with the virtual server and server policy configuration. This can reveal whether the request is reaching the expected policy or matching another configuration first. Backend disk usage may affect application performance but does not normally determine FortiWeb policy selection. Browser extensions and cache age are also unlikely to explain server-policy matching. Reviewing traffic and security logs alongside the request attributes can provide additional evidence about how FortiWeb processed the request.<\/span><\/p>\n

                                        Question 160. A security team wants to identify suspicious requests while preserving enough information to investigate false positives later. Which FortiWeb capability should be emphasized?<\/b><\/p>\n

                                          \n
                                        1. <\/b> Security and traffic logging<\/span><\/li>\n
                                        2. <\/b> HTTP caching<\/span><\/li>\n
                                        3. <\/b> Server pool load balancing<\/span><\/li>\n
                                        4. <\/b> URL rewriting<\/span><\/li>\n<\/ol>\n

                                          Correct Answer: 1. Security and traffic logging<\/b><\/p>\n

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

                                          Security and traffic logging provides visibility into requests, policy decisions, security events, and enforcement actions. Detailed logs can help administrators determine why a request was blocked or allowed and can provide evidence when investigating false positives. Logging is therefore an important companion to WAF and other security controls. HTTP caching improves response delivery, load balancing distributes requests among backend servers, and URL rewriting modifies request destinations or paths. Administrators should configure appropriate logging levels and retention while considering storage capacity and privacy requirements. Centralized forwarding can also provide additional resilience and enable correlation with security events from other systems.<\/span><\/p>\n

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

                                          View Full Fortinet NSE5_FWB_AD-8.0 Exam Dumps and Practice Test Dumps   Question 141. A FortiWeb administrator needs to ensure that a protected web application can identify requests for multiple domains hosted on the same FortiWeb appliance. Which HTTP request field is primarily used for hostname-based matching? Host header Content-Length header User-Agent header Accept-Encoding header Correct […]<\/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\/21635"}],"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=21635"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/21635\/revisions"}],"predecessor-version":[{"id":21636,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/21635\/revisions\/21636"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=21635"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=21635"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=21635"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}