{"id":21651,"date":"2026-09-25T06:41:35","date_gmt":"2026-09-25T06:41:35","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=21651"},"modified":"2026-09-25T06:41:35","modified_gmt":"2026-09-25T06:41:35","slug":"fortinet-nse5_fwb_ad-8-0-practice-test-questions-and-exam-dumps-part-16-q301-320","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/fortinet-nse5_fwb_ad-8-0-practice-test-questions-and-exam-dumps-part-16-q301-320\/","title":{"rendered":"Fortinet NSE5_FWB_AD-8.0 Practice Test Questions and Exam Dumps Part 16 Q301-320"},"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 301. An administrator wants FortiWeb to protect a web application from requests containing malicious SQL statements. Which security profile is primarily responsible for detecting this type of attack?<\/b><\/p>\n

    \n
  1. <\/b> WAF profile<\/span><\/li>\n
  2. <\/b> Server health profile<\/span><\/li>\n
  3. <\/b> DNS forwarding profile<\/span><\/li>\n
  4. <\/b> Traffic shaping profile<\/span><\/li>\n<\/ol>\n

    Correct Answer: 1. WAF profile<\/b><\/p>\n

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

    A Web Application Firewall profile provides application-layer security controls for detecting and blocking attacks such as SQL injection. SQL injection attempts to manipulate database queries by inserting malicious SQL syntax into application inputs. FortiWeb can inspect HTTP or HTTPS requests and compare application parameters against configured security rules and signatures. A server health profile is concerned with backend availability, DNS forwarding handles name resolution, and traffic shaping controls traffic behavior rather than specifically identifying SQL injection. A WAF profile should therefore be associated with the appropriate FortiWeb server policy when the objective is to inspect application requests for SQL injection and other common web attacks.<\/span><\/p>\n

    Question 302. A FortiWeb administrator wants to prevent clients from directly accessing a backend server and require all application traffic to pass through FortiWeb. Which deployment design best satisfies this requirement?<\/b><\/p>\n

      \n
    1. <\/b> Offline monitoring<\/span><\/li>\n
    2. <\/b> Reverse proxy<\/span><\/li>\n
    3. <\/b> DNS-only deployment<\/span><\/li>\n
    4. <\/b> Passive packet capture<\/span><\/li>\n<\/ol>\n

      Correct Answer: 2. Reverse proxy<\/b><\/p>\n

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

      A reverse-proxy deployment places FortiWeb between clients and backend applications so that clients communicate with FortiWeb rather than directly with the protected servers. FortiWeb can then inspect, authenticate, filter, and forward application traffic according to configured policies. This architecture also allows the administrator to publish applications through virtual servers while keeping backend resources behind the security appliance. Offline monitoring and passive packet capture can provide visibility but do not force application traffic through FortiWeb for enforcement. A DNS-only deployment does not provide inline application inspection. Reverse proxy mode therefore directly satisfies the requirement for centralized application traffic enforcement.<\/span><\/p>\n

      Question 303. Which FortiWeb component identifies the frontend address and port on which clients connect to a published web application?<\/b><\/p>\n

        \n
      1. <\/b> Real server<\/span><\/li>\n
      2. <\/b> Server pool<\/span><\/li>\n
      3. <\/b> Virtual server<\/span><\/li>\n
      4. <\/b> Health-check object<\/span><\/li>\n<\/ol>\n

        Correct Answer: 3. Virtual server<\/b><\/p>\n

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

        A virtual server represents the frontend application endpoint exposed by FortiWeb. It defines the address and service information through which clients access a protected application and provides the frontend context for processing incoming connections. Real servers represent backend application systems, while a server pool groups backend servers for traffic distribution. Health-check objects determine whether backend servers are available. Understanding the distinction between frontend and backend objects is important when configuring FortiWeb. When an administrator needs to define the listener that clients use to access a published application, the virtual server is the appropriate configuration object.<\/span><\/p>\n

        Question 304. A web application has several backend servers, and the administrator wants requests to be distributed according to the configured load-balancing method. Which FortiWeb function performs this task?<\/b><\/p>\n

          \n
        1. <\/b> Load balancing<\/span><\/li>\n
        2. <\/b> Certificate validation<\/span><\/li>\n
        3. <\/b> IP reputation<\/span><\/li>\n
        4. <\/b> API discovery<\/span><\/li>\n<\/ol>\n

          Correct Answer: 1. Load balancing<\/b><\/p>\n

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

          Load balancing distributes application requests across multiple backend servers according to the selected algorithm and server availability. FortiWeb can use server pools containing real servers and apply load-balancing behavior to distribute traffic while considering server health. This can improve application scalability and availability by preventing all requests from being directed to a single backend server. Certificate validation verifies TLS certificates, IP reputation evaluates source-address reputation, and API discovery identifies API endpoints. These features do not distribute application traffic. Load balancing is therefore the FortiWeb function responsible for distributing requests among eligible backend servers.<\/span><\/p>\n

          Question 305. An administrator wants to block requests that contain a specific malicious pattern regardless of which URL receives the request. Which WAF capability is most appropriate?<\/b><\/p>\n

            \n
          1. <\/b> Signature-based detection<\/span><\/li>\n
          2. <\/b> Session persistence<\/span><\/li>\n
          3. <\/b> Server health checking<\/span><\/li>\n
          4. <\/b> DNS caching<\/span><\/li>\n<\/ol>\n

            Correct Answer: 1. Signature-based detection<\/b><\/p>\n

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

            Signature-based detection uses predefined patterns to identify known attack techniques in application traffic. This approach is effective for recognizing established threats such as common injection attacks, cross-site scripting attempts, and other malicious request patterns. FortiWeb WAF signatures can be applied through appropriate security profiles and policies. Session persistence controls backend affinity, server health checking determines whether backend servers are available, and DNS caching improves name-resolution performance. When the requirement is to detect a known malicious pattern independently of the specific URL being requested, signature-based WAF detection is the most relevant mechanism.<\/span><\/p>\n

            Question 306. A company wants FortiWeb to restrict access to a sensitive URL based on the source IP address. Which security control should the administrator configure?<\/b><\/p>\n

              \n
            1. <\/b> IP access control<\/span><\/li>\n
            2. <\/b> Web caching<\/span><\/li>\n
            3. <\/b> SSL offloading<\/span><\/li>\n
            4. <\/b> Session persistence<\/span><\/li>\n<\/ol>\n

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

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

              IP access control can restrict or permit requests according to their source IP addresses or networks. This is useful when sensitive application resources should only be accessible from trusted corporate networks or explicitly approved addresses. FortiWeb can use access-control rules to enforce these restrictions before requests are allowed to proceed to the protected application. Web caching stores eligible content, SSL offloading handles TLS termination, and session persistence maintains client affinity to backend servers. None of those directly determines whether a request’s source address is permitted to access a particular protected resource. IP access control is therefore the appropriate mechanism.<\/span><\/p>\n

              Question 307. Which FortiWeb capability is specifically designed to identify and control malicious automated web clients?<\/b><\/p>\n

                \n
              1. <\/b> Bot mitigation<\/span><\/li>\n
              2. <\/b> Certificate management<\/span><\/li>\n
              3. <\/b> Static routing<\/span><\/li>\n
              4. <\/b> Server synchronization<\/span><\/li>\n<\/ol>\n

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

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

                Bot mitigation provides controls for identifying and managing automated clients that interact with protected web applications. Malicious bots can perform activities such as credential stuffing, scraping, automated account creation, inventory abuse, and high-volume request generation. FortiWeb can use bot-related detection mechanisms to distinguish suspicious automation from legitimate users and apply configured actions. Certificate management is responsible for cryptographic credentials, static routing controls network forwarding, and server synchronization relates to maintaining information between systems or HA members. Bot mitigation is therefore the FortiWeb security capability most directly associated with identifying and controlling malicious automated web clients.<\/span><\/p>\n

                Question 308. A FortiWeb administrator wants to preserve HTTPS encryption between FortiWeb and a backend application after inspecting the client’s HTTPS request. What should be configured?<\/b><\/p>\n

                  \n
                1. <\/b> Server-side TLS<\/span><\/li>\n
                2. <\/b> DNS forwarding<\/span><\/li>\n
                3. <\/b> URL rewriting only<\/span><\/li>\n
                4. <\/b> HTTP-only backend communication<\/span><\/li>\n<\/ol>\n

                  Correct Answer: 1. Server-side TLS<\/b><\/p>\n

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

                  Server-side TLS allows FortiWeb to establish an encrypted connection to the backend application after processing the client-side connection. In this architecture, FortiWeb can terminate the client TLS session, inspect the decrypted HTTP traffic using its security controls, and then establish another TLS session toward the backend. This provides encryption on the internal application segment as well as the client-facing segment. DNS forwarding does not encrypt application traffic, URL rewriting changes URL information, and HTTP-only backend communication would not preserve encryption between FortiWeb and the backend. Server-side TLS is therefore required when backend communication must remain encrypted.<\/span><\/p>\n

                  Question 309. Which FortiWeb feature allows an administrator to inspect API requests against an expected definition of available methods, paths, and parameters?<\/b><\/p>\n

                    \n
                  1. <\/b> API protection<\/span><\/li>\n
                  2. <\/b> DNS caching<\/span><\/li>\n
                  3. <\/b> IP persistence<\/span><\/li>\n
                  4. <\/b> Certificate enrollment<\/span><\/li>\n<\/ol>\n

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

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

                    API protection provides controls specifically designed for securing application programming interfaces. API security can include validating requests against expected API behavior, controlling methods and paths, and applying protections to API parameters and payloads. This is important because APIs expose structured application functionality and can have different security requirements from traditional browser-based web pages. DNS caching improves name-resolution performance, IP persistence maintains client affinity, and certificate enrollment manages certificates. API protection is therefore the appropriate FortiWeb capability when administrators need to inspect and enforce security requirements for defined API methods, endpoints, parameters, or payloads.<\/span><\/p>\n

                    Question 310. A backend application server becomes unavailable while FortiWeb is distributing requests across a server pool. What configuration allows FortiWeb to recognize the failure and stop sending new requests to that server?<\/b><\/p>\n

                      \n
                    1. <\/b> Health check<\/span><\/li>\n
                    2. <\/b> URL rewrite rule<\/span><\/li>\n
                    3. <\/b> WAF exception<\/span><\/li>\n
                    4. <\/b> Authentication policy<\/span><\/li>\n<\/ol>\n

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

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

                      A health check periodically tests backend servers to determine whether they remain available and responsive. If a server fails the configured health-check criteria, FortiWeb can mark it unavailable and remove it from eligible load-balancing decisions until it recovers. This prevents new client requests from being directed to a failed backend application instance. URL rewrite rules modify URLs, WAF exceptions change security inspection behavior, and authentication policies control user authentication. None of these determines backend server availability. Health checks are therefore essential when FortiWeb must dynamically account for backend failures while distributing application traffic.<\/span><\/p>\n

                      Question 311. Which FortiWeb feature can enforce limits on the number of concurrent connections or requests generated by clients to help reduce resource exhaustion?<\/b><\/p>\n

                        \n
                      1. <\/b> DoS prevention<\/span><\/li>\n
                      2. <\/b> Certificate management<\/span><\/li>\n
                      3. <\/b> API discovery<\/span><\/li>\n
                      4. <\/b> URL translation<\/span><\/li>\n<\/ol>\n

                        Correct Answer: 1. DoS prevention<\/b><\/p>\n

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

                        DoS prevention provides controls intended to reduce the impact of excessive traffic and resource-exhaustion attempts against protected applications. Depending on the configured protection mechanism, FortiWeb can apply thresholds related to request rates, connections, or other traffic characteristics. These controls are useful for mitigating application-layer denial-of-service behavior where attackers attempt to consume server resources through excessive activity. Certificate management handles TLS credentials, API discovery identifies API endpoints, and URL translation modifies URL structures. DoS prevention is therefore the appropriate security function when the requirement is to limit abusive traffic and preserve application resources.<\/span><\/p>\n

                        Question 312. An administrator needs to troubleshoot a WAF event and determine the source IP, requested URL, detected attack, and action taken by FortiWeb. Where should the administrator look?<\/b><\/p>\n

                          \n
                        1. <\/b> Security logs<\/span><\/li>\n
                        2. <\/b> DNS zone configuration<\/span><\/li>\n
                        3. <\/b> Certificate request file<\/span><\/li>\n
                        4. <\/b> Backend application source code only<\/span><\/li>\n<\/ol>\n

                          Correct Answer: 1. Security logs<\/b><\/p>\n

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

                          Security logs provide the detailed event information required to investigate WAF activity. Depending on the configured logging settings, an event can contain information such as the source address, destination or requested resource, detection type, policy, action, and timestamp. These details help administrators understand why FortiWeb allowed, blocked, or otherwise processed a request. DNS zone configuration does not contain WAF enforcement details, a certificate request file contains information related to certificate issuance, and backend source code alone does not show how FortiWeb handled a specific request. Security logs are therefore the primary source for investigating individual WAF security events.<\/span><\/p>\n

                          Question 313. Which FortiWeb feature can modify an HTTP response before it is returned to the client?<\/b><\/p>\n

                            \n
                          1. <\/b> Response rewriting<\/span><\/li>\n
                          2. <\/b> Server health checking<\/span><\/li>\n
                          3. <\/b> IP reputation<\/span><\/li>\n
                          4. <\/b> API discovery<\/span><\/li>\n<\/ol>\n

                            Correct Answer: 1. Response rewriting<\/b><\/p>\n

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

                            Response rewriting allows FortiWeb to modify information contained in an HTTP response before the response reaches the client. This can be useful when application content contains URLs, headers, or other information that needs to be transformed to match the publicly exposed application structure. Server health checking monitors backend availability, IP reputation evaluates source addresses, and API discovery identifies API endpoints. These functions do not directly modify HTTP responses. Response rewriting therefore provides the appropriate mechanism when an administrator needs FortiWeb to transform response content or related HTTP information as it passes from the backend application toward the client.<\/span><\/p>\n

                            Question 314. An administrator wants to reduce the number of requests reaching a backend server by serving previously retrieved cacheable content directly from FortiWeb. Which feature should be configured?<\/b><\/p>\n

                              \n
                            1. <\/b> Web caching<\/span><\/li>\n
                            2. <\/b> Bot detection<\/span><\/li>\n
                            3. <\/b> API schema validation<\/span><\/li>\n
                            4. <\/b> IP reputation<\/span><\/li>\n<\/ol>\n

                              Correct Answer: 1. Web caching<\/b><\/p>\n

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

                              Web caching allows FortiWeb to retain eligible application responses and serve them directly to subsequent clients when the cached response can be reused. This reduces repeated requests to backend servers and can improve response performance for appropriate content. Caching is particularly useful for static or otherwise cacheable resources that do not need to be regenerated for every request. Bot detection identifies automated clients, API schema validation checks API request structures, and IP reputation evaluates source-address trust. These features do not provide content caching. Web caching is therefore the appropriate application-delivery feature for reducing backend workload through reusable responses.<\/span><\/p>\n

                              Question 315. A security administrator wants to ensure that a protected application only accepts HTTP methods that have been explicitly approved. Which security mechanism should be used?<\/b><\/p>\n

                                \n
                              1. <\/b> HTTP method restriction<\/span><\/li>\n
                              2. <\/b> DNS forwarding<\/span><\/li>\n
                              3. <\/b> Server pool persistence<\/span><\/li>\n
                              4. <\/b> Certificate renewal<\/span><\/li>\n<\/ol>\n

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

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

                                HTTP method restriction allows administrators to control which HTTP methods a protected application accepts. If an application only requires methods such as GET and POST, restricting unnecessary methods can reduce the application’s attack surface and prevent unexpected request types from reaching the backend. This type of control is particularly useful for APIs and web applications with clearly defined HTTP behavior. DNS forwarding handles name resolution, server pool persistence concerns backend selection, and certificate renewal manages certificate lifecycle operations. HTTP method restriction therefore directly addresses the requirement to permit only explicitly approved HTTP request methods.<\/span><\/p>\n

                                Question 316. Which FortiWeb capability is useful for protecting an application from attackers who repeatedly submit login attempts using many stolen username and password combinations?<\/b><\/p>\n

                                  \n
                                1. <\/b> Credential-stuffing protection and bot mitigation<\/span><\/li>\n
                                2. <\/b> Static route redistribution<\/span><\/li>\n
                                3. <\/b> Certificate chain generation<\/span><\/li>\n
                                4. <\/b> Backend content caching<\/span><\/li>\n<\/ol>\n

                                  Correct Answer: 1. Credential-stuffing protection and bot mitigation<\/b><\/p>\n

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

                                  Credential stuffing involves automated attempts to authenticate using credentials obtained from other sources. Bot mitigation and related authentication-abuse controls can help detect and limit automated login activity by evaluating request behavior and applying appropriate thresholds or challenges. These protections are particularly important on login endpoints because successful credential stuffing can result in account compromise. Static route redistribution affects network routing, certificate chain generation concerns TLS certificates, and backend content caching improves application performance. Credential-stuffing protection combined with bot mitigation therefore provides a security approach specifically suited to detecting and controlling automated authentication abuse.<\/span><\/p>\n

                                  Question 317. An administrator needs to restrict a specific application URL to authenticated users while allowing public access to other URLs on the same site. Which FortiWeb capability is most appropriate?<\/b><\/p>\n

                                    \n
                                  1. <\/b> URL-based authentication policy<\/span><\/li>\n
                                  2. <\/b> Global DNS cache<\/span><\/li>\n
                                  3. <\/b> Interface bonding<\/span><\/li>\n
                                  4. <\/b> Server health check<\/span><\/li>\n<\/ol>\n

                                    Correct Answer: 1. URL-based authentication policy<\/b><\/p>\n

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

                                    A URL-based authentication policy can apply authentication requirements to selected application resources while leaving other resources publicly accessible. This is useful when only sensitive areas, such as administrative portals or account-management pages, require authenticated access. The policy can be associated with the relevant protected application and URL conditions so that FortiWeb requests authentication when users attempt to access the specified resource. DNS caching does not provide authentication control, interface bonding combines network interfaces, and server health checks monitor backend availability. A URL-based authentication policy therefore provides the application-layer access control required for selectively protecting specific URLs.<\/span><\/p>\n

                                    Question 318. Which FortiWeb capability provides centralized visibility into application security events and can forward logs to an external logging system when configured?<\/b><\/p>\n

                                      \n
                                    1. <\/b> Logging and log forwarding<\/span><\/li>\n
                                    2. <\/b> URL rewriting<\/span><\/li>\n
                                    3. <\/b> Session persistence<\/span><\/li>\n
                                    4. <\/b> Server pool selection<\/span><\/li>\n<\/ol>\n

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

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

                                      FortiWeb logging records security and operational events generated by the appliance. When external log forwarding is configured, relevant events can be sent to a centralized logging or security-monitoring system for retention, correlation, alerting, and investigation. Centralized logging is especially useful in larger environments where administrators need to correlate web application security events with activity from other infrastructure and security products. URL rewriting modifies URLs, session persistence maintains client-to-backend affinity, and server pool selection determines backend destinations. Logging and log forwarding therefore provide the visibility and integration needed for centralized analysis of FortiWeb security events.<\/span><\/p>\n

                                      Question 319. A FortiWeb administrator wants to identify whether a request violates the expected structure of an API before allowing it to reach the backend. Which approach is most appropriate?<\/b><\/p>\n

                                        \n
                                      1. <\/b> API schema validation<\/span><\/li>\n
                                      2. <\/b> DNS forwarding<\/span><\/li>\n
                                      3. <\/b> Web caching<\/span><\/li>\n
                                      4. <\/b> IP route redistribution<\/span><\/li>\n<\/ol>\n

                                        Correct Answer: 1. API schema validation<\/b><\/p>\n

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

                                        API schema validation compares API requests against an expected definition of the API’s structure and behavior. This can include expected paths, methods, parameters, data types, and payload structures. Requests that do not conform to the defined schema can be identified and handled according to the configured policy. This provides an important layer of protection against malformed or unexpected API requests. DNS forwarding resolves domain names, web caching stores eligible application content, and IP route redistribution concerns network routing. API schema validation is therefore the most appropriate mechanism when FortiWeb must determine whether an API request conforms to the expected application interface.<\/span><\/p>\n

                                        Question 320. An organization wants to deploy two FortiWeb appliances so that one can continue protecting applications if the other experiences a failure. Which design principle should guide the deployment?<\/b><\/p>\n

                                          \n
                                        1. <\/b> High-availability redundancy<\/span><\/li>\n
                                        2. <\/b> Single-device isolation<\/span><\/li>\n
                                        3. <\/b> Offline-only inspection<\/span><\/li>\n
                                        4. <\/b> DNS caching without failover<\/span><\/li>\n<\/ol>\n

                                          Correct Answer: 1. High-availability redundancy<\/b><\/p>\n

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

                                          High-availability redundancy uses multiple FortiWeb appliances to provide continued service when an individual appliance fails. The HA configuration determines device roles, synchronization behavior, monitoring, and failover operation. Proper HA design should also account for network connectivity, traffic paths, state requirements, and the failure scenarios the organization needs to tolerate. Single-device isolation provides no appliance-level redundancy, offline inspection does not provide inline failover, and DNS caching alone cannot replace application-security appliance redundancy. High availability is therefore the appropriate design principle when an organization requires continued FortiWeb protection and application delivery following the failure of one appliance.<\/span><\/p>\n

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

                                          View Full Fortinet NSE5_FWB_AD-8.0 Exam Dumps and Practice Test Dumps   Question 301. An administrator wants FortiWeb to protect a web application from requests containing malicious SQL statements. Which security profile is primarily responsible for detecting this type of attack? WAF profile Server health profile DNS forwarding profile Traffic shaping profile Correct Answer: 1. WAF […]<\/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\/21651"}],"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=21651"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/21651\/revisions"}],"predecessor-version":[{"id":21652,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/21651\/revisions\/21652"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=21651"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=21651"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=21651"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}