{"id":22375,"date":"2026-09-25T12:32:31","date_gmt":"2026-09-25T12:32:31","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=22375"},"modified":"2026-09-25T12:32:31","modified_gmt":"2026-09-25T12:32:31","slug":"pmi-pmi-pba-practice-test-questions-and-exam-dumps-part15-q281-300","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/pmi-pmi-pba-practice-test-questions-and-exam-dumps-part15-q281-300\/","title":{"rendered":"PMI PMI-PBA Practice Test Questions and Exam Dumps Part15 Q281-300"},"content":{"rendered":"

View Full <\/b>PMI PMI-PBA Exam Dumps<\/b><\/a> and Practice Test Dumps<\/b><\/h2>\n

 <\/p>\n

Question 281.<\/b><\/p>\n

A business analyst finds that a requirement is technically complete but cannot be traced to any business objective, stakeholder need, regulation, or other justified source. What should the analyst do?<\/b><\/p>\n

    \n
  1. <\/b> Implement it because it is technically complete<\/span>
    \n<\/span>2.<\/b> Investigate its rationale and determine whether sufficient business justification exists<\/span>
    \n<\/span>3.<\/b> Give it the highest priority<\/span>
    \n<\/span>4.<\/b> Ask the technical team to create a business objective for it<\/span><\/li>\n<\/ol>\n

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

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

    Technical completeness does not establish that a requirement should consume organizational resources. The analyst should understand why the requirement exists and determine whether it supports a stakeholder need, business objective, regulatory obligation, risk response, or another legitimate purpose. If no justification can be established, the requirement should be brought to appropriate stakeholders for a scope or prioritization decision. Traceability from requirements to their sources and objectives helps identify unnecessary scope and ensures that solution capabilities contribute to intended business outcomes.<\/span><\/p>\n

    Question 282.<\/b><\/p>\n

    A business analyst wants to represent a complex decision in which each answer leads to another condition or final outcome. Which technique is particularly suitable?<\/b><\/p>\n

      \n
    1. <\/b> Decision tree<\/span>
      \n<\/span>2.<\/b> Stakeholder register<\/span>
      \n<\/span>3.<\/b> Context diagram<\/span>
      \n<\/span>4.<\/b> SWOT analysis<\/span><\/li>\n<\/ol>\n

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

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

      A decision tree represents decisions and their possible paths visually, making it useful when an outcome depends on a sequence of conditions or choices. Stakeholders can follow individual branches to understand how different circumstances lead to particular results. The model can expose missing paths, inconsistent outcomes, or unclear business rules. Decision tables may be more efficient when many independent condition combinations must be analyzed, while decision trees are particularly intuitive when decisions occur sequentially. The analyst should select the representation that communicates the business logic most effectively.<\/span><\/p>\n

      Question 283.<\/b><\/p>\n

      A business analyst discovers that an important stakeholder was omitted from earlier elicitation activities. What should the analyst do?<\/b><\/p>\n

        \n
      1. <\/b> Exclude the stakeholder because elicitation has already occurred<\/span>
        \n<\/span>2.<\/b> Ask another stakeholder to approve everything on the omitted stakeholder’s behalf<\/span>
        \n<\/span>3.<\/b> Assess the stakeholder’s needs and determine whether existing requirements or decisions need to be revisited<\/span>
        \n<\/span>4.<\/b> Wait until solution deployment to obtain feedback<\/span><\/li>\n<\/ol>\n

        Correct Answer: 3<\/b><\/p>\n

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

        Discovering a missing stakeholder can reveal gaps in requirements or assumptions. The analyst should determine the stakeholder’s role, influence, needs, and potential impact on the solution and then conduct appropriate elicitation. Existing requirements and decisions should be reviewed where the stakeholder’s perspective is materially relevant. Not every previous activity necessarily needs to be repeated, but significant omissions should be corrected before they become expensive implementation problems. Stakeholder analysis should therefore continue throughout the initiative rather than being treated as a one-time activity.<\/span><\/p>\n

        Question 284.<\/b><\/p>\n

        A proposed solution requires a third-party interface, but the external provider has announced that the current interface will soon be discontinued. What should the business analyst do?<\/b><\/p>\n

          \n
        1. <\/b> Ignore the announcement because the current interface still works<\/span>
          \n<\/span>2.<\/b> Build exclusively for the discontinued interface<\/span>
          \n<\/span>3.<\/b> Remove all integration requirements<\/span>
          \n<\/span>4.<\/b> Assess the future interface, timing, migration implications, dependencies, and risks before finalizing requirements<\/span><\/li>\n<\/ol>\n

          Correct Answer: 4<\/b><\/p>\n

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

          Known external changes should be incorporated into analysis when they affect the expected operating environment. Building around an interface that will soon disappear could create immediate rework or prevent the solution from functioning after deployment. The analyst should confirm the provider’s timeline, understand the replacement interface, identify compatibility and migration requirements, and evaluate schedule and dependency risks. Requirements may need to accommodate a transition period. Proactive analysis helps ensure that the solution remains viable beyond its initial implementation date.<\/span><\/p>\n

          Question 285.<\/b><\/p>\n

          What is an important reason for maintaining requirement rationale?<\/b><\/p>\n

            \n
          1. <\/b> It explains why a requirement exists and can support prioritization, change analysis, and future decisions.<\/span>
            \n<\/span>2.<\/b> It guarantees that the requirement will never change.<\/span>
            \n<\/span>3.<\/b> It replaces acceptance criteria.<\/span>
            \n<\/span>4.<\/b> It eliminates the need for requirement ownership.<\/span><\/li>\n<\/ol>\n

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

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

            Requirement rationale records the reason a requirement is needed. This context can be valuable when stakeholders later question the requirement, propose changes, or need to choose between competing priorities. Without rationale, future teams may preserve obsolete requirements simply because nobody understands why they were created. Rationale can also distinguish mandatory requirements from preferences and connect requirements to risks, benefits, policies, or objectives. It complements traceability and other attributes but does not replace validation, acceptance criteria, or ownership.<\/span><\/p>\n

            Question 286.<\/b><\/p>\n

            A business analyst wants to understand why a process consistently produces a high percentage of incorrect transactions. What should the analyst focus on?<\/b><\/p>\n

              \n
            1. <\/b> Replacing the process immediately<\/span>
              \n<\/span>2.<\/b> Identifying underlying causes using process evidence, error data, stakeholder input, and root cause analysis<\/span>
              \n<\/span>3.<\/b> Increasing the target error rate<\/span>
              \n<\/span>4.<\/b> Measuring only employee attendance<\/span><\/li>\n<\/ol>\n

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

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

              A high error rate is an observable symptom, but improvement depends on understanding what causes those errors. The analyst should examine where errors occur, their categories, process conditions, system behavior, business rules, training, data quality, workload, and other relevant factors. Root cause techniques can help distinguish underlying causes from symptoms. Once the causes are sufficiently understood, stakeholders can evaluate solution alternatives that address them directly. Implementing changes based only on assumptions may shift the problem or create additional inefficiencies.<\/span><\/p>\n

              Question 287.<\/b><\/p>\n

              A requirement states that a service must be available 99.9% of the time. What additional information should the business analyst clarify?<\/b><\/p>\n

                \n
              1. <\/b> Only which team developed the service<\/span>
                \n<\/span>2.<\/b> Only the service’s purchase price<\/span>
                \n<\/span>3.<\/b> Measurement period, service hours, exclusions, planned maintenance, and how availability will be calculated<\/span>
                \n<\/span>4.<\/b> Only the user interface design<\/span><\/li>\n<\/ol>\n

                Correct Answer: 3<\/b><\/p>\n

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

                A percentage such as 99.9% can still be ambiguous without a defined measurement method. Stakeholders should agree on the relevant service period, whether planned maintenance is excluded, which components are included, and how partial outages are treated. The analyst should also understand the business impact of downtime to confirm that the target is appropriate. Clear measurement rules allow solution architects to design for the required level of availability and enable operations and stakeholders to evaluate actual performance consistently after implementation.<\/span><\/p>\n

                Question 288.<\/b><\/p>\n

                A business analyst learns that users need extensive manual training to complete a supposedly intuitive new process. What should the analyst do?<\/b><\/p>\n

                  \n
                1. <\/b> Assume additional training is always the best solution<\/span>
                  \n<\/span>2.<\/b> Remove all training materials<\/span>
                  \n<\/span>3.<\/b> Ignore the issue because training is outside business analysis<\/span>
                  \n<\/span>4.<\/b> Investigate whether the difficulty indicates usability, process, requirement, or organizational readiness problems<\/span><\/li>\n<\/ol>\n

                  Correct Answer: 4<\/b><\/p>\n

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

                  Training can be necessary, particularly for complex business activities, but unexpectedly extensive training may indicate a deeper problem. The process could be unnecessarily complicated, the interface may be difficult to understand, requirements may not reflect user needs, or users may lack prerequisite knowledge. The analyst should investigate the cause before assuming more training is the only answer. The appropriate response could involve usability improvements, process redesign, revised instructions, role changes, or targeted training. The objective is effective operational performance rather than training volume.<\/span><\/p>\n

                  Question 289.<\/b><\/p>\n

                  What is a primary purpose of model validation?<\/b><\/p>\n

                    \n
                  1. <\/b> To confirm with relevant stakeholders that a model accurately and sufficiently represents the intended business information or behavior<\/span>
                    \n<\/span>2.<\/b> To guarantee the model contains no technical notation errors<\/span>
                    \n<\/span>3.<\/b> To prevent the model from changing<\/span>
                    \n<\/span>4.<\/b> To replace textual requirements entirely<\/span><\/li>\n<\/ol>\n

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

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

                    Models simplify or visualize business information, processes, data, states, decisions, or interactions. Validation determines whether the model represents the intended reality or future behavior sufficiently for its purpose. Relevant stakeholders should review the content, assumptions, boundaries, exceptions, and relationships rather than focusing only on notation. A technically perfect diagram can still represent the wrong process or rule. Models can complement textual requirements and often reveal issues that prose hides, but they do not necessarily replace every other requirements artifact.<\/span><\/p>\n

                    Question 290.<\/b><\/p>\n

                    A business analyst needs to evaluate whether a proposed requirement is worth delivering in the next release. Which information is most useful?<\/b><\/p>\n

                      \n
                    1. <\/b> The requirement’s document length<\/span>
                      \n<\/span>2.<\/b> Expected value, urgency, dependencies, risks, effort, constraints, and strategic alignment<\/span>
                      \n<\/span>3.<\/b> The alphabetical position of the requirement<\/span>
                      \n<\/span>4.<\/b> The number of meetings in which it was discussed<\/span><\/li>\n<\/ol>\n

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

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

                      Release decisions should consider multiple factors rather than relying on a single characteristic. Business value and urgency help determine importance, while dependencies and constraints can affect feasible sequencing. Effort and risk provide information about delivery implications, and strategic alignment helps ensure scarce resources support organizational priorities. Mandatory regulatory or contractual requirements may also influence timing. The analyst should make these factors visible to authorized decision-makers. A structured approach produces more defensible priorities than ordering requirements according to documentation characteristics or stakeholder persistence.<\/span><\/p>\n

                      Question 291.<\/b><\/p>\n

                      A business analyst finds that an existing process includes an activity that produces no identifiable customer, compliance, control, or operational value. What should the analyst do?<\/b><\/p>\n

                        \n
                      1. <\/b> Preserve the activity because it already exists<\/span>
                        \n<\/span>2.<\/b> Automate the activity immediately<\/span>
                        \n<\/span>3.<\/b> Investigate why it exists and evaluate whether it can be eliminated from the future process<\/span>
                        \n<\/span>4.<\/b> Add an approval step after the activity<\/span><\/li>\n<\/ol>\n

                        Correct Answer: 3<\/b><\/p>\n

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

                        Current-state activities should not automatically be reproduced in the future state. Some may represent legacy practices that no longer serve a meaningful purpose. The analyst should determine whether the activity supports a business rule, control, regulatory obligation, information need, or other legitimate outcome. If no sufficient rationale remains, eliminating the activity may reduce cost, cycle time, and complexity. Automating a non-value-adding activity can simply make unnecessary work occur faster. Process improvement should therefore question the purpose of existing steps before preserving them.<\/span><\/p>\n

                        Question 292.<\/b><\/p>\n

                        A business analyst discovers that a proposed automated process could make incorrect high-value decisions when source data is incomplete. What should the analyst do?<\/b><\/p>\n

                          \n
                        1. <\/b> Allow automation to proceed without exception handling<\/span>
                          \n<\/span>2.<\/b> Treat missing data as automatically valid<\/span>
                          \n<\/span>3.<\/b> Remove data validation<\/span>
                          \n<\/span>4.<\/b> Define appropriate validation, exception, escalation, and manual-review requirements based on business risk<\/span><\/li>\n<\/ol>\n

                          Correct Answer: 4<\/b><\/p>\n

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

                          Automation should not silently make high-impact decisions when required information is incomplete or unreliable. The analyst should determine which data is essential, what constitutes acceptable quality, and what the process should do when information fails validation. Depending on business risk, the solution might stop processing, request additional data, route the case for manual review, or escalate it. Explicit exception requirements protect the organization from inappropriate automated outcomes while allowing routine cases to benefit from automation.<\/span><\/p>\n

                          Question 293.<\/b><\/p>\n

                          Why should a business analyst periodically reassess stakeholder engagement during a long initiative?<\/b><\/p>\n

                            \n
                          1. <\/b> Stakeholder influence, interest, responsibilities, availability, and impact can change over time.<\/span>
                            \n<\/span>2.<\/b> Stakeholder analysis becomes permanently correct after the first meeting.<\/span>
                            \n<\/span>3.<\/b> It guarantees that no new stakeholder will appear.<\/span>
                            \n<\/span>4.<\/b> It eliminates the need for communication.<\/span><\/li>\n<\/ol>\n

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

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

                            Initiatives evolve, and stakeholder relationships can evolve with them. Organizational restructuring, staffing changes, new regulatory concerns, solution decisions, or changes in scope can alter who needs to participate and how. A stakeholder who was initially peripheral may become critical during implementation or transition. Periodic reassessment helps the analyst adapt elicitation, communication, validation, and decision-making approaches accordingly. Treating the original stakeholder analysis as permanently accurate can result in missed perspectives, delayed approvals, and ineffective engagement later in the initiative.<\/span><\/p>\n

                            Question 294.<\/b><\/p>\n

                            A business analyst is preparing requirements information for executives who need to make a funding decision. How should the information be presented?<\/b><\/p>\n

                              \n
                            1. <\/b> Provide every detailed requirement and technical field definition<\/span>
                              \n<\/span>2.<\/b> Tailor the communication toward objectives, value, costs, risks, alternatives, major requirements, and decision-relevant information<\/span>
                              \n<\/span>3.<\/b> Provide only technical architecture diagrams<\/span>
                              \n<\/span>4.<\/b> Avoid discussing assumptions and uncertainty<\/span><\/li>\n<\/ol>\n

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

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

                              Requirements communication should be tailored to the audience and purpose. Executives making a funding decision typically need sufficient information about the business need, strategic alignment, expected value, costs, major risks, assumptions, alternatives, and significant scope rather than every implementation detail. Detailed requirements should remain available when necessary, but overwhelming decision-makers with unnecessary detail can obscure the important issues. Effective communication provides the right level of information for the decision while remaining transparent about uncertainty and significant constraints.<\/span><\/p>\n

                              Question 295.<\/b><\/p>\n

                              A requirement specifies that personal information must be deleted when it is no longer needed. What should the business analyst clarify?<\/b><\/p>\n

                                \n
                              1. <\/b> Only which database stores the information<\/span>
                                \n<\/span>2.<\/b> Only who originally entered the information<\/span>
                                \n<\/span>3.<\/b> Retention triggers, applicable exceptions, deletion expectations, ownership, audit needs, and relevant legal or privacy rules<\/span>
                                \n<\/span>4.<\/b> Only the storage cost<\/span><\/li>\n<\/ol>\n

                                Correct Answer: 3<\/b><\/p>\n

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

                                A general requirement to delete information when no longer needed requires more precise business rules. The analyst should determine how the retention period begins, which events trigger deletion, whether legal holds or other exceptions apply, what systems and copies are included, and what evidence of deletion may be required. Privacy, records-management, legal, security, and business stakeholders may need to contribute. Clear lifecycle requirements help ensure information is retained for legitimate needs without being stored indefinitely and creating unnecessary privacy or compliance exposure.<\/span><\/p>\n

                                Question 296.<\/b><\/p>\n

                                A business analyst is evaluating a proposed future-state process that reduces cost but increases average customer waiting time significantly. What should the analyst do?<\/b><\/p>\n

                                  \n
                                1. <\/b> Recommend it solely because cost decreases<\/span>
                                  \n<\/span>2.<\/b> Ignore customer waiting time<\/span>
                                  \n<\/span>3.<\/b> Remove the cost measure<\/span>
                                  \n<\/span>4.<\/b> Present the cost and service-level trade-off against agreed business objectives and performance targets<\/span><\/li>\n<\/ol>\n

                                  Correct Answer: 4<\/b><\/p>\n

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

                                  Process alternatives can improve one outcome while worsening another. The analyst should make these trade-offs visible and compare them with organizational objectives and agreed performance expectations. A cost reduction may be worthwhile if the increase in waiting time remains acceptable, or it may undermine customer experience and retention objectives. The decision belongs to authorized stakeholders, but they need balanced information about both effects. Evaluating alternatives across multiple relevant measures helps avoid optimizing one metric at the expense of overall business value.<\/span><\/p>\n

                                  Question 297.<\/b><\/p>\n

                                  What is the purpose of requirements verification?<\/b><\/p>\n

                                    \n
                                  1. <\/b> To assess whether requirements are sufficiently well formed, clear, consistent, complete, feasible, and usable for their intended purpose<\/span>
                                    \n<\/span>2.<\/b> To prove that the final solution achieves every business benefit<\/span>
                                    \n<\/span>3.<\/b> To authorize all scope changes automatically<\/span>
                                    \n<\/span>4.<\/b> To replace requirements validation<\/span><\/li>\n<\/ol>\n

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

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

                                    Requirements verification focuses on the quality of requirements and related information. The analyst examines whether they are expressed clearly, consistently, completely, and at an appropriate level of detail for their intended use. Verification may also identify infeasible, duplicate, contradictory, or untestable requirements. Validation addresses a different question: whether the requirements represent the right needs and support intended business outcomes. Both activities are important because a perfectly written requirement can still describe the wrong capability, while a valuable need can be documented poorly.<\/span><\/p>\n

                                    Question 298.<\/b><\/p>\n

                                    A business analyst learns that an external supplier can support a required capability only if requests are submitted in batches rather than individually. What should the analyst do?<\/b><\/p>\n

                                      \n
                                    1. <\/b> Ignore the supplier limitation<\/span>
                                      \n<\/span>2.<\/b> Analyze how the constraint affects business processes, interfaces, timing, performance, and solution requirements<\/span>
                                      \n<\/span>3.<\/b> Tell users that no changes are necessary<\/span>
                                      \n<\/span>4.<\/b> Remove the capability without analysis<\/span><\/li>\n<\/ol>\n

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

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

                                      External solution constraints can affect business behavior and should be incorporated into requirements analysis. Batch processing may introduce delays, change workflow timing, affect customer expectations, or require queues and reconciliation procedures. The analyst should determine whether these consequences remain acceptable and whether alternative suppliers or solution approaches should be considered. The constraint should be communicated to affected stakeholders so requirements reflect realistic capabilities. Ignoring it could produce expectations that the selected external service cannot satisfy.<\/span><\/p>\n

                                      Question 299.<\/b><\/p>\n

                                      A business analyst notices that stakeholders have approved individual requirements but have never reviewed how those requirements work together as an end-to-end solution. What should the analyst do?<\/b><\/p>\n

                                        \n
                                      1. <\/b> Assume individual approvals guarantee solution coherence<\/span>
                                        \n<\/span>2.<\/b> Proceed directly to deployment<\/span>
                                        \n<\/span>3.<\/b> Facilitate integrated validation using appropriate scenarios, models, or walkthroughs<\/span>
                                        \n<\/span>4.<\/b> Remove relationships among requirements<\/span><\/li>\n<\/ol>\n

                                        Correct Answer: 3<\/b><\/p>\n

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

                                        Requirements can appear correct individually while producing gaps or conflicts when combined. End-to-end scenarios, process walkthroughs, prototypes, models, or other integrated validation techniques can help stakeholders understand how requirements interact. This may reveal missing transitions, inconsistent rules, duplicated behavior, or incomplete exception handling. The analyst should validate both individual requirements and their collective ability to support the intended business outcome. Integrated review is particularly valuable for complex solutions involving multiple processes, systems, roles, or organizational units.<\/span><\/p>\n

                                        Question 300.<\/b><\/p>\n

                                        A post-implementation review shows that a solution is delivering expected benefits, but operating costs are substantially higher than projected. What should the business analyst do?<\/b><\/p>\n

                                          \n
                                        1. <\/b> Ignore costs because benefits were achieved<\/span>
                                          \n<\/span>2.<\/b> Report only the favorable benefit results<\/span>
                                          \n<\/span>3.<\/b> Replace the original operating-cost estimate with the actual figure without further analysis<\/span>
                                          \n<\/span>4.<\/b> Evaluate the higher costs against overall realized value, investigate causes, and communicate the findings to appropriate stakeholders<\/span><\/li>\n<\/ol>\n

                                          Correct Answer: 4<\/b><\/p>\n

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

                                          Solution value depends on both benefits and the resources required to achieve and sustain them. Higher-than-expected operating costs may reduce the net value of an otherwise successful solution. The analyst should compare actual costs with assumptions and forecasts, identify the causes of variance, and determine whether corrective opportunities exist. Stakeholders should receive a balanced assessment that includes favorable outcomes as well as unexpected costs. Post-implementation evaluation helps the organization understand actual value and improve future business cases, estimates, and solution decisions.<\/span><\/p>\n

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

                                          View Full PMI PMI-PBA Exam Dumps and Practice Test Dumps   Question 281. A business analyst finds that a requirement is technically complete but cannot be traced to any business objective, stakeholder need, regulation, or other justified source. What should the analyst do? Implement it because it is technically complete 2. Investigate its rationale and […]<\/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\/22375"}],"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=22375"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/22375\/revisions"}],"predecessor-version":[{"id":22376,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/22375\/revisions\/22376"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=22375"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=22375"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=22375"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}