{"id":20644,"date":"2026-09-24T06:34:17","date_gmt":"2026-09-24T06:34:17","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=20644"},"modified":"2026-09-24T06:34:17","modified_gmt":"2026-09-24T06:34:17","slug":"iiba-cbap-practice-test-questions-and-exam-dumps-part-17-q321-340","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/iiba-cbap-practice-test-questions-and-exam-dumps-part-17-q321-340\/","title":{"rendered":"IIBA CBAP Practice Test Questions and Exam Dumps Part 17 Q321-340"},"content":{"rendered":"

View Full <\/b>IIBA CBAP Exam Dumps<\/b><\/a> and Practice Test Dumps<\/b><\/h2>\n

 <\/p>\n

Question 321: A business analyst is defining the boundaries of a business capability assessment. Which information is most important to establish first?<\/b><\/p>\n

    \n
  1. <\/b> The current and desired capability states, including relevant performance outcomes<\/span><\/li>\n
  2. <\/b> The preferred software vendor for the future solution<\/span><\/li>\n
  3. <\/b> The detailed interface design for each affected system<\/span><\/li>\n
  4. <\/b> The final training schedule for end users<\/span><\/li>\n<\/ol>\n

    Correct Answer: 1. The current and desired capability states, including relevant performance outcomes<\/b><\/p>\n

    Explanation:<\/b>
    \n<\/b>A capability assessment should establish what the organization can do today and what it needs to be able to do in the future. Comparing current and desired capability states helps identify gaps that may prevent the organization from achieving its objectives. Performance outcomes provide additional context for determining whether the capability is adequate. Software vendors, interface designs, and training schedules may become relevant later, but they are implementation details rather than the primary basis for assessing the capability gap. The business analyst should therefore begin by understanding the required capabilities and the difference between the current and desired states.<\/span><\/p>\n

    Question 322: During requirements analysis, stakeholders use the same term to mean different things. What should the business analyst do?<\/b><\/p>\n

      \n
    1. <\/b> Select the definition used most frequently by stakeholders<\/span><\/li>\n
    2. <\/b> Remove the term from all requirements<\/span><\/li>\n
    3. <\/b> Establish and validate a shared definition with the appropriate stakeholders<\/span><\/li>\n
    4. <\/b> Allow each stakeholder to retain a separate interpretation<\/span><\/li>\n<\/ol>\n

      Correct Answer: 3. Establish and validate a shared definition with the appropriate stakeholders<\/b><\/p>\n

      Explanation:<\/b>
      \n<\/b>Inconsistent terminology can create ambiguity and cause stakeholders to interpret requirements differently. The business analyst should identify the conflicting meanings, discuss them with the relevant stakeholders, and establish a shared definition that accurately reflects the intended business concept. The agreed definition should then be reflected consistently in requirements and related documentation. Choosing the most common interpretation does not guarantee that it is correct, while removing a useful business term may create additional confusion. Separate interpretations should not remain when a shared understanding is required for successful analysis and solution delivery.<\/span><\/p>\n

      Question 323: A proposed solution requires information from an external organization that provides data only once each month. Which consideration is most important when analyzing this dependency?<\/b><\/p>\n

        \n
      1. <\/b> The color scheme of the external organization’s system<\/span><\/li>\n
      2. <\/b> The dependency’s timing, responsibilities, risks, and effect on solution operations<\/span><\/li>\n
      3. <\/b> The number of employees working for the external organization<\/span><\/li>\n
      4. <\/b> The programming language used by the external organization’s system<\/span><\/li>\n<\/ol>\n

        Correct Answer: 2. The dependency’s timing, responsibilities, risks, and effect on solution operations<\/b><\/p>\n

        Explanation:<\/b>
        \n<\/b>External dependencies can significantly affect solution performance, timing, and reliability. The business analyst should understand when the required information becomes available, who is responsible for providing and receiving it, what risks could interrupt the dependency, and what consequences result if the information is late or unavailable. These factors help determine whether the proposed solution is feasible and what controls or alternatives may be required. Details such as color schemes, employee counts, or programming languages are generally not relevant unless they directly affect the dependency or the business outcome being analyzed.<\/span><\/p>\n

        Question 324: A stakeholder proposes eliminating a requirement because it is difficult to implement. What should the business analyst evaluate before recommending its removal?<\/b><\/p>\n

          \n
        1. <\/b> Only the developer’s estimated implementation effort<\/span><\/li>\n
        2. <\/b> Whether another stakeholder dislikes the requirement<\/span><\/li>\n
        3. <\/b> Whether the requirement appears frequently in similar projects<\/span><\/li>\n
        4. <\/b> Its business value, dependencies, objectives supported, and consequences of removal<\/span><\/li>\n<\/ol>\n

          Correct Answer: 4. Its business value, dependencies, objectives supported, and consequences of removal<\/b><\/p>\n

          Explanation:<\/b>
          \n<\/b>Implementation difficulty alone is not sufficient justification for removing a requirement. The business analyst should determine why the requirement exists, what business objective or outcome it supports, which other requirements or solution components depend on it, and what consequences could result from removing it. The analysis may reveal that the requirement is essential despite its implementation complexity, or that an alternative can provide the same value more efficiently. This approach supports an evidence-based decision rather than allowing technical effort alone to determine business requirements.<\/span><\/p>\n

          Question 325: A business analyst wants to determine whether a process improvement actually reduced processing time. Which approach provides the strongest evidence?<\/b><\/p>\n

            \n
          1. <\/b> Compare a defined baseline measure with performance after implementation<\/span><\/li>\n
          2. <\/b> Ask employees whether the process feels faster<\/span><\/li>\n
          3. <\/b> Review only the project team’s opinion<\/span><\/li>\n
          4. <\/b> Compare the new process with an unrelated department<\/span><\/li>\n<\/ol>\n

            Correct Answer: 1. Compare a defined baseline measure with performance after implementation<\/b><\/p>\n

            Explanation:<\/b>
            \n<\/b>A measurable baseline provides a reference point against which the results of a change can be evaluated. The business analyst should establish or identify the processing-time measure before the change and compare it with the corresponding measure after implementation. This allows the organization to determine whether the expected improvement actually occurred. Employee perceptions and project-team opinions may provide useful qualitative information, but they do not provide the same objective evidence. Comparing unrelated departments may also introduce differences that make the results difficult to interpret accurately.<\/span><\/p>\n

            Question 326: A solution is technically feasible, but employees will need to perform several new activities. What should the business analyst analyze next?<\/b><\/p>\n

              \n
            1. <\/b> Whether the solution has the most attractive user interface<\/span><\/li>\n
            2. <\/b> Organizational readiness, role changes, required skills, and transition impacts<\/span><\/li>\n
            3. <\/b> Whether the project can be completed without stakeholder involvement<\/span><\/li>\n
            4. <\/b> Whether the existing solution should automatically be retired<\/span><\/li>\n<\/ol>\n

              Correct Answer: 2. Organizational readiness, role changes, required skills, and transition impacts<\/b><\/p>\n

              Explanation:<\/b>
              \n<\/b>Technical feasibility does not guarantee that an organization can successfully adopt a solution. When employees must perform new activities, the business analyst should examine organizational readiness, changes to roles and responsibilities, required skills, training or support needs, and other transition impacts. These factors can reveal capability gaps or adoption risks that need to be addressed before implementation. Automatically retiring the existing solution or avoiding stakeholder involvement does not address these organizational considerations. Understanding the human and operational effects helps ensure that the solution can actually deliver its intended business outcomes.<\/span><\/p>\n

              Question 327: Several stakeholders request different features, but analysis shows that all requests are intended to improve the same business outcome. What should the business analyst do?<\/b><\/p>\n

                \n
              1. <\/b> Select the feature requested by the most senior stakeholder<\/span><\/li>\n
              2. <\/b> Treat each feature as an unrelated business need<\/span><\/li>\n
              3. <\/b> Analyze the common underlying need and evaluate solution alternatives against it<\/span><\/li>\n
              4. <\/b> Reject all requests because they are inconsistent<\/span><\/li>\n<\/ol>\n

                Correct Answer: 3. Analyze the common underlying need and evaluate solution alternatives against it<\/b><\/p>\n

                Explanation:<\/b>
                \n<\/b>Different stakeholder requests may represent different proposed solutions to the same underlying business need. The business analyst should identify the shared desired outcome and then evaluate the alternatives based on their ability to address that outcome. This prevents the analysis from becoming unnecessarily focused on stakeholder-preferred features. Seniority alone should not determine the solution, and rejecting all requests would discard potentially valuable information. Understanding the common need also creates an opportunity to identify a solution that satisfies the business objective more effectively than any individual feature initially proposed.<\/span><\/p>\n

                Question 328: A requirement is understandable but cannot be objectively tested. Which improvement is most appropriate?<\/b><\/p>\n

                  \n
                1. <\/b> Add measurable and observable acceptance criteria<\/span><\/li>\n
                2. <\/b> Add additional technical terminology<\/span><\/li>\n
                3. <\/b> Increase the requirement’s level of abstraction<\/span><\/li>\n
                4. <\/b> Remove all conditions from the requirement<\/span><\/li>\n<\/ol>\n

                  Correct Answer: 1. Add measurable and observable acceptance criteria<\/b><\/p>\n

                  Explanation:<\/b>
                  \n<\/b>A requirement should be sufficiently testable so stakeholders can determine whether the intended capability or condition has been achieved. Adding measurable and observable acceptance criteria converts vague expectations into conditions that can be objectively evaluated. Additional technical terminology may make the requirement harder to understand, while increasing abstraction can reduce testability. Removing conditions would generally make the requirement less precise rather than more useful. The business analyst should work with stakeholders to define expected results, thresholds, conditions, or other observable measures that provide a clear basis for validation.<\/span><\/p>\n

                  Question 329: A business analyst is comparing two proposed solutions. Stakeholders disagree because one emphasizes lower cost while the other emphasizes faster implementation. What should guide the analysis?<\/b><\/p>\n

                    \n
                  1. <\/b> The personal preference of the project manager<\/span><\/li>\n
                  2. <\/b> The solution with the lowest initial purchase price<\/span><\/li>\n
                  3. <\/b> The solution preferred by the largest stakeholder group<\/span><\/li>\n
                  4. <\/b> Agreed decision criteria reflecting business value, cost, risk, timing, and constraints<\/span><\/li>\n<\/ol>\n

                    Correct Answer: 4. Agreed decision criteria reflecting business value, cost, risk, timing, and constraints<\/b><\/p>\n

                    Explanation:<\/b>
                    \n<\/b>Solution alternatives should be evaluated using criteria that reflect the organization’s objectives and constraints rather than individual preferences. Relevant criteria may include expected business value, total cost, implementation timing, risks, feasibility, dependencies, and strategic alignment. Establishing or confirming agreed criteria helps stakeholders understand the trade-offs involved and provides a consistent basis for comparing alternatives. Selecting an option solely because it has the lowest initial cost or the largest stakeholder following may overlook important consequences. The analysis should make those trade-offs visible so the appropriate decision-makers can make an informed decision.<\/span><\/p>\n

                    Question 330: During a process review, the same activity is performed by two departments using different procedures. What should the business analyst investigate?<\/b><\/p>\n

                      \n
                    1. <\/b> Which department has more employees<\/span><\/li>\n
                    2. <\/b> Whether both departments use the same software brand<\/span><\/li>\n
                    3. <\/b> Differences in inputs, rules, resources, roles, systems, and business conditions<\/span><\/li>\n
                    4. <\/b> Which department was created first<\/span><\/li>\n<\/ol>\n

                      Correct Answer: 3. Differences in inputs, rules, resources, roles, systems, and business conditions<\/b><\/p>\n

                      Explanation:<\/b>
                      \n<\/b>Process variation may be intentional or may indicate an opportunity for improvement. The business analyst should investigate the factors that cause the departments to perform the activity differently. These can include differences in inputs, business rules, roles, resources, systems, customer types, or operating conditions. Understanding these causes helps determine whether the variation is necessary or whether standardization could improve performance. Department size, software branding, or organizational age does not by itself explain why the process differs. The analysis should focus on the actual conditions that influence how the activity is performed.<\/span><\/p>\n

                      Question 331: A project has many requirements with dependencies among them. What is the primary benefit of maintaining requirements traceability?<\/b><\/p>\n

                        \n
                      1. <\/b> It identifies relationships and helps assess the impact of requirement changes<\/span><\/li>\n
                      2. <\/b> It eliminates the need for stakeholder validation<\/span><\/li>\n
                      3. <\/b> It guarantees that every requirement will be implemented<\/span><\/li>\n
                      4. <\/b> It replaces solution testing<\/span><\/li>\n<\/ol>\n

                        Correct Answer: 1. It identifies relationships and helps assess the impact of requirement changes<\/b><\/p>\n

                        Explanation:<\/b>
                        \n<\/b>Requirements traceability records meaningful relationships between requirements and other elements such as business objectives, solution components, designs, tests, and related requirements. When one requirement changes, traceability helps the business analyst identify potentially affected elements and assess impacts. Traceability does not guarantee implementation, eliminate stakeholder validation, or replace testing. Its value is in maintaining understanding of how requirements relate to the business need and solution, thereby supporting impact analysis, consistency, completeness, and controlled change throughout the initiative.<\/span><\/p>\n

                        Question 332: A stakeholder provides information based primarily on personal experience. What should the business analyst do before treating the information as an established fact?<\/b><\/p>\n

                          \n
                        1. <\/b> Accept it because the stakeholder has worked in the process<\/span><\/li>\n
                        2. <\/b> Validate it using appropriate evidence and other relevant stakeholders<\/span><\/li>\n
                        3. <\/b> Remove the information from the analysis<\/span><\/li>\n
                        4. <\/b> Replace it with information from a different project<\/span><\/li>\n<\/ol>\n

                          Correct Answer: 2. Validate it using appropriate evidence and other relevant stakeholders<\/b><\/p>\n

                          Explanation:<\/b>
                          \n<\/b>Stakeholder experience can provide valuable insight, especially about operational practices that may not be documented. However, individual experience may represent only one perspective or a specific situation. The business analyst should validate important information through additional evidence, relevant stakeholders, observations, data, documentation, or other appropriate sources. Automatically accepting the information could introduce incorrect assumptions, while discarding it would lose potentially useful knowledge. Validation allows the analyst to distinguish individual perceptions from broader process realities and improves the reliability of the requirements and analysis conclusions.<\/span><\/p>\n

                          Question 333: A business analyst identifies a proposed change that affects several departments differently. What should be included in the impact analysis?<\/b><\/p>\n

                            \n
                          1. <\/b> Only the department requesting the change<\/span><\/li>\n
                          2. <\/b> Only the estimated development effort<\/span><\/li>\n
                          3. <\/b> The effects on affected processes, roles, requirements, systems, risks, and stakeholders<\/span><\/li>\n
                          4. <\/b> Only the financial cost of the change<\/span><\/li>\n<\/ol>\n

                            Correct Answer: 3. The effects on affected processes, roles, requirements, systems, risks, and stakeholders<\/b><\/p>\n

                            Explanation:<\/b>
                            \n<\/b>A cross-functional change can produce different consequences for different parts of an organization. Impact analysis should therefore consider affected processes, roles and responsibilities, requirements, systems, information, stakeholders, risks, costs, dependencies, and expected benefits. Focusing only on the requesting department or development effort may overlook important operational consequences. Financial cost is also relevant but is only one part of the analysis. A comprehensive impact assessment helps decision-makers understand the full scope of the change and determine whether additional requirements, mitigations, stakeholder involvement, or implementation activities are necessary.<\/span><\/p>\n

                            Question 334: A business analyst is evaluating whether a proposed solution complies with organizational policies. Which information is most relevant?<\/b><\/p>\n

                              \n
                            1. <\/b> The personal preferences of individual developers<\/span><\/li>\n
                            2. <\/b> The solution’s visual design<\/span><\/li>\n
                            3. <\/b> The number of project meetings completed<\/span><\/li>\n
                            4. <\/b> Applicable policies, controls, constraints, and the impacts of non-compliance<\/span><\/li>\n<\/ol>\n

                              Correct Answer: 4. Applicable policies, controls, constraints, and the impacts of non-compliance<\/b><\/p>\n

                              Explanation:<\/b>
                              \n<\/b>Organizational policies may impose mandatory conditions on a solution. The business analyst should identify the policies and controls that apply, determine what constraints they create, and understand the consequences if the solution does not comply. Depending on the context, non-compliance could create operational, financial, legal, security, or reputational consequences. Visual design, meeting counts, and individual preferences generally do not establish compliance. Compliance analysis should be based on the applicable organizational rules and evidence showing whether the proposed solution satisfies them.<\/span><\/p>\n

                              Question 335: A stakeholder wants a requirement included because it was used successfully in another organization. What should the business analyst determine first?<\/b><\/p>\n

                                \n
                              1. <\/b> Whether the requirement is relevant and applicable to the current organization’s context and objectives<\/span><\/li>\n
                              2. <\/b> Whether the other organization used the same project methodology<\/span><\/li>\n
                              3. <\/b> Whether the requirement is more expensive than current requirements<\/span><\/li>\n
                              4. <\/b> Whether the stakeholder can provide the original project schedule<\/span><\/li>\n<\/ol>\n

                                Correct Answer: 1. Whether the requirement is relevant and applicable to the current organization’s context and objectives<\/b><\/p>\n

                                Explanation:<\/b>
                                \n<\/b>A requirement that worked in another organization is not automatically appropriate for the current initiative. The business analyst should determine whether the requirement addresses a relevant business need, supports current objectives, and fits the organization’s processes, constraints, stakeholders, capabilities, and operating environment. External examples can provide useful ideas, but they must be evaluated in context. Project methodology, schedule, or isolated cost comparisons do not establish applicability. Reusing requirements should therefore involve analysis of the assumptions and conditions under which the original requirement was successful.<\/span><\/p>\n

                                Question 336: A business analyst is preparing information for executives and operational users. What should the analyst do?<\/b><\/p>\n

                                  \n
                                1. <\/b> Give both groups exactly the same level of technical detail<\/span><\/li>\n
                                2. <\/b> Tailor the content and level of detail to each audience while preserving consistent meaning<\/span><\/li>\n
                                3. <\/b> Provide only technical information to both groups<\/span><\/li>\n
                                4. <\/b> Allow each group to interpret the requirements independently<\/span><\/li>\n<\/ol>\n

                                  Correct Answer: 2. Tailor the content and level of detail to each audience while preserving consistent meaning<\/b><\/p>\n

                                  Explanation:<\/b>
                                  \n<\/b>Different stakeholder groups have different information needs, responsibilities, expertise, and decision-making roles. Executives may need concise information about outcomes, value, risks, and trade-offs, while operational users may need more detail about processes, activities, rules, and impacts. Tailoring communication improves understanding without changing the underlying meaning of the requirements. Providing identical technical detail to everyone may overwhelm some stakeholders, while allowing independent interpretations can create inconsistency. The business analyst should therefore adapt the presentation while maintaining a consistent and accurate representation of the analyzed information.<\/span><\/p>\n

                                  Question 337: A project team discovers that a proposed feature will create additional operational costs after implementation. What should the business analyst include when evaluating the feature?<\/b><\/p>\n

                                    \n
                                  1. <\/b> Only the initial development cost<\/span><\/li>\n
                                  2. <\/b> Only the expected customer benefit<\/span><\/li>\n
                                  3. <\/b> The feature’s life-cycle costs, expected benefits, risks, and business value<\/span><\/li>\n
                                  4. <\/b> Only the cost of training employees<\/span><\/li>\n<\/ol>\n

                                    Correct Answer: 3. The feature’s life-cycle costs, expected benefits, risks, and business value<\/b><\/p>\n

                                    Explanation:<\/b>
                                    \n<\/b>A feature should be evaluated across its relevant life cycle rather than only by its initial implementation cost. Ongoing operational costs, maintenance, support, training, expected benefits, risks, and other consequences can significantly affect its overall value. Considering these factors provides decision-makers with a more complete understanding of the trade-offs. Focusing only on development, customer benefit, or training may produce an incomplete assessment. The business analyst should ensure that both short-term and ongoing implications are considered when determining whether the feature supports the organization’s objectives.<\/span><\/p>\n

                                    Question 338: A requirement depends on another requirement that is scheduled for a later release. What should the business analyst do?<\/b><\/p>\n

                                      \n
                                    1. <\/b> Ignore the dependency until implementation begins<\/span><\/li>\n
                                    2. <\/b> Remove the dependent requirement immediately<\/span><\/li>\n
                                    3. <\/b> Document the dependency and assess its effect on timing, scope, risks, and implementation<\/span><\/li>\n
                                    4. <\/b> Move both requirements into the first release automatically<\/span><\/li>\n<\/ol>\n

                                      Correct Answer: 3. Document the dependency and assess its effect on timing, scope, risks, and implementation<\/b><\/p>\n

                                      Explanation:<\/b>
                                      \n<\/b>Dependencies between requirements can affect release sequencing, feasibility, scope, risks, and expected outcomes. The business analyst should document the relationship and assess what happens if the dependent requirement is delivered later. The analysis may reveal that the requirement must be deferred, redesigned, delivered earlier, or supported through an alternative capability. Automatically moving both requirements or removing one without analysis can create unnecessary costs or prevent expected business outcomes. Explicitly managing dependencies allows stakeholders and decision-makers to understand their implications before committing to a release plan.<\/span><\/p>\n

                                      Question 339: A solution has been implemented, but the expected business benefit has not materialized. What should the business analyst examine?<\/b><\/p>\n

                                        \n
                                      1. <\/b> Only whether the software was deployed on schedule<\/span><\/li>\n
                                      2. <\/b> Whether the original need, expected outcomes, assumptions, adoption factors, and performance measures remain valid<\/span><\/li>\n
                                      3. <\/b> Only whether all functional requirements were marked complete<\/span><\/li>\n
                                      4. <\/b> Whether the project documentation uses the correct template<\/span><\/li>\n<\/ol>\n

                                        Correct Answer: 2. Whether the original need, expected outcomes, assumptions, adoption factors, and performance measures remain valid<\/b><\/p>\n

                                        Explanation:<\/b>
                                        \n<\/b>Successful implementation does not necessarily mean that the intended business outcome has been achieved. The business analyst should compare actual results with the expected outcomes and investigate whether the original business need was correctly represented, whether assumptions remain valid, whether users adopted the solution as expected, and whether the selected performance measures accurately capture the benefit. Functional completion alone may confirm delivery but not value realization. Examining these factors can reveal whether the issue is related to the solution, adoption, changing conditions, incorrect assumptions, or the way benefits were originally defined and measured.<\/span><\/p>\n

                                        Question 340: At the end of an initiative, the organization wants to improve its future business analysis practices. What should the business analyst capture?<\/b><\/p>\n

                                          \n
                                        1. <\/b> Only the final project budget<\/span><\/li>\n
                                        2. <\/b> Only stakeholder complaints<\/span><\/li>\n
                                        3. <\/b> Only the requirements that were rejected<\/span><\/li>\n
                                        4. <\/b> Lessons learned, effective practices, challenges, decisions, and improvement opportunities<\/span><\/li>\n<\/ol>\n

                                          Correct Answer: 4. Lessons learned, effective practices, challenges, decisions, and improvement opportunities<\/b><\/p>\n

                                          Explanation:<\/b>
                                          \n<\/b>Lessons learned help an organization improve its business analysis practices on future initiatives. The business analyst should capture what worked well, what created challenges, how important decisions were made, which approaches were effective or ineffective, and what improvements should be considered. Limiting the review to budget, complaints, or rejected requirements would provide only a partial view of the initiative. A structured review of analysis, elicitation, stakeholder engagement, decision-making, requirements management, and outcomes can provide reusable knowledge and help the organization continuously improve its business analysis practices.<\/span><\/p>\n

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

                                          View Full IIBA CBAP Exam Dumps and Practice Test Dumps   Question 321: A business analyst is defining the boundaries of a business capability assessment. Which information is most important to establish first? The current and desired capability states, including relevant performance outcomes The preferred software vendor for the future solution The detailed interface design […]<\/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\/20644"}],"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=20644"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/20644\/revisions"}],"predecessor-version":[{"id":20645,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/20644\/revisions\/20645"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=20644"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=20644"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=20644"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}