{"id":21673,"date":"2026-09-25T06:49:51","date_gmt":"2026-09-25T06:49:51","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=21673"},"modified":"2026-09-25T06:49:51","modified_gmt":"2026-09-25T06:49:51","slug":"splunk-splk-5002-practice-test-questions-and-exam-dumps-part-7-q121-140","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/splunk-splk-5002-practice-test-questions-and-exam-dumps-part-7-q121-140\/","title":{"rendered":"Splunk SPLK-5002 Practice Test Questions and Exam Dumps Part 7 Q121-140"},"content":{"rendered":"

View Full <\/b>Splunk SPLK-5002 Exam Dumps<\/b><\/a> and Practice Test Dumps<\/b><\/h2>\n

 <\/p>\n

Question 121: Which SPL command can be used to calculate the sum of <\/b>bytes<\/b> for each <\/b>host<\/b>?<\/b><\/p>\n

    \n
  1. <\/b> stats total(bytes) by host<\/span><\/li>\n
  2. <\/b> stats sum(bytes) by host<\/span><\/li>\n
  3. <\/b> sum bytes by host<\/span><\/li>\n
  4. <\/b> stats add(bytes) by host<\/span><\/li>\n<\/ol>\n

    Correct Answer: 2. <\/b>stats sum(bytes) by host<\/b><\/p>\n

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

    The <\/span>stats sum(bytes) by host<\/span> command calculates the total value of the <\/span>bytes<\/span> field separately for each host. The <\/span>sum()<\/span> statistical function adds the numeric values, while the <\/span>by host<\/span> clause creates a separate group for every host. This is useful when analyzing network traffic, storage activity, or application data volumes. The other choices use invalid statistical functions or incorrect SPL syntax. <\/span>stats<\/span> can perform multiple calculations in the same search, so additional metrics such as <\/span>count<\/span> or <\/span>avg(bytes)<\/span> can also be included when a broader summary is required.<\/span><\/p>\n

    Question 122: Which SPL command can remove duplicate events based on both <\/b>host<\/b> and <\/b>user<\/b>?<\/b><\/p>\n

      \n
    1. <\/b> dedup host,user<\/span><\/li>\n
    2. <\/b> unique host,user<\/span><\/li>\n
    3. <\/b> deduplicate host and user<\/span><\/li>\n
    4. <\/b> remove duplicates host,user<\/span><\/li>\n<\/ol>\n

      Correct Answer: 1. <\/b>dedup host,user<\/b><\/p>\n

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

      The <\/span>dedup<\/span> command removes duplicate search results based on the values of specified fields. Using <\/span>dedup host,user<\/span> means Splunk considers the combination of <\/span>host<\/span> and <\/span>user<\/span> when determining duplicates. One result is retained for each unique combination encountered. This can be useful when the same user appears repeatedly on the same host and only one representative event is required. The other choices are not standard SPL syntax. Because <\/span>dedup<\/span> keeps the first matching result, the current ordering of events can affect which event remains in the final results.<\/span><\/p>\n

      Question 123: Which SPL command can create a new field containing the result of adding two numeric fields?<\/b><\/p>\n

        \n
      1. <\/b> calculate total=field1+field2<\/span><\/li>\n
      2. <\/b> stats total=field1+field2<\/span><\/li>\n
      3. <\/b> eval total=field1+field2<\/span><\/li>\n
      4. <\/b> add total=field1+field2<\/span><\/li>\n<\/ol>\n

        Correct Answer: 3. <\/b>eval total=field1+field2<\/b><\/p>\n

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

        The <\/span>eval<\/span> command is used to create or modify fields using expressions. <\/span>eval total=field1+field2<\/span> creates a new field called <\/span>total<\/span> containing the sum of the two numeric fields. This is useful for deriving values that are not directly present in the original events, such as combining inbound and outbound traffic or calculating a total duration. <\/span>stats<\/span> is designed for aggregation rather than event-level field creation. The other commands are not valid SPL syntax for this operation. <\/span>eval<\/span> also supports conditional logic, string functions, mathematical operations, and many other expressions.<\/span><\/p>\n

        Question 124: Which SPL command can display the number of events over time with five-minute intervals?<\/b><\/p>\n

          \n
        1. <\/b> timechart span=5m count<\/span><\/li>\n
        2. <\/b> timechart interval=5m events<\/span><\/li>\n
        3. <\/b> chart time=5m count<\/span><\/li>\n
        4. <\/b> timebucket count span=5m<\/span><\/li>\n<\/ol>\n

          Correct Answer: 1. <\/b>timechart span=5m count<\/b><\/p>\n

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

          The <\/span>timechart<\/span> command creates time-based statistical results, and the <\/span>span<\/span> argument controls the size of each time bucket. Therefore, <\/span>timechart span=5m count<\/span> counts events in five-minute intervals. This is useful for identifying traffic spikes, changes in activity, and recurring patterns. The <\/span>_time<\/span> field provides the time dimension used by <\/span>timechart<\/span>. The other choices use incorrect command or argument syntax. Choosing an appropriate span is important because very small intervals can produce noisy results, while very large intervals may hide short-lived changes in activity.<\/span><\/p>\n

          Question 125: Which SPL command can extract an IP address from the <\/b>_raw<\/b> field using a named capture group?<\/b><\/p>\n

            \n
          1. <\/b> regex _raw “(?<ip>\\d+\\.\\d+\\.\\d+\\.\\d+)”<\/span><\/li>\n
          2. <\/b> rex field=_raw “(?<ip>\\d+\\.\\d+\\.\\d+\\.\\d+)”<\/span><\/li>\n
          3. <\/b> extract field=_raw “(?<ip>\\d+\\.\\d+\\.\\d+\\.\\d+)”<\/span><\/li>\n
          4. <\/b> capture field=_raw ip<\/span><\/li>\n<\/ol>\n

            Correct Answer: 2. <\/b>rex field=_raw “(?<ip>\\d+\\.\\d+\\.\\d+\\.\\d+)”<\/b><\/p>\n

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

            The <\/span>rex<\/span> command can use a regular expression with a named capture group to extract information into a new field. In this example, the named group <\/span>(?<ip>…)<\/span> creates an <\/span>ip<\/span> field containing the matched IPv4 address. The <\/span>regex<\/span> command is primarily used to filter events rather than create extracted fields. <\/span>rex<\/span> is therefore the appropriate choice when the goal is extraction. In real-world searches, a more comprehensive IP pattern may be required depending on the data. Regular-expression extraction is particularly useful when important fields exist only inside unstructured raw event text.<\/span><\/p>\n

            Question 126: Which SPL command can return events where the <\/b>user<\/b> field exists?<\/b><\/p>\n

              \n
            1. <\/b> where user<\/span><\/li>\n
            2. <\/b> search user=*<\/span><\/li>\n
            3. <\/b> exists user<\/span><\/li>\n
            4. <\/b> fieldexists user<\/span><\/li>\n<\/ol>\n

              Correct Answer: 2. <\/b>search user=*<\/b><\/p>\n

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

              The <\/span>search user=*<\/span> expression matches events where the <\/span>user<\/span> field has a value. This is a common SPL technique for filtering events based on field existence. It can be useful when some events contain a particular field while others do not. <\/span>where<\/span> requires a valid expression, and simply specifying <\/span>user<\/span> is not the standard way to test field existence there. The other commands are not standard SPL syntax for this operation. Field-existence filtering is especially useful when working with heterogeneous event data from multiple sourcetypes or applications.<\/span><\/p>\n

              Question 127: Which SPL command can calculate the minimum and maximum values of <\/b>duration<\/b> for each application?<\/b><\/p>\n

                \n
              1. <\/b> stats min(duration), max(duration) by application<\/span><\/li>\n
              2. <\/b> stats range(duration) by application<\/span><\/li>\n
              3. <\/b> stats low(duration), high(duration) by application<\/span><\/li>\n
              4. <\/b> minmax duration by application<\/span><\/li>\n<\/ol>\n

                Correct Answer: 1. <\/b>stats min(duration), max(duration) by application<\/b><\/p>\n

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

                The <\/span>stats<\/span> command supports multiple statistical functions in one search. <\/span>min(duration)<\/span> identifies the lowest duration and <\/span>max(duration)<\/span> identifies the highest duration. Adding <\/span>by application<\/span> produces separate minimum and maximum values for each application. This can help identify the performance range of different applications. The other choices either use nonstandard function names or do not provide the requested pair of metrics. Statistical summaries such as minimum, maximum, average, and percentile values can be combined to provide a more complete view of application performance.<\/span><\/p>\n

                Question 128: Which SPL command can count events and group them by both <\/b>action<\/b> and <\/b>user<\/b>?<\/b><\/p>\n

                  \n
                1. <\/b> stats count action,user<\/span><\/li>\n
                2. <\/b> stats count by action,user<\/span><\/li>\n
                3. <\/b> count events by action,user<\/span><\/li>\n
                4. <\/b> eventstats action,user count<\/span><\/li>\n<\/ol>\n

                  Correct Answer: 2. <\/b>stats count by action,user<\/b><\/p>\n

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

                  The <\/span>stats count by action,user<\/span> command counts matching events for each unique combination of <\/span>action<\/span> and <\/span>user<\/span>. For example, it can show how many login, logout, download, or update actions were performed by each user. The <\/span>count<\/span> function counts events, while the <\/span>by<\/span> clause defines the grouping dimensions. The other choices use invalid or incomplete SPL syntax. Grouping by multiple fields is useful when analyzing relationships between two dimensions, especially when a simple count by only one field would not provide enough context.<\/span><\/p>\n

                  Question 129: Which SPL command can calculate a distinct count of users for each host?<\/b><\/p>\n

                    \n
                  1. <\/b> stats count(user) by host<\/span><\/li>\n
                  2. <\/b> stats unique(user) by host<\/span><\/li>\n
                  3. <\/b> stats dc(user) by host<\/span><\/li>\n
                  4. <\/b> stats users(user) by host<\/span><\/li>\n<\/ol>\n

                    Correct Answer: 3. <\/b>stats dc(user) by host<\/b><\/p>\n

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

                    The <\/span>dc()<\/span> function calculates the distinct count of a field. Therefore, <\/span>stats dc(user) by host<\/span> returns the number of unique users associated with each host. This is different from <\/span>count(user)<\/span>, which counts events containing the user field and can count the same user multiple times. Distinct counts are useful when measuring unique identities, devices, IP addresses, or sessions. The <\/span>by host<\/span> clause ensures that the calculation is performed separately for each host. This type of search is commonly used for access analysis and identifying systems accessed by many different users.<\/span><\/p>\n

                    Question 130: Which SPL command can sort results by <\/b>host<\/b> in ascending order?<\/b><\/p>\n

                      \n
                    1. <\/b> sort host<\/span><\/li>\n
                    2. <\/b> sort -host<\/span><\/li>\n
                    3. <\/b> orderby host ascending<\/span><\/li>\n
                    4. <\/b> sort +host descending<\/span><\/li>\n<\/ol>\n

                      Correct Answer: 1. <\/b>sort host<\/b><\/p>\n

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

                      The <\/span>sort<\/span> command orders search results according to one or more fields. By default, specifying <\/span>sort host<\/span> sorts the results by <\/span>host<\/span> in ascending order. A minus sign, such as <\/span>sort -host<\/span>, requests descending order. Sorting is useful when organizing results alphabetically, numerically, or chronologically before displaying or processing them. The other choices either reverse the requested order or use invalid syntax. When sorting numeric values, users should also consider the data type and field contents to ensure the resulting order represents the intended comparison.<\/span><\/p>\n

                      Question 131: Which SPL command can calculate the average, minimum, and maximum <\/b>response_time<\/b> for each <\/b>host<\/b>?<\/b><\/p>\n

                        \n
                      1. <\/b> stats avg(response_time), min(response_time), max(response_time) by host<\/span><\/li>\n
                      2. <\/b> stats performance(response_time) by host<\/span><\/li>\n
                      3. <\/b> stats average,min,max response_time by host<\/span><\/li>\n
                      4. <\/b> calculate avg min max response_time by host<\/span><\/li>\n<\/ol>\n

                        Correct Answer: 1. <\/b>stats avg(response_time), min(response_time), max(response_time) by host<\/b><\/p>\n

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

                        The <\/span>stats<\/span> command can calculate multiple statistical measures simultaneously. In this search, <\/span>avg(response_time)<\/span> provides the average, <\/span>min(response_time)<\/span> provides the lowest value, and <\/span>max(response_time)<\/span> provides the highest value for each host. The <\/span>by host<\/span> clause creates a separate set of statistics for each host. This combination is useful for comparing performance across systems and understanding both typical and extreme response times. The other choices do not use valid SPL statistical syntax. Multiple aggregations can also be given aliases to make the resulting field names easier to interpret.<\/span><\/p>\n

                        Question 132: Which SPL command can filter results after <\/b>stats count by host<\/b> to show only hosts with more than 100 events?<\/b><\/p>\n

                          \n
                        1. <\/b> where count > 100<\/span><\/li>\n
                        2. <\/b> search events > 100<\/span><\/li>\n
                        3. <\/b> filter count greater 100<\/span><\/li>\n
                        4. <\/b> having count > 100<\/span><\/li>\n<\/ol>\n

                          Correct Answer: 1. <\/b>where count > 100<\/b><\/p>\n

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

                          After <\/span>stats count by host<\/span>, the resulting rows contain a <\/span>count<\/span> field. The <\/span>where<\/span> command can then evaluate that calculated field and retain only rows where <\/span>count<\/span> is greater than 100. A complete search can therefore be written as <\/span>stats count by host | where count > 100<\/span>. This technique is useful for threshold-based reporting and identifying high-volume hosts. The other choices either use invalid SPL syntax or commands that are not standard for filtering statistical results. <\/span>where<\/span> is especially useful when the field being tested was created by an earlier command.<\/span><\/p>\n

                          Question 133: Which SPL command can add a sequential row number to events as they are processed?<\/b><\/p>\n

                            \n
                          1. <\/b> stats count<\/span><\/li>\n
                          2. <\/b> eventstats count<\/span><\/li>\n
                          3. <\/b> streamstats count<\/span><\/li>\n
                          4. <\/b> rowcount<\/span><\/li>\n<\/ol>\n

                            Correct Answer: 3. <\/b>streamstats count<\/b><\/p>\n

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

                            The <\/span>streamstats<\/span> command can calculate a running count as events are processed. A search such as <\/span>streamstats count as row_number<\/span> creates a sequential count that can serve as a row number for the current result order. Unlike <\/span>stats<\/span>, which summarizes all events into aggregate results, <\/span>streamstats<\/span> preserves the individual events while adding the running calculation. This can be useful when analyzing event sequences or identifying the position of events within a result set. The final numbering depends on the order in which Splunk processes the search results.<\/span><\/p>\n

                            Question 134: Which SPL command can display only events from the <\/b>authentication<\/b> sourcetype?<\/b><\/p>\n

                              \n
                            1. <\/b> source=authentication<\/span><\/li>\n
                            2. <\/b> sourcetype=authentication<\/span><\/li>\n
                            3. <\/b> type=authentication<\/span><\/li>\n
                            4. <\/b> eventtype=authentication<\/span><\/li>\n<\/ol>\n

                              Correct Answer: 2. <\/b>sourcetype=authentication<\/b><\/p>\n

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

                              The <\/span>sourcetype<\/span> field identifies the type of data associated with an event in Splunk. Searching for <\/span>sourcetype=authentication<\/span> returns events whose sourcetype matches that value. Sourcetype filtering is commonly used to focus a search on a particular type of log data, such as authentication, web, firewall, or application events. <\/span>source<\/span> identifies the input source, while <\/span>eventtype<\/span> refers to a configured event type and is not interchangeable with sourcetype. Using the correct metadata field is important when narrowing searches to the intended dataset.<\/span><\/p>\n

                              Question 135: Which SPL command can retrieve the most recent 20 results from the current result set?<\/b><\/p>\n

                                \n
                              1. <\/b> head 20<\/span><\/li>\n
                              2. <\/b> tail 20<\/span><\/li>\n
                              3. <\/b> latest 20<\/span><\/li>\n
                              4. <\/b> recent 20<\/span><\/li>\n<\/ol>\n

                                Correct Answer: 2. <\/b>tail 20<\/b><\/p>\n

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

                                The <\/span>tail<\/span> command returns the last results from the current search result set. Therefore, <\/span>tail 20<\/span> returns the final 20 results in the current ordering. If the results have been ordered chronologically with the newest events at the end, this can be used to inspect the most recent events. <\/span>head 20<\/span> instead returns the first 20 results. The commands <\/span>latest<\/span> and <\/span>recent<\/span> shown here are not the standard SPL commands for limiting results in this way. Result ordering should always be considered when interpreting the output of <\/span>tail<\/span>.<\/span><\/p>\n

                                Question 136: Which SPL command can create a field that labels events as <\/b>High<\/b> when <\/b>severity<\/b> is 4 or greater and <\/b>Normal<\/b> otherwise?<\/b><\/p>\n

                                  \n
                                1. <\/b> eval priority=if(severity>=4,”High”,”Normal”)<\/span><\/li>\n
                                2. <\/b> where priority=if(severity>=4,”High”,”Normal”)<\/span><\/li>\n
                                3. <\/b> stats priority=if(severity>=4,”High”,”Normal”)<\/span><\/li>\n
                                4. <\/b> rename priority=if(severity>=4,”High”,”Normal”)<\/span><\/li>\n<\/ol>\n

                                  Correct Answer: 1. <\/b>eval priority=if(severity>=4,”High”,”Normal”)<\/b><\/p>\n

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

                                  The <\/span>eval<\/span> command can create a calculated field using the <\/span>if()<\/span> function. In this example, <\/span>priority<\/span> becomes <\/span>High<\/span> when <\/span>severity<\/span> is 4 or greater and <\/span>Normal<\/span> otherwise. Conditional field creation is useful for categorizing events, applying business logic, and simplifying later analysis. <\/span>where<\/span> is used to filter results rather than create this type of classification, while <\/span>stats<\/span> performs aggregation. <\/span>rename<\/span> changes field names and cannot perform this conditional calculation. The resulting <\/span>priority<\/span> field can then be used in later filtering, statistical analysis, or visualization.<\/span><\/p>\n

                                  Question 137: Which SPL command can extract the domain from an email address stored in the <\/b>email<\/b> field?<\/b><\/p>\n

                                    \n
                                  1. <\/b> rex field=email “@(?<domain>[^ ]+)”<\/span><\/li>\n
                                  2. <\/b> regex field=email “@(?<domain>[^ ]+)”<\/span><\/li>\n
                                  3. <\/b> extract email domain<\/span><\/li>\n
                                  4. <\/b> split email domain<\/span><\/li>\n<\/ol>\n

                                    Correct Answer: 1. <\/b>rex field=email “@(?<domain>[^ ]+)”<\/b><\/p>\n

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

                                    The <\/span>rex<\/span> command can extract a portion of a field using a regular expression and a named capture group. In this example, the pattern captures the text following <\/span>@<\/span> into a new field called <\/span>domain<\/span>. This is useful for transforming unstructured or semi-structured data into fields that can be analyzed with other SPL commands. <\/span>regex<\/span> is primarily intended for filtering events rather than creating extracted fields. The other commands do not represent the appropriate SPL syntax for this extraction task. More restrictive patterns may be appropriate when the data requires strict email-domain validation.<\/span><\/p>\n

                                    Question 138: Which SPL command can return the earliest and latest values of <\/b>_time<\/b> for the entire search result set?<\/b><\/p>\n

                                      \n
                                    1. <\/b> stats min(_time), max(_time)<\/span><\/li>\n
                                    2. <\/b> stats earliest(_time), latest(_time)<\/span><\/li>\n
                                    3. <\/b> timechart first(_time), last(_time)<\/span><\/li>\n
                                    4. <\/b> eventtime earliest latest<\/span><\/li>\n<\/ol>\n

                                      Correct Answer: 2. <\/b>stats earliest(_time), latest(_time)<\/b><\/p>\n

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

                                      The <\/span>stats<\/span> command with <\/span>earliest(_time)<\/span> and <\/span>latest(_time)<\/span> returns the earliest and latest event timestamps across the matching results. Because no <\/span>by<\/span> clause is specified, the statistics are calculated for the entire result set rather than separately for groups. This can be useful for determining the actual event-time range represented by matching data. The selected Splunk time range still determines which events are eligible for the calculation. The other choices either use less appropriate functions or invalid syntax for directly returning the earliest and latest event timestamps.<\/span><\/p>\n

                                      Question 139: Which SPL command can count events separately for each value of the <\/b>action<\/b> field and sort the results from highest count to lowest?<\/b><\/p>\n

                                        \n
                                      1. <\/b> stats count by action | sort -count<\/span><\/li>\n
                                      2. <\/b> stats action count | sort count<\/span><\/li>\n
                                      3. <\/b> count by action | descending count<\/span><\/li>\n
                                      4. <\/b> top action | sort count<\/span><\/li>\n<\/ol>\n

                                        Correct Answer: 1. <\/b>stats count by action | sort -count<\/b><\/p>\n

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

                                        The search <\/span>stats count by action | sort -count<\/span> first calculates the number of events for each distinct <\/span>action<\/span> value. The pipe then passes those summary results to <\/span>sort -count<\/span>, which orders them from the highest count to the lowest. This pattern is useful for quickly ranking activity types, such as login, download, update, or delete actions. <\/span>stats<\/span> performs the aggregation, while <\/span>sort<\/span> controls the final ordering. The other choices do not correctly combine the required aggregation and descending sort operations.<\/span><\/p>\n

                                        Question 140: Which SPL command can display a selected set of fields in a specific column order?<\/b><\/p>\n

                                          \n
                                        1. <\/b> fields user host status<\/span><\/li>\n
                                        2. <\/b> table user host status<\/span><\/li>\n
                                        3. <\/b> select user host status<\/span><\/li>\n
                                        4. <\/b> columns user host status<\/span><\/li>\n<\/ol>\n

                                          Correct Answer: 2. <\/b>table user host status<\/b><\/p>\n

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

                                          The <\/span>table<\/span> command creates a tabular result containing the specified fields in the order provided. For example, <\/span>table user host status<\/span> produces columns in the sequence <\/span>user<\/span>, <\/span>host<\/span>, and <\/span>status<\/span>. This is particularly useful for producing clean, report-ready output after filtering or aggregation. Although <\/span>fields<\/span> can control which fields are retained, <\/span>table<\/span> is specifically designed to present selected fields as columns in a defined order. The other commands are not standard SPL commands for this purpose. Using <\/span>table<\/span> near the end of a search can make final results easier to read and interpret.<\/span><\/p>\n

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

                                          View Full Splunk SPLK-5002 Exam Dumps and Practice Test Dumps   Question 121: Which SPL command can be used to calculate the sum of bytes for each host? stats total(bytes) by host stats sum(bytes) by host sum bytes by host stats add(bytes) by host Correct Answer: 2. stats sum(bytes) by host Explanation :- The stats […]<\/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\/21673"}],"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=21673"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/21673\/revisions"}],"predecessor-version":[{"id":21674,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/21673\/revisions\/21674"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=21673"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=21673"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=21673"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}