{"id":21653,"date":"2026-09-25T06:41:48","date_gmt":"2026-09-25T06:41:48","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=21653"},"modified":"2026-09-25T06:41:48","modified_gmt":"2026-09-25T06:41:48","slug":"fortinet-nse5_fwb_ad-8-0-practice-test-questions-and-exam-dumps-part-17-q321-340","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/fortinet-nse5_fwb_ad-8-0-practice-test-questions-and-exam-dumps-part-17-q321-340\/","title":{"rendered":"Fortinet NSE5_FWB_AD-8.0 Practice Test Questions and Exam Dumps Part 17 Q321-340"},"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 321. Which FortiWeb feature allows an administrator to apply different protection settings based on the requested hostname or URL?<\/b><\/p>\n

    \n
  1. <\/b> System DNS configuration<\/span><\/li>\n
  2. <\/b> Hardware acceleration<\/span><\/li>\n
  3. <\/b> Firmware image management<\/span><\/li>\n
  4. <\/b> Web protection profile assignment<\/span><\/li>\n<\/ol>\n

    Correct Answer: 4. Web protection profile assignment<\/b><\/p>\n

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

    Web protection profile assignment allows FortiWeb to apply different security policies according to characteristics of incoming web requests, such as the protected virtual server, hostname, or URL context. This is useful when multiple applications with different security requirements share the same FortiWeb appliance. Administrators can associate appropriate protection profiles with the relevant traffic instead of applying one identical security configuration to every application. DNS configuration, hardware acceleration, and firmware management do not determine which WAF protections are applied to an individual HTTP request. This separation of policy from system-level configuration provides more granular control over application security.<\/span><\/p>\n

    Question 322. When FortiWeb performs SSL\/TLS offloading for a protected application, what is the primary benefit?<\/b><\/p>\n

      \n
    1. <\/b> It allows FortiWeb to decrypt HTTPS traffic for inspection<\/span><\/li>\n
    2. <\/b> It eliminates the need for HTTP inspection<\/span><\/li>\n
    3. <\/b> It prevents clients from establishing TLS sessions<\/span><\/li>\n
    4. <\/b> It converts HTTPS traffic into DNS queries<\/span><\/li>\n<\/ol>\n

      Correct Answer: 1. It allows FortiWeb to decrypt HTTPS traffic for inspection<\/b><\/p>\n

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

      SSL\/TLS offloading allows FortiWeb to terminate the client-side TLS session, decrypt the HTTPS request, inspect the application traffic, and then establish the appropriate connection toward the backend server. This is particularly important for WAF protection because encrypted requests cannot be meaningfully inspected while their contents remain encrypted. FortiWeb can therefore apply security controls such as signatures, access rules, and other web protection mechanisms to the decrypted request. SSL offloading does not prevent clients from using HTTPS, nor does it eliminate HTTP inspection. The main security benefit is visibility into encrypted application traffic.<\/span><\/p>\n

      Question 323. What is the purpose of configuring a server pool on FortiWeb?<\/b><\/p>\n

        \n
      1. <\/b> To store administrator accounts<\/span><\/li>\n
      2. <\/b> To define DNS servers used by FortiWeb<\/span><\/li>\n
      3. <\/b> To store FortiWeb firmware images<\/span><\/li>\n
      4. <\/b> To group backend servers that can receive application traffic<\/span><\/li>\n<\/ol>\n

        Correct Answer: 4. To group backend servers that can receive application traffic<\/b><\/p>\n

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

        A server pool groups backend or real servers that FortiWeb can use when forwarding requests for a protected application. The pool provides the backend destinations used by the virtual server or associated application configuration and can support load-balancing behavior among multiple servers. Depending on the configuration, FortiWeb can use health checks and load-balancing methods to determine which server should receive a request. Server pools are unrelated to administrator accounts, DNS configuration, or firmware storage. Proper server-pool configuration is therefore an important part of reverse-proxy deployment and backend traffic distribution.<\/span><\/p>\n

        Question 324. Which configuration is most directly responsible for determining whether a backend server is considered available for load balancing?<\/b><\/p>\n

          \n
        1. <\/b> Administrator authentication profile<\/span><\/li>\n
        2. <\/b> Server health check<\/span><\/li>\n
        3. <\/b> Web cache policy<\/span><\/li>\n
        4. <\/b> URL rewriting rule<\/span><\/li>\n<\/ol>\n

          Correct Answer: 2. Server health check<\/b><\/p>\n

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

          A server health check tests whether a backend server is available and capable of responding to application traffic. FortiWeb can use configured health-check methods to monitor real servers and avoid forwarding requests to destinations that are unavailable or unhealthy. Depending on the configuration, the check can involve connection tests or application-level responses. Administrator authentication, caching, and URL rewriting serve different purposes and do not determine backend server availability. Health monitoring is especially important when a server pool contains multiple real servers because it helps FortiWeb maintain traffic availability by excluding failed or unresponsive destinations.<\/span><\/p>\n

          Question 325. Why is SNI important when FortiWeb protects multiple HTTPS applications on the same IP address?<\/b><\/p>\n

            \n
          1. <\/b> It disables certificate validation<\/span><\/li>\n
          2. <\/b> It converts HTTPS into HTTP automatically<\/span><\/li>\n
          3. <\/b> It assigns a unique MAC address to every application<\/span><\/li>\n
          4. <\/b> It allows TLS clients to indicate the requested hostname during the handshake<\/span><\/li>\n<\/ol>\n

            Correct Answer: 4. It allows TLS clients to indicate the requested hostname during the handshake<\/b><\/p>\n

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

            Server Name Indication, or SNI, allows a TLS client to include the hostname it is requesting during the TLS handshake. This is useful when multiple HTTPS applications or domains share the same IP address because FortiWeb can use the requested hostname when determining the appropriate TLS configuration and certificate. SNI does not disable certificate validation, change the protocol into HTTP, or assign network hardware addresses. In environments hosting multiple secure applications on shared infrastructure, correct SNI and certificate configuration helps FortiWeb present the appropriate certificate and process HTTPS traffic for the intended application.<\/span><\/p>\n

            Question 326. Which FortiWeb capability is specifically intended to detect and control automated clients such as malicious bots?<\/b><\/p>\n

              \n
            1. <\/b> Static routing<\/span><\/li>\n
            2. <\/b> Interface aggregation<\/span><\/li>\n
            3. <\/b> Bot mitigation<\/span><\/li>\n
            4. <\/b> Configuration backup<\/span><\/li>\n<\/ol>\n

              Correct Answer: 3. Bot mitigation<\/b><\/p>\n

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

              Bot mitigation provides controls for identifying and managing automated clients that access web applications. Legitimate automated services and malicious bots can behave differently from normal human users, and FortiWeb can use available bot-detection mechanisms and related controls to identify suspicious automation. Depending on the configured policy, detected bots may be monitored, challenged, limited, or blocked. Static routing determines packet forwarding, interface aggregation combines network interfaces, and configuration backup preserves system settings. None of those functions directly address automated application clients. Bot mitigation is therefore the FortiWeb capability most directly associated with controlling unwanted automated web activity.<\/span><\/p>\n

              Question 327. What is the primary purpose of a FortiWeb custom signature?<\/b><\/p>\n

                \n
              1. <\/b> To detect application-specific traffic patterns not adequately covered by predefined signatures<\/span><\/li>\n
              2. <\/b> To replace the FortiWeb operating system<\/span><\/li>\n
              3. <\/b> To configure physical interface speed<\/span><\/li>\n
              4. <\/b> To create administrator password policies<\/span><\/li>\n<\/ol>\n

                Correct Answer: 1. To detect application-specific traffic patterns not adequately covered by predefined signatures<\/b><\/p>\n

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

                Custom signatures allow administrators to create additional detection rules for application-specific attack patterns or suspicious content that may not be adequately addressed by the predefined signature database. This is useful when an organization has unique application behavior, proprietary parameters, or a known attack pattern that requires a specialized rule. Custom signatures supplement the existing security controls rather than replacing the operating system or configuring network-interface characteristics. They also have no direct relationship to administrator password policies. When creating custom signatures, administrators should carefully define matching conditions to reduce false positives while still detecting the intended malicious pattern.<\/span><\/p>\n

                Question 328. What HTTP characteristic can be restricted to reduce unnecessary or potentially risky application requests?<\/b><\/p>\n

                  \n
                1. <\/b> Firmware version<\/span><\/li>\n
                2. <\/b> RAID configuration<\/span><\/li>\n
                3. <\/b> Administrator timezone<\/span><\/li>\n
                4. <\/b> HTTP method<\/span><\/li>\n<\/ol>\n

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

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

                  HTTP methods such as GET, POST, PUT, DELETE, and other methods determine the type of operation requested by a client. FortiWeb can use HTTP-method controls as part of application security policies to restrict methods that an application does not require. Limiting unnecessary methods can reduce the application’s attack surface and help prevent unexpected operations. Firmware versions, RAID settings, and administrator timezone settings are system-level configurations and do not describe the requested HTTP operation. Administrators should determine which methods are actually required by each protected application before restricting them, because blocking a legitimate method can interfere with normal application functionality.<\/span><\/p>\n

                  Question 329. What is the primary function of FortiWeb URL rewriting?<\/b><\/p>\n

                    \n
                  1. <\/b> To replace network interfaces<\/span><\/li>\n
                  2. <\/b> To modify request or response URLs according to configured rules<\/span><\/li>\n
                  3. <\/b> To synchronize administrator passwords<\/span><\/li>\n
                  4. <\/b> To update FortiWeb firmware automatically<\/span><\/li>\n<\/ol>\n

                    Correct Answer: 2. To modify request or response URLs according to configured rules<\/b><\/p>\n

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

                    URL rewriting allows FortiWeb to modify URLs in HTTP requests or responses according to configured conditions and replacement rules. It can be useful when an application has changed its URL structure, when traffic needs to be redirected to a different application path, or when a protected application requires specific URL transformations. URL rewriting is an application-layer function and does not replace interfaces, synchronize administrator credentials, or perform firmware upgrades. Administrators should design rewriting rules carefully so that they affect only the intended traffic. Incorrect rules can cause unexpected application behavior or redirect legitimate requests to unintended resources.<\/span><\/p>\n

                    Question 330. What is the primary purpose of session persistence in a load-balanced FortiWeb deployment?<\/b><\/p>\n

                      \n
                    1. <\/b> It forces every client to use a different backend server<\/span><\/li>\n
                    2. <\/b> It disables backend health checks<\/span><\/li>\n
                    3. <\/b> It encrypts all server-pool configuration files<\/span><\/li>\n
                    4. <\/b> It keeps related requests from a client associated with the same backend server when required<\/span><\/li>\n<\/ol>\n

                      Correct Answer: 4. It keeps related requests from a client associated with the same backend server when required<\/b><\/p>\n

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

                      Session persistence, sometimes called session affinity or stickiness, helps ensure that requests belonging to the same client session continue to reach the same backend server when an application requires state to remain local to that server. This can be important for applications that maintain session information locally instead of sharing it across all backend servers. Persistence does not disable health checks or encrypt configuration files. It also does not intentionally force every client to a different server. Proper persistence configuration must be balanced with availability requirements because an unhealthy backend may need to be removed from service even when existing sessions were previously associated with it.<\/span><\/p>\n

                      Question 331. Which FortiWeb function is most useful for identifying unusual application behavior based on learned traffic patterns?<\/b><\/p>\n

                        \n
                      1. <\/b> Machine-learning-based anomaly detection<\/span><\/li>\n
                      2. <\/b> Interface renaming<\/span><\/li>\n
                      3. <\/b> Static DNS configuration<\/span><\/li>\n
                      4. <\/b> Firmware boot selection<\/span><\/li>\n<\/ol>\n

                        Correct Answer: 1. Machine-learning-based anomaly detection<\/b><\/p>\n

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

                        Machine-learning-based anomaly detection can help identify application behavior that deviates from established traffic patterns. By learning characteristics of normal application traffic, anomaly-detection mechanisms can identify unusual requests or behaviors that may warrant further investigation. This approach can complement traditional signature-based protection because not every suspicious behavior necessarily matches a predefined attack signature. Interface naming, DNS configuration, and firmware boot selection are unrelated to behavioral analysis of application traffic. Administrators should still validate detected anomalies because unusual activity is not automatically malicious. Proper tuning and understanding of legitimate application behavior can help reduce false positives.<\/span><\/p>\n

                        Question 332. Why should administrators configure appropriate exclusions or exceptions for legitimate application behavior in WAF policies?<\/b><\/p>\n

                          \n
                        1. <\/b> To disable all security inspection<\/span><\/li>\n
                        2. <\/b> To reduce false positives while retaining protection for other traffic<\/span><\/li>\n
                        3. <\/b> To prevent FortiWeb from generating any logs<\/span><\/li>\n
                        4. <\/b> To bypass backend server health checks<\/span><\/li>\n<\/ol>\n

                          Correct Answer: 2. To reduce false positives while retaining protection for other traffic<\/b><\/p>\n

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

                          Legitimate applications sometimes generate requests that resemble attack patterns or violate generic security assumptions. Carefully configured exceptions or exclusions can allow those legitimate requests while keeping the relevant protection enabled for other traffic. This approach is preferable to disabling an entire security control when only a specific application behavior requires an exception. Exceptions should be as narrow as practical and based on a clear understanding of the affected traffic. They do not inherently disable logging, bypass health checks, or turn off all WAF inspection. Properly scoped exclusions help administrators balance application compatibility with continued security enforcement.<\/span><\/p>\n

                          Question 333. What is a key advantage of forwarding FortiWeb security logs to a centralized logging system?<\/b><\/p>\n

                            \n
                          1. <\/b> It removes the need for security policies<\/span><\/li>\n
                          2. <\/b> It automatically fixes detected attacks<\/span><\/li>\n
                          3. <\/b> It provides centralized storage and analysis of events from FortiWeb<\/span><\/li>\n
                          4. <\/b> It converts all HTTP requests to HTTPS<\/span><\/li>\n<\/ol>\n

                            Correct Answer: 3. It provides centralized storage and analysis of events from FortiWeb<\/b><\/p>\n

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

                            Centralized log forwarding allows FortiWeb events to be collected by an external logging or security-analysis system. This can improve long-term retention, correlation, monitoring, reporting, and incident investigation because security events from FortiWeb can be analyzed alongside information from other systems. Log forwarding does not automatically remediate attacks, remove the need for security policies, or convert HTTP traffic into HTTPS. Administrators can use centralized logging to identify recurring attack patterns, investigate blocked requests, and correlate application events with activity observed elsewhere in the network. Reliable log transport and appropriate filtering should be configured according to operational requirements.<\/span><\/p>\n

                            Question 334. What is the primary security purpose of API schema validation on a protected API?<\/b><\/p>\n

                              \n
                            1. <\/b> To increase physical interface bandwidth<\/span><\/li>\n
                            2. <\/b> To replace TLS certificates<\/span><\/li>\n
                            3. <\/b> To synchronize FortiWeb HA passwords<\/span><\/li>\n
                            4. <\/b> To verify that API requests conform to expected structures and data definitions<\/span><\/li>\n<\/ol>\n

                              Correct Answer: 4. To verify that API requests conform to expected structures and data definitions<\/b><\/p>\n

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

                              API schema validation checks whether requests conform to an expected API definition, including aspects such as supported parameters, data types, structures, and required fields. This provides an additional security layer because malformed or unexpected requests can be identified before reaching the backend application. Schema validation is different from physical bandwidth configuration, certificate management, or HA credential synchronization. For organizations exposing APIs, enforcing an appropriate schema can help reduce the risk associated with unexpected input and improve consistency between the documented API contract and actual requests. The schema must be maintained when legitimate API versions or structures change.<\/span><\/p>\n

                              Question 335. What is the most appropriate first step when troubleshooting a FortiWeb policy that unexpectedly blocks legitimate requests?<\/b><\/p>\n

                                \n
                              1. <\/b> Review the matching policy, logs, and triggered security rule<\/span><\/li>\n
                              2. <\/b> Immediately disable every security feature<\/span><\/li>\n
                              3. <\/b> Delete the protected application configuration<\/span><\/li>\n
                              4. <\/b> Replace all backend servers<\/span><\/li>\n<\/ol>\n

                                Correct Answer: 1. Review the matching policy, logs, and triggered security rule<\/b><\/p>\n

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

                                When legitimate requests are unexpectedly blocked, the first troubleshooting step should be to determine exactly which FortiWeb policy and security rule handled the request. Logs can reveal the source, destination, URL, action, and security mechanism that caused the block. Reviewing the matching policy and triggered rule helps administrators identify whether the problem is caused by a signature, access rule, validation setting, rate limit, or another control. Disabling all security features or deleting application configuration removes protection without identifying the underlying issue. Replacing backend servers is also unrelated unless separate evidence indicates a backend failure.<\/span><\/p>\n

                                Question 336. What is the main purpose of administrator profiles in FortiWeb?<\/b><\/p>\n

                                  \n
                                1. <\/b> To load-balance HTTP requests<\/span><\/li>\n
                                2. <\/b> To define permissions for administrative access to system functions<\/span><\/li>\n
                                3. <\/b> To inspect SQL queries from clients<\/span><\/li>\n
                                4. <\/b> To define backend server health-check intervals<\/span><\/li>\n<\/ol>\n

                                  Correct Answer: 2. To define permissions for administrative access to system functions<\/b><\/p>\n

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

                                  Administrator profiles are used to control what administrative users are permitted to view or modify on FortiWeb. Role-based administrative access supports the principle of least privilege by allowing users to receive only the permissions necessary for their responsibilities. This helps reduce the risk of unauthorized configuration changes and limits the impact of compromised administrator credentials. Administrator profiles are separate from traffic-processing functions such as load balancing, SQL inspection, and backend health checks. A carefully designed administrator-role structure can also improve operational accountability by separating responsibilities between security, network, and system administrators.<\/span><\/p>\n

                                  Question 337. What is the purpose of configuring a protected host or protected application on FortiWeb?<\/b><\/p>\n

                                    \n
                                  1. <\/b> To create a new administrator account<\/span><\/li>\n
                                  2. <\/b> To select the FortiWeb boot partition<\/span><\/li>\n
                                  3. <\/b> To define the application or destination that FortiWeb is responsible for protecting<\/span><\/li>\n
                                  4. <\/b> To configure NTP synchronization<\/span><\/li>\n<\/ol>\n

                                    Correct Answer: 3. To define the application or destination that FortiWeb is responsible for protecting<\/b><\/p>\n

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

                                    Protected-host or protected-application configuration identifies the web service for which FortiWeb should apply security and traffic-processing policies. In a reverse-proxy deployment, this information helps FortiWeb associate incoming client requests with the appropriate virtual server, backend server pool, and web protection settings. It is therefore a key component of defining the application security boundary. Administrator accounts, boot partitions, and NTP synchronization serve unrelated system-management functions. Accurate protected-host configuration is important because a mismatch between the requested hostname, virtual server, and application configuration can result in traffic being processed by an unintended policy or not being protected as expected.<\/span><\/p>\n

                                    Question 338. Which feature can help limit excessive request rates from a client or application endpoint?<\/b><\/p>\n

                                      \n
                                    1. <\/b> Rate limiting<\/span><\/li>\n
                                    2. <\/b> Configuration backup<\/span><\/li>\n
                                    3. <\/b> Certificate import<\/span><\/li>\n
                                    4. <\/b> Administrator GUI customization<\/span><\/li>\n<\/ol>\n

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

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

                                      Rate limiting restricts how frequently requests can be accepted from a defined client, source, application, or other matching condition. It can help control excessive traffic and reduce the impact of abusive or unusually high request rates. Rate limiting is useful as part of application availability protection, particularly when an endpoint is vulnerable to request floods or automated abuse. Configuration backups, certificate imports, and GUI customization do not control the rate of HTTP requests. Administrators should configure limits according to normal application traffic because excessively restrictive thresholds can affect legitimate users and create unnecessary service disruptions.<\/span><\/p>\n

                                      Question 339. What is the primary purpose of backing up a FortiWeb configuration before making major changes?<\/b><\/p>\n

                                        \n
                                      1. <\/b> To increase web application throughput<\/span><\/li>\n
                                      2. <\/b> To disable WAF signatures<\/span><\/li>\n
                                      3. <\/b> To replace server-pool health checks<\/span><\/li>\n
                                      4. <\/b> To provide a recovery point if the configuration change causes problems<\/span><\/li>\n<\/ol>\n

                                        Correct Answer: 4. To provide a recovery point if the configuration change causes problems<\/b><\/p>\n

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

                                        A configuration backup preserves the current FortiWeb settings so administrators can restore a known configuration if a major change produces unexpected results. This is especially valuable before firmware upgrades, significant policy modifications, topology changes, or other maintenance activities. A backup does not increase application throughput or disable WAF signatures, and it does not replace backend health checks. Administrators should store backups securely and ensure that the backup corresponds to the appropriate FortiWeb version and configuration state. Maintaining reliable recovery points reduces the operational risk associated with significant configuration changes.<\/span><\/p>\n

                                        Question 340. In a high-availability FortiWeb deployment, why is configuration synchronization important?<\/b><\/p>\n

                                          \n
                                        1. <\/b> It forces all clients to use HTTP instead of HTTPS<\/span><\/li>\n
                                        2. <\/b> It ensures relevant configuration information is consistent between HA members<\/span><\/li>\n
                                        3. <\/b> It disables failover between appliances<\/span><\/li>\n
                                        4. <\/b> It removes the need for backend servers<\/span><\/li>\n<\/ol>\n

                                          Correct Answer: 2. It ensures relevant configuration information is consistent between HA members<\/b><\/p>\n

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

                                          Configuration synchronization helps maintain consistent relevant settings between FortiWeb devices participating in an HA deployment. Consistency is important because a device that becomes active after failover should have the necessary policies and configuration to continue protecting the applications. Synchronization does not disable failover, remove backend servers, or change HTTPS traffic into HTTP. Administrators should also understand which configuration elements are synchronized and verify HA status after making significant changes. Proper synchronization contributes to predictable failover behavior and reduces the risk that the secondary appliance will operate with outdated or incomplete security configuration.<\/span><\/p>\n

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

                                          View Full Fortinet NSE5_FWB_AD-8.0 Exam Dumps and Practice Test Dumps   Question 321. Which FortiWeb feature allows an administrator to apply different protection settings based on the requested hostname or URL? System DNS configuration Hardware acceleration Firmware image management Web protection profile assignment Correct Answer: 4. Web protection profile assignment Explanation :- Web protection profile […]<\/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\/21653"}],"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=21653"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/21653\/revisions"}],"predecessor-version":[{"id":21654,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/21653\/revisions\/21654"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=21653"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=21653"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=21653"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}