{"id":21663,"date":"2026-09-25T06:47:37","date_gmt":"2026-09-25T06:47:37","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=21663"},"modified":"2026-09-25T06:47:37","modified_gmt":"2026-09-25T06:47:37","slug":"splunk-splk-5002-practice-test-questions-and-exam-dumps-part-2-q21-40","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/splunk-splk-5002-practice-test-questions-and-exam-dumps-part-2-q21-40\/","title":{"rendered":"Splunk SPLK-5002 Practice Test Questions and Exam Dumps Part 2 Q21-40"},"content":{"rendered":"

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

 <\/p>\n

Question 21. An analyst needs to search for events from the <\/b>sales<\/b> index where the <\/b>status<\/b> field is either <\/b>success<\/b> or <\/b>pending<\/b>. Which SPL search is appropriate?<\/b><\/p>\n

    \n
  1. <\/b> index=sales status=success OR pending<\/span><\/li>\n
  2. <\/b> index=sales status IN (success,pending)<\/span><\/li>\n
  3. <\/b> index=sales (status=success OR status=pending)<\/span><\/li>\n
  4. <\/b> index=sales status=(success,pending)<\/span><\/li>\n<\/ol>\n

    Correct Answer: 3. <\/b>index=sales (status=success OR status=pending)<\/b><\/p>\n

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

    The search uses two explicit field-value conditions combined with the <\/span>OR<\/span> operator. By writing <\/span>(status=success OR status=pending)<\/span>, Splunk evaluates the alternatives as conditions against the same field. The parentheses make the intended Boolean grouping clear and prevent ambiguity when additional search conditions are included. The other examples do not represent the standard approach for expressing two alternative field values in a basic SPL search. Using explicit field comparisons is also useful for readability when constructing more complex searches. Therefore, the third search correctly returns events from the <\/span>sales<\/span> index whose status is either <\/span>success<\/span> or <\/span>pending<\/span>.<\/span><\/p>\n

    Question 22. Which SPL command is commonly used to calculate the number of distinct values of a field?<\/b><\/p>\n

      \n
    1. <\/b> stats dc(field)<\/span><\/li>\n
    2. <\/b> table distinct(field)<\/span><\/li>\n
    3. <\/b> unique field<\/span><\/li>\n
    4. <\/b> count distinct(field)<\/span><\/li>\n<\/ol>\n

      Correct Answer: 1. <\/b>stats dc(field)<\/b><\/p>\n

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

      The <\/span>dc()<\/span> statistical function used with the <\/span>stats<\/span> command calculates the distinct count of values in a field. For example, <\/span>stats dc(user)<\/span> returns the number of unique users represented in the search results. This differs from a simple <\/span>count<\/span>, which counts events or values without necessarily removing duplicates. The <\/span>table<\/span> command formats results rather than performing this statistical calculation, while <\/span>unique<\/span> and <\/span>count distinct<\/span> are not the standard SPL syntax for this operation. Therefore, <\/span>stats dc(field)<\/span> is the appropriate pattern when an analyst needs the number of distinct field values.<\/span><\/p>\n

      Question 23. An administrator wants to search only events generated by a particular host while also restricting the search to a specific index. Which search is appropriate?<\/b><\/p>\n

        \n
      1. <\/b> index=security host=server01<\/span><\/li>\n
      2. <\/b> index:security host:server01<\/span><\/li>\n
      3. <\/b> security | host server01<\/span><\/li>\n
      4. <\/b> search index security host server01<\/span><\/li>\n<\/ol>\n

        Correct Answer: 1. <\/b>index=security host=server01<\/b><\/p>\n

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

        Splunk searches can combine multiple field-value restrictions in the same search expression. <\/span>index=security host=server01<\/span> restricts the search to events in the <\/span>security<\/span> index and further limits results to events associated with <\/span>server01<\/span>. This is a common and efficient way to narrow a search before applying additional SPL commands. The other options do not use the standard field-value syntax for specifying both the index and host. Applying indexed search criteria early can also reduce the amount of data that later commands must process.<\/span><\/p>\n

        Question 24. Which SPL command can be used to calculate the earliest and latest values of a time-related field within grouped results?<\/b><\/p>\n

          \n
        1. <\/b> stats earliest(field) latest(field) by group<\/span><\/li>\n
        2. <\/b> table first(field) last(field)<\/span><\/li>\n
        3. <\/b> time range field by group<\/span><\/li>\n
        4. <\/b> sort earliest latest by group<\/span><\/li>\n<\/ol>\n

          Correct Answer: 1. <\/b>stats earliest(field) latest(field) by group<\/b><\/p>\n

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

          The <\/span>stats<\/span> command supports functions such as <\/span>earliest()<\/span> and <\/span>latest()<\/span> for determining the earliest and latest values represented by a field within the search results. Adding <\/span>by group<\/span> produces separate calculations for each value of the grouping field. This is useful when analysts need to determine the first and most recent observed values associated with different entities. The other options do not provide valid SPL syntax for this grouped statistical calculation. Therefore, <\/span>stats earliest(field) latest(field) by group<\/span> is the appropriate search pattern for this requirement.<\/span><\/p>\n

          Question 25. An analyst wants to display events in descending order based on a numeric field called <\/b>bytes<\/b>. Which SPL command should be used?<\/b><\/p>\n

            \n
          1. <\/b> sort bytes descending<\/span><\/li>\n
          2. <\/b> sort – bytes<\/span><\/li>\n
          3. <\/b> sort -bytes<\/span><\/li>\n
          4. <\/b> order bytes DESC<\/span><\/li>\n<\/ol>\n

            Correct Answer: 3. <\/b>sort -bytes<\/b><\/p>\n

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

            The <\/span>sort<\/span> command can order results according to specified fields. Prefixing a field with a minus sign requests descending order, so <\/span>sort -bytes<\/span> places larger byte values before smaller ones. This is useful when an analyst wants to identify events with the highest values first. A positive field name generally produces ascending ordering, while the other proposed syntaxes do not represent the standard SPL syntax for descending sort. Therefore, <\/span>sort -bytes<\/span> is the appropriate command when results need to be sorted from the largest <\/span>bytes<\/span> value to the smallest.<\/span><\/p>\n

            Question 26. An analyst wants to create a field named <\/b>total<\/b> by adding the values of <\/b>bytes_in<\/b> and <\/b>bytes_out<\/b>. Which SPL command should be used?<\/b><\/p>\n

              \n
            1. <\/b> eval total=bytes_in+bytes_out<\/span><\/li>\n
            2. <\/b> stats total=bytes_in+bytes_out<\/span><\/li>\n
            3. <\/b> calculate total bytes_in bytes_out<\/span><\/li>\n
            4. <\/b> field total=bytes_in+bytes_out<\/span><\/li>\n<\/ol>\n

              Correct Answer: 1. <\/b>eval total=bytes_in+bytes_out<\/b><\/p>\n

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

              The <\/span>eval<\/span> command is used to create calculated fields from existing fields and expressions. In this case, <\/span>eval total=bytes_in+bytes_out<\/span> creates a new field named <\/span>total<\/span> whose value is the sum of <\/span>bytes_in<\/span> and <\/span>bytes_out<\/span>. This calculation is performed on the applicable events as the search pipeline processes them. <\/span>stats<\/span> is intended for aggregation rather than this per-event field calculation, while the other commands shown are not valid SPL syntax for creating the requested field. Therefore, <\/span>eval<\/span> is the correct command for this calculation.<\/span><\/p>\n

              Question 27. Which SPL command can be used to filter events based on a Boolean expression involving multiple fields?<\/b><\/p>\n

                \n
              1. <\/b> table<\/span><\/li>\n
              2. <\/b> where<\/span><\/li>\n
              3. <\/b> rename<\/span><\/li>\n
              4. <\/b> fields<\/span><\/li>\n<\/ol>\n

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

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

                The <\/span>where<\/span> command evaluates an expression and keeps only the events for which that expression evaluates as true. It is particularly useful for comparisons involving multiple fields or calculated conditions. For example, an analyst could use <\/span>where bytes_out > bytes_in AND status=200<\/span> to apply multiple conditions to each event. <\/span>table<\/span> formats selected fields, <\/span>rename<\/span> changes field names, and <\/span>fields<\/span> controls field availability. Therefore, <\/span>where<\/span> is the appropriate SPL command when filtering requires a Boolean expression involving multiple fields rather than a simple search-term filter.<\/span><\/p>\n

                Question 28. An analyst wants to identify the five most common values of the <\/b>user<\/b> field. Which SPL command is most appropriate?<\/b><\/p>\n

                  \n
                1. <\/b> top limit=5 user<\/span><\/li>\n
                2. <\/b> stats count by user | head 5<\/span><\/li>\n
                3. <\/b> top 5 user<\/span><\/li>\n
                4. <\/b> sort user | head 5<\/span><\/li>\n<\/ol>\n

                  Correct Answer: 3. <\/b>top 5 user<\/b><\/p>\n

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

                  The <\/span>top<\/span> command is designed to identify the most frequently occurring values of a field. Specifying <\/span>5<\/span> limits the output to the five highest-frequency values, making <\/span>top 5 user<\/span> an appropriate search for identifying the most common users. Although aggregation with <\/span>stats<\/span> and subsequent sorting can also be used to construct frequency analyses, the <\/span>top<\/span> command directly provides this functionality. The other options either use nonstandard syntax or do not necessarily produce the intended frequency ranking. Therefore, <\/span>top 5 user<\/span> is the most direct SPL command for this requirement.<\/span><\/p>\n

                  Question 29. Which SPL command can combine the results of two searches into a single result set by appending the second search’s results?<\/b><\/p>\n

                    \n
                  1. <\/b> join<\/span><\/li>\n
                  2. <\/b> append<\/span><\/li>\n
                  3. <\/b> merge<\/span><\/li>\n
                  4. <\/b> combine<\/span><\/li>\n<\/ol>\n

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

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

                    The <\/span>append<\/span> command adds the results of a subsearch to the results produced by the main search. This is useful when an analyst needs to combine two independently generated result sets into one set of results. It differs from commands designed specifically to correlate matching fields between datasets. <\/span>join<\/span> has a different purpose and uses field-based matching, while <\/span>merge<\/span> and <\/span>combine<\/span> are not the standard SPL commands for this operation. Therefore, when the requirement is to append the results of another search to the current results, the <\/span>append<\/span> command is appropriate.<\/span><\/p>\n

                    Question 30. An analyst needs to extract an email address from raw event text using a regular expression. Which SPL command should be used?<\/b><\/p>\n

                      \n
                    1. <\/b> rex<\/span><\/li>\n
                    2. <\/b> extract_email<\/span><\/li>\n
                    3. <\/b> regex_extract<\/span><\/li>\n
                    4. <\/b> parse<\/span><\/li>\n<\/ol>\n

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

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

                      The <\/span>rex<\/span> command supports regular-expression-based extraction from event data. An analyst can use a named capture group in the regular expression to create a field containing the extracted email address. This is useful when the desired information is present in <\/span>_raw<\/span> but has not already been extracted into a structured field. The other commands listed are not the standard SPL command for regular-expression extraction. Therefore, <\/span>rex<\/span> is the correct choice when an analyst needs to identify and extract an email address or another structured value from raw event text.<\/span><\/p>\n

                      Question 31. Which field is automatically associated with the timestamp of a Splunk event?<\/b><\/p>\n

                        \n
                      1. <\/b> _host<\/span><\/li>\n
                      2. <\/b> _time<\/span><\/li>\n
                      3. <\/b> _timestamp<\/span><\/li>\n
                      4. <\/b> event_time<\/span><\/li>\n<\/ol>\n

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

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

                        Splunk uses the internal field <\/span>_time<\/span> to represent the timestamp associated with an event. It is a fundamental field for time-based searching, reporting, charting, and time bucketing. Analysts frequently use <\/span>_time<\/span> with commands and functions that organize events chronologically or divide them into time intervals. The other field names listed are not the standard internal field used by Splunk to represent an event’s timestamp. Understanding <\/span>_time<\/span> is especially important when constructing searches involving time ranges, timecharts, and commands such as <\/span>bin<\/span>.<\/span><\/p>\n

                        Question 32. An analyst wants to group events into five-minute intervals based on their event timestamps. Which SPL expression is most appropriate?<\/b><\/p>\n

                          \n
                        1. <\/b> bin _time span=5m<\/span><\/li>\n
                        2. <\/b> bucket _time every=5<\/span><\/li>\n
                        3. <\/b> group _time 5m<\/span><\/li>\n
                        4. <\/b> timebucket _time=5m<\/span><\/li>\n<\/ol>\n

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

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

                          The <\/span>bin<\/span> command can place continuous values into discrete buckets. When used with <\/span>_time<\/span>, it is commonly used to create time buckets for analysis. <\/span>bin _time span=5m<\/span> groups event timestamps into five-minute intervals, allowing subsequent commands such as <\/span>stats count by _time<\/span> to summarize activity over those intervals. The other examples do not use standard SPL syntax for time bucketing. Therefore, <\/span>bin _time span=5m<\/span> is the appropriate expression when an analyst needs to group events into five-minute timestamp intervals.<\/span><\/p>\n

                          Question 33. Which SPL command can return a statistical summary while grouping the results by two fields?<\/b><\/p>\n

                            \n
                          1. <\/b> stats count by host, sourcetype<\/span><\/li>\n
                          2. <\/b> stats group host sourcetype<\/span><\/li>\n
                          3. <\/b> summary host and sourcetype<\/span><\/li>\n
                          4. <\/b> table count host sourcetype<\/span><\/li>\n<\/ol>\n

                            Correct Answer: 1. <\/b>stats count by host, sourcetype<\/b><\/p>\n

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

                            The <\/span>stats<\/span> command supports grouping by multiple fields. <\/span>stats count by host, sourcetype<\/span> calculates event counts for each unique combination of <\/span>host<\/span> and <\/span>sourcetype<\/span>. This is useful for building multidimensional summaries, such as determining how many events each source type generates on each host. The other options do not use the standard SPL syntax for grouped statistical aggregation. Therefore, the first option is correct because it combines the <\/span>count<\/span> aggregation with a <\/span>by<\/span> clause containing two grouping fields.<\/span><\/p>\n

                            Question 34. An analyst wants to display only unique combinations of <\/b>host<\/b> and <\/b>source<\/b> in the results. Which SPL approach is appropriate?<\/b><\/p>\n

                              \n
                            1. <\/b> dedup host source<\/span><\/li>\n
                            2. <\/b> unique host source<\/span><\/li>\n
                            3. <\/b> stats unique(host,source)<\/span><\/li>\n
                            4. <\/b> distinct host source<\/span><\/li>\n<\/ol>\n

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

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

                              The <\/span>dedup<\/span> command removes duplicate results based on the fields specified. Using <\/span>dedup host source<\/span> keeps a single result for each unique combination of <\/span>host<\/span> and <\/span>source<\/span>. This is useful when an analyst wants to reduce repeated entries while retaining representative events. The other options do not use the standard SPL syntax for removing duplicate combinations of fields. Therefore, <\/span>dedup host source<\/span> is the appropriate approach when the objective is to retain unique host-and-source combinations in the search results.<\/span><\/p>\n

                              Question 35. Which SPL command is used to select or exclude fields from the results without performing statistical aggregation?<\/b><\/p>\n

                                \n
                              1. <\/b> fields<\/span><\/li>\n
                              2. <\/b> stats<\/span><\/li>\n
                              3. <\/b> eventstats<\/span><\/li>\n
                              4. <\/b> transaction<\/span><\/li>\n<\/ol>\n

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

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

                                The <\/span>fields<\/span> command controls which fields are available in the search results. It can be used to include selected fields or exclude unwanted fields, helping simplify the dataset passed through later search commands. For example, <\/span>fields host source sourcetype<\/span> keeps only those fields, while <\/span>fields – password<\/span> removes a specified field. <\/span>stats<\/span> performs aggregation, <\/span>eventstats<\/span> adds statistical information to events, and <\/span>transaction<\/span> groups related events. Therefore, <\/span>fields<\/span> is the appropriate command when the objective is simply to control field availability without performing statistical aggregation.<\/span><\/p>\n

                                Question 36. An analyst needs to add the total event count for each host to every event associated with that host. Which SPL command is appropriate?<\/b><\/p>\n

                                  \n
                                1. <\/b> stats count by host<\/span><\/li>\n
                                2. <\/b> eventstats count by host<\/span><\/li>\n
                                3. <\/b> table host count<\/span><\/li>\n
                                4. <\/b> dedup host<\/span><\/li>\n<\/ol>\n

                                  Correct Answer: 2. <\/b>eventstats count by host<\/b><\/p>\n

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

                                  The <\/span>eventstats<\/span> command calculates statistics and adds the resulting values back into the individual events. Using <\/span>eventstats count by host<\/span> calculates the number of events for each host and makes that count available as a field on the corresponding events. This differs from <\/span>stats<\/span>, which normally transforms the event stream into an aggregated result set. <\/span>table<\/span> controls displayed fields, while <\/span>dedup<\/span> removes duplicate results. Therefore, <\/span>eventstats<\/span> is the appropriate command when an analyst needs grouped statistics to remain associated with each original event.<\/span><\/p>\n

                                  Question 37. Which SPL command can calculate a running or cumulative total across search results?<\/b><\/p>\n

                                    \n
                                  1. <\/b> accum<\/span><\/li>\n
                                  2. <\/b> runningtotal<\/span><\/li>\n
                                  3. <\/b> streamstats sum(field)<\/span><\/li>\n
                                  4. <\/b> stats cumulative(field)<\/span><\/li>\n<\/ol>\n

                                    Correct Answer: 3. <\/b>streamstats sum(field)<\/b><\/p>\n

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

                                    The <\/span>streamstats<\/span> command calculates streaming statistics as events are processed. Using a function such as <\/span>sum(field)<\/span> allows an analyst to maintain a cumulative value across the result sequence. This is useful for analyzing trends, running totals, and other calculations where each result depends on preceding results. The exact output depends on the search ordering and the command configuration. The other options are not the standard SPL syntax for calculating a streaming cumulative statistic. Therefore, <\/span>streamstats sum(field)<\/span> is the appropriate command pattern for a running total.<\/span><\/p>\n

                                    Question 38. An analyst wants to replace occurrences of one value in a field with another value during search processing. Which SPL command can perform this transformation?<\/b><\/p>\n

                                      \n
                                    1. <\/b> rename<\/span><\/li>\n
                                    2. <\/b> replace<\/span><\/li>\n
                                    3. <\/b> sort<\/span><\/li>\n
                                    4. <\/b> dedup<\/span><\/li>\n<\/ol>\n

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

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

                                      The <\/span>replace<\/span> command can substitute one value for another in a specified field. This is useful when an analyst needs to normalize or transform field values during search processing without changing the original event data stored in Splunk. For example, values representing the same category with different labels can be standardized for analysis. <\/span>rename<\/span> changes field names rather than their values, <\/span>sort<\/span> orders results, and <\/span>dedup<\/span> removes duplicate events. Therefore, <\/span>replace<\/span> is the appropriate SPL command when the task requires substituting field values.<\/span><\/p>\n

                                      Question 39. Which SPL command is commonly used to correlate multiple events that share a common identifier and represent a single logical activity?<\/b><\/p>\n

                                        \n
                                      1. <\/b> transaction<\/span><\/li>\n
                                      2. <\/b> table<\/span><\/li>\n
                                      3. <\/b> rename<\/span><\/li>\n
                                      4. <\/b> fields<\/span><\/li>\n<\/ol>\n

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

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

                                        The <\/span>transaction<\/span> command groups related events into transactions based on specified identifying fields and transaction constraints. This can be useful when multiple events collectively represent one logical activity, such as a user session or application transaction. The command can consider common identifiers and timing relationships when determining which events belong together. <\/span>table<\/span> formats results, <\/span>rename<\/span> changes field names, and <\/span>fields<\/span> controls field availability. Therefore, when the objective is to correlate multiple related events into a logical transaction, the <\/span>transaction<\/span> command is an appropriate choice.<\/span><\/p>\n

                                        Question 40. An analyst wants to search for events where the <\/b>status<\/b> field exists, regardless of its specific value. Which SPL search is appropriate?<\/b><\/p>\n

                                          \n
                                        1. <\/b> status=*<\/span><\/li>\n
                                        2. <\/b> status=ANY<\/span><\/li>\n
                                        3. <\/b> exists(status)<\/span><\/li>\n
                                        4. <\/b> status=present<\/span><\/li>\n<\/ol>\n

                                          Correct Answer: 1. <\/b>status=*<\/b><\/p>\n

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

                                          In Splunk search syntax, <\/span>status=*<\/span> is commonly used to search for events where the <\/span>status<\/span> field has a value. The wildcard indicates that the field can contain any value rather than requiring a specific value such as 200 or 404. This is useful when the analyst wants to ensure that a field is present while remaining indifferent to its particular value. The other examples are not the standard SPL syntax for this basic field-existence search. Therefore, <\/span>status=*<\/span> is the appropriate search expression for finding events containing the <\/span>status<\/span> field.<\/span><\/p>\n

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

                                          View Full Splunk SPLK-5002 Exam Dumps and Practice Test Dumps   Question 21. An analyst needs to search for events from the sales index where the status field is either success or pending. Which SPL search is appropriate? index=sales status=success OR pending index=sales status IN (success,pending) index=sales (status=success OR status=pending) index=sales status=(success,pending) Correct Answer: 3. […]<\/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\/21663"}],"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=21663"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/21663\/revisions"}],"predecessor-version":[{"id":21664,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/21663\/revisions\/21664"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=21663"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=21663"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=21663"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}