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

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

 <\/p>\n

Question 341: A business analyst is asked to determine whether a proposed initiative addresses a valid business need. Which information should be examined first?<\/b><\/p>\n

    \n
  1. <\/b> The preferred technology platform<\/span><\/li>\n
  2. <\/b> The project team’s previous experience<\/span><\/li>\n
  3. <\/b> The problem or opportunity, desired outcomes, and organizational objectives<\/span><\/li>\n
  4. <\/b> The number of developers available<\/span><\/li>\n<\/ol>\n

    Correct Answer: 3. The problem or opportunity, desired outcomes, and organizational objectives<\/b><\/p>\n

    Explanation:<\/b>
    \n<\/b>A valid business need is grounded in a problem, opportunity, or objective that provides a reason for undertaking an initiative. The business analyst should understand the current situation, the desired outcomes, and how those outcomes relate to organizational objectives. Technology preferences and resource availability may affect how the initiative is implemented, but they do not establish whether the underlying need is valid. Examining the business need first helps prevent the organization from pursuing a solution simply because a technology or implementation approach is available.<\/span><\/p>\n

    Question 342: During elicitation, a stakeholder gives very detailed information about a process but cannot explain why certain activities are performed. What should the business analyst do?<\/b><\/p>\n

      \n
    1. <\/b> Explore the purpose, business rules, and expected outcomes behind those activities<\/span><\/li>\n
    2. <\/b> Document every activity without further questioning<\/span><\/li>\n
    3. <\/b> Replace the stakeholder’s process with a standard industry process<\/span><\/li>\n
    4. <\/b> Assume the activities are required because they are currently performed<\/span><\/li>\n<\/ol>\n

      Correct Answer: 1. Explore the purpose, business rules, and expected outcomes behind those activities<\/b><\/p>\n

      Explanation:<\/b>
      \n<\/b>Understanding what a process does is not enough; the business analyst should also understand why the activities exist. Exploring the purpose, business rules, and expected outcomes can reveal unnecessary work, hidden constraints, compliance obligations, or opportunities for improvement. Simply documenting current activities may preserve inefficiencies without understanding their justification. Current practice should not automatically be treated as necessary, and replacing it with an external standard may ignore organization-specific needs. Focused questioning helps distinguish essential business activities from practices that may no longer provide value.<\/span><\/p>\n

      Question 343: A requirements review reveals that two requirements appear to conflict, but the stakeholders who created them are unavailable. What should the business analyst do first?<\/b><\/p>\n

        \n
      1. <\/b> Delete the newer requirement<\/span><\/li>\n
      2. <\/b> Implement both requirements and resolve the conflict later<\/span><\/li>\n
      3. <\/b> Ask the development team to decide which requirement is correct<\/span><\/li>\n
      4. <\/b> Investigate the source, purpose, dependencies, and context of each requirement<\/span><\/li>\n<\/ol>\n

        Correct Answer: 4. Investigate the source, purpose, dependencies, and context of each requirement<\/b><\/p>\n

        Explanation:<\/b>
        \n<\/b>A conflict may result from different business contexts, assumptions, priorities, or interpretations. Before changing or removing a requirement, the business analyst should investigate its origin, purpose, dependencies, and relationship to business objectives and other requirements. The development team should not independently decide business priorities, and implementing conflicting requirements can create defects or contradictory behavior. Understanding the context may reveal that one requirement is obsolete, that both apply under different conditions, or that a higher-level business rule resolves the apparent conflict.<\/span><\/p>\n

        Question 344: A stakeholder says that a proposed solution will improve customer loyalty. What should the business analyst request to evaluate this expected benefit?<\/b><\/p>\n

          \n
        1. <\/b> A list of all employees involved in implementation<\/span><\/li>\n
        2. <\/b> Defined measures and criteria for determining whether customer loyalty improves<\/span><\/li>\n
        3. <\/b> The preferred design of the solution<\/span><\/li>\n
        4. <\/b> A copy of the project communication plan<\/span><\/li>\n<\/ol>\n

          Correct Answer: 2. Defined measures and criteria for determining whether customer loyalty improves<\/b><\/p>\n

          Explanation:<\/b>
          \n<\/b>Expected benefits should be measurable or otherwise evaluable so the organization can determine whether the solution delivered the intended value. For a claim about improved customer loyalty, the business analyst should work with stakeholders to identify suitable measures, a baseline where appropriate, target conditions, and evaluation criteria. Without these elements, the organization may implement the solution but be unable to determine whether the expected benefit occurred. Implementation details and communication plans may be useful elsewhere, but they do not provide evidence for evaluating the claimed benefit.<\/span><\/p>\n

          Question 345: A business analyst discovers that a requirement has no identified stakeholder who can explain its purpose. What should the analyst investigate?<\/b><\/p>\n

            \n
          1. <\/b> Whether the requirement supports a valid business need, objective, or outcome<\/span><\/li>\n
          2. <\/b> Whether the requirement is written using the correct template<\/span><\/li>\n
          3. <\/b> Whether the requirement has the longest description in the set<\/span><\/li>\n
          4. <\/b> Whether the requirement can be assigned to a developer<\/span><\/li>\n<\/ol>\n

            Correct Answer: 1. Whether the requirement supports a valid business need, objective, or outcome<\/b><\/p>\n

            Explanation:<\/b>
            \n<\/b>A requirement should have a meaningful relationship to a business need, objective, stakeholder need, or expected outcome. If nobody can explain why the requirement exists, the business analyst should investigate its rationale before assuming that it should remain. The requirement may be inherited, outdated, duplicated, or based on an undocumented need. Formatting, description length, or developer assignment does not establish business justification. Understanding the requirement’s purpose helps determine whether it should be retained, clarified, modified, or removed based on evidence and stakeholder understanding.<\/span><\/p>\n

            Question 346: A solution requires employees to make decisions differently from the current process. Which analysis is most important before implementation?<\/b><\/p>\n

              \n
            1. <\/b> The visual consistency of the user interface<\/span><\/li>\n
            2. <\/b> The number of requirements in the backlog<\/span><\/li>\n
            3. <\/b> Changes to roles, decision rights, processes, skills, and organizational readiness<\/span><\/li>\n
            4. <\/b> The order in which requirements were originally elicited<\/span><\/li>\n<\/ol>\n

              Correct Answer: 3. Changes to roles, decision rights, processes, skills, and organizational readiness<\/b><\/p>\n

              Explanation:<\/b>
              \n<\/b>Changing how employees make decisions can affect responsibilities, authority, workflows, skills, controls, and organizational behavior. The business analyst should evaluate these changes to determine whether employees are prepared and whether transition activities are required. Organizational readiness analysis may identify training, communication, policy, process, or role changes that must be addressed. Interface design and backlog size do not provide sufficient information about the organizational impact. Understanding these effects before implementation can reduce adoption problems and ensure that the solution can operate effectively within the organization.<\/span><\/p>\n

              Question 347: Several requirements are individually valid, but together they exceed the approved solution scope. What should the business analyst do?<\/b><\/p>\n

                \n
              1. <\/b> Include all requirements because each one is valid<\/span><\/li>\n
              2. <\/b> Analyze their value, scope impact, dependencies, and alignment with objectives<\/span><\/li>\n
              3. <\/b> Remove the requirements with the longest descriptions<\/span><\/li>\n
              4. <\/b> Let developers decide which requirements should remain<\/span><\/li>\n<\/ol>\n

                Correct Answer: 2. Analyze their value, scope impact, dependencies, and alignment with objectives<\/b><\/p>\n

                Explanation:<\/b>
                \n<\/b>A requirement can be valid while still being outside the approved scope of a particular solution or release. The business analyst should assess the business value of the requirements, their relationship to objectives, dependencies, risks, and the consequences of expanding scope. This information supports an informed decision by the appropriate stakeholders. Automatically including every valid requirement can create uncontrolled scope growth, while arbitrary removal can eliminate valuable capabilities. Developers can provide technical input, but scope decisions should consider broader business priorities and authorized decision criteria.<\/span><\/p>\n

                Question 348: A business analyst needs to understand how information moves between activities in a business process. Which representation is most useful?<\/b><\/p>\n

                  \n
                1. <\/b> A stakeholder influence matrix<\/span><\/li>\n
                2. <\/b> A business capability map<\/span><\/li>\n
                3. <\/b> A decision log<\/span><\/li>\n
                4. <\/b> An information flow or data flow model<\/span><\/li>\n<\/ol>\n

                  Correct Answer: 4. An information flow or data flow model<\/b><\/p>\n

                  Explanation:<\/b>
                  \n<\/b>An information or data flow model helps represent where information originates, how it moves between activities or participants, and where it is transformed, stored, or consumed. This can reveal missing information, unnecessary handoffs, duplication, delays, or dependencies. A stakeholder influence matrix focuses on stakeholder relationships, a capability map describes organizational abilities, and a decision log records decisions and their context. Selecting the appropriate model depends on the analytical question, and when the question concerns movement and transformation of information, an information or data flow representation is appropriate.<\/span><\/p>\n

                  Question 349: A business analyst is evaluating a proposed change that will affect a regulatory control. What should be considered?<\/b><\/p>\n

                    \n
                  1. <\/b> Whether the change satisfies applicable regulatory obligations and required controls<\/span><\/li>\n
                  2. <\/b> Whether the change uses the organization’s preferred programming language<\/span><\/li>\n
                  3. <\/b> Whether the change reduces the number of project meetings<\/span><\/li>\n
                  4. <\/b> Whether the change has the same interface as the current solution<\/span><\/li>\n<\/ol>\n

                    Correct Answer: 1. Whether the change satisfies applicable regulatory obligations and required controls<\/b><\/p>\n

                    Explanation:<\/b>
                    \n<\/b>Regulatory obligations can impose mandatory requirements or constraints on a solution and its processes. When a change affects a regulatory control, the business analyst should identify the applicable obligations, understand the control’s purpose, and determine whether the proposed change continues to satisfy the required conditions. Failure to address regulatory requirements can create significant consequences. Programming languages, meeting frequency, and interface consistency may be relevant to other aspects of solution evaluation but do not establish regulatory compliance. Compliance analysis should be based on the applicable obligations and evidence of adherence.<\/span><\/p>\n

                    Question 350: A stakeholder strongly supports one solution alternative and dismisses another without reviewing the evidence. What should the business analyst do?<\/b><\/p>\n

                      \n
                    1. <\/b> Accept the stakeholder’s preferred alternative because of their experience<\/span><\/li>\n
                    2. <\/b> Remove the preferred alternative from consideration<\/span><\/li>\n
                    3. <\/b> Facilitate comparison using agreed evaluation criteria and relevant evidence<\/span><\/li>\n
                    4. <\/b> Select the alternative with the lowest implementation cost<\/span><\/li>\n<\/ol>\n

                      Correct Answer: 3. Facilitate comparison using agreed evaluation criteria and relevant evidence<\/b><\/p>\n

                      Explanation:<\/b>
                      \n<\/b>The business analyst should support objective comparison of alternatives using criteria relevant to the business need. Evaluation criteria may include value, cost, risk, feasibility, strategic alignment, timing, dependencies, and organizational impacts. Stakeholder experience is valuable input, but a preferred alternative should still be evaluated against the agreed criteria and available evidence. Automatically accepting or rejecting an option can introduce bias into the decision process. A structured comparison makes trade-offs visible and provides decision-makers with information needed to select an appropriate alternative.<\/span><\/p>\n

                      Question 351: During requirements validation, stakeholders discover that an important business rule has an exception that was not documented. What should the business analyst do?<\/b><\/p>\n

                        \n
                      1. <\/b> Remove the business rule entirely<\/span><\/li>\n
                      2. <\/b> Document and validate the exception, including its conditions and expected outcomes<\/span><\/li>\n
                      3. <\/b> Ignore the exception because it occurs infrequently<\/span><\/li>\n
                      4. <\/b> Allow developers to determine how the exception should behave<\/span><\/li>\n<\/ol>\n

                        Correct Answer: 2. Document and validate the exception, including its conditions and expected outcomes<\/b><\/p>\n

                        Explanation:<\/b>
                        \n<\/b>Business rule exceptions can materially affect solution behavior even when they occur infrequently. The business analyst should identify the conditions under which the exception applies, the expected outcome, responsible parties, and any related constraints or dependencies. The exception should then be validated with appropriate stakeholders. Ignoring it may lead to incorrect solution behavior, while removing the entire rule may eliminate an important business control. Developers can help implement the rule, but the business meaning and expected outcome should be established and validated through business analysis.<\/span><\/p>\n

                        Question 352: A business analyst is determining whether a proposed solution can be supported after implementation. Which factors are most relevant?<\/b><\/p>\n

                          \n
                        1. <\/b> Operational resources, skills, support capabilities, processes, and constraints<\/span><\/li>\n
                        2. <\/b> The number of pages in the requirements document<\/span><\/li>\n
                        3. <\/b> The stakeholder with the largest organizational title<\/span><\/li>\n
                        4. <\/b> The visual design of the project presentation<\/span><\/li>\n<\/ol>\n

                          Correct Answer: 1. Operational resources, skills, support capabilities, processes, and constraints<\/b><\/p>\n

                          Explanation:<\/b>
                          \n<\/b>Operational feasibility concerns whether the organization can successfully operate and support the proposed solution. Relevant factors include available resources, required skills, support processes, responsibilities, infrastructure, operating procedures, and constraints. A solution may be technically possible but difficult to operate if the organization lacks the necessary capabilities or support structure. Document length, organizational title, and presentation design do not establish operational feasibility. The business analyst should identify operational gaps and determine whether they can be addressed through changes, training, staffing, process improvements, or other appropriate measures.<\/span><\/p>\n

                          Question 353: A business analyst is asked to prioritize requirements when resources are limited. Stakeholders disagree about which requirements should be implemented first. What should guide the prioritization?<\/b><\/p>\n

                            \n
                          1. <\/b> The order in which stakeholders submitted their requests<\/span><\/li>\n
                          2. <\/b> The personal preference of the project manager<\/span><\/li>\n
                          3. <\/b> The length of each requirement<\/span><\/li>\n
                          4. <\/b> Agreed criteria such as value, urgency, risk, dependencies, and constraints<\/span><\/li>\n<\/ol>\n

                            Correct Answer: 4. Agreed criteria such as value, urgency, risk, dependencies, and constraints<\/b><\/p>\n

                            Explanation:<\/b>
                            \n<\/b>Prioritization should be based on criteria that reflect business objectives and the circumstances of the initiative. Common factors include expected value, urgency, risk reduction, regulatory obligations, dependencies, implementation constraints, and strategic alignment. Agreeing on the criteria before evaluating requirements helps reduce arbitrary prioritization and makes trade-offs transparent. Submission order, requirement length, or an individual’s preference does not necessarily reflect business importance. The business analyst should facilitate a structured prioritization approach and ensure that relevant stakeholders understand how the criteria are being applied.<\/span><\/p>\n

                            Question 354: A business analyst wants to determine why customers repeatedly abandon a process at the same step. What should the analyst investigate?<\/b><\/p>\n

                              \n
                            1. <\/b> Only the number of employees supporting the process<\/span><\/li>\n
                            2. <\/b> The common causes, conditions, barriers, and evidence associated with that step<\/span><\/li>\n
                            3. <\/b> Only the color of the screen used at that step<\/span><\/li>\n
                            4. <\/b> Whether the process documentation is stored in the correct folder<\/span><\/li>\n<\/ol>\n

                              Correct Answer: 2. The common causes, conditions, barriers, and evidence associated with that step<\/b><\/p>\n

                              Explanation:<\/b>
                              \n<\/b>Repeated abandonment at the same point suggests that common factors may be affecting customer behavior. The business analyst should investigate the conditions surrounding that step, such as usability barriers, unclear information, business rules, waiting time, required effort, missing options, or other process characteristics. Data and stakeholder evidence can help determine which factors contribute to the problem. Focusing only on staffing, visual design, or documentation storage would provide an incomplete analysis. Understanding the underlying causes is necessary before selecting an appropriate improvement or solution.<\/span><\/p>\n

                              Question 355: An organization changes its strategic priorities while requirements are still being analyzed. What should the business analyst do?<\/b><\/p>\n

                                \n
                              1. <\/b> Continue using the original priorities without review<\/span><\/li>\n
                              2. <\/b> Immediately discard all existing requirements<\/span><\/li>\n
                              3. <\/b> Revalidate requirements against the updated objectives, needs, and expected value<\/span><\/li>\n
                              4. <\/b> Freeze stakeholder participation until implementation<\/span><\/li>\n<\/ol>\n

                                Correct Answer: 3. Revalidate requirements against the updated objectives, needs, and expected value<\/b><\/p>\n

                                Explanation:<\/b>
                                \n<\/b>Changes in strategic priorities can affect the relevance and value of requirements that were previously considered important. The business analyst should reassess requirements against the updated objectives, business needs, expected outcomes, dependencies, and constraints. Some requirements may remain valid, while others may need reprioritization, modification, or removal. Automatically retaining or discarding all requirements would ignore the specific effects of the strategic change. Revalidation helps ensure that analysis remains aligned with the organization’s current direction rather than relying on assumptions that are no longer valid.<\/span><\/p>\n

                                Question 356: A proposed solution depends on an assumption about future customer behavior. What should the business analyst do?<\/b><\/p>\n

                                  \n
                                1. <\/b> Identify the assumption, assess its uncertainty, and determine its potential impact<\/span><\/li>\n
                                2. <\/b> Treat the assumption as a confirmed business fact<\/span><\/li>\n
                                3. <\/b> Remove all requirements related to customer behavior<\/span><\/li>\n
                                4. <\/b> Ignore the assumption until after implementation<\/span><\/li>\n<\/ol>\n

                                  Correct Answer: 1. Identify the assumption, assess its uncertainty, and determine its potential impact<\/b><\/p>\n

                                  Explanation:<\/b>
                                  \n<\/b>Assumptions can influence solution feasibility, expected benefits, risks, and requirements. When a solution depends on future customer behavior, the business analyst should explicitly identify the assumption, determine how uncertain it is, and assess what could happen if it proves incorrect. Where practical, the assumption should be validated using evidence or appropriate analysis. Treating an assumption as fact can create hidden risk, while ignoring it delays recognition of a potentially significant issue. Making assumptions visible allows stakeholders to understand their implications and determine appropriate mitigation or validation activities.<\/span><\/p>\n

                                  Question 357: A business analyst needs to represent several possible outcomes based on multiple conditions and exceptions. Which model is particularly appropriate?<\/b><\/p>\n

                                    \n
                                  1. <\/b> Stakeholder map<\/span><\/li>\n
                                  2. <\/b> Decision table<\/span><\/li>\n
                                  3. <\/b> Capability map<\/span><\/li>\n
                                  4. <\/b> Context diagram<\/span><\/li>\n<\/ol>\n

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

                                    Explanation:<\/b>
                                    \n<\/b>A decision table is useful when a business rule contains multiple conditions and corresponding outcomes. It provides a structured way to represent combinations of conditions, actions, and exceptions and helps stakeholders identify missing or contradictory rule combinations. A capability map describes organizational abilities, a stakeholder map represents stakeholder relationships, and a context diagram shows the boundary and interactions of a solution with external entities. For complex rule logic involving multiple conditions and outcomes, a decision table provides a clear and systematic representation that can support validation and testing.<\/span><\/p>\n

                                    Question 358: A stakeholder asks the business analyst to approve a requirement even though the stakeholder does not have approval authority. What should the business analyst do?<\/b><\/p>\n

                                      \n
                                    1. <\/b> Approve it because the stakeholder requested it<\/span><\/li>\n
                                    2. <\/b> Ask a developer to approve it instead<\/span><\/li>\n
                                    3. <\/b> Record the requirement as approved without identifying an approver<\/span><\/li>\n
                                    4. <\/b> Identify the authorized decision-maker and obtain the appropriate approval<\/span><\/li>\n<\/ol>\n

                                      Correct Answer: 4. Identify the authorized decision-maker and obtain the appropriate approval<\/b><\/p>\n

                                      Explanation:<\/b>
                                      \n<\/b>Approval should come from the stakeholder or authority responsible for making the relevant decision. The business analyst can facilitate validation, clarify information, and manage the requirements process, but should not substitute personal judgment for established decision rights. Identifying the authorized decision-maker ensures that the requirement has appropriate accountability and governance. Recording an unauthorized approval can create confusion and governance problems later. The analyst should therefore confirm who has authority to approve the requirement and ensure that the decision and its status are properly documented.<\/span><\/p>\n

                                      Question 359: A solution is delivered on time and within budget, but users continue using the old process. What should the business analyst investigate?<\/b><\/p>\n

                                        \n
                                      1. <\/b> Only whether the project schedule was accurate<\/span><\/li>\n
                                      2. <\/b> Only whether the solution met its technical specifications<\/span><\/li>\n
                                      3. <\/b> Adoption barriers, user needs, training, process impacts, and organizational readiness<\/span><\/li>\n
                                      4. <\/b> Whether the requirements document contained enough pages<\/span><\/li>\n<\/ol>\n

                                        Correct Answer: 3. Adoption barriers, user needs, training, process impacts, and organizational readiness<\/b><\/p>\n

                                        Explanation:<\/b>
                                        \n<\/b>Delivery within time and budget does not guarantee that users will adopt a solution or that it will achieve its expected outcomes. Continued use of the old process may indicate insufficient training, usability problems, unclear benefits, process conflicts, lack of support, resistance to change, or other organizational readiness issues. The business analyst should investigate these factors using stakeholder feedback and appropriate evidence. Technical completion and schedule performance are important project measures, but they do not by themselves demonstrate successful adoption or business value realization.<\/span><\/p>\n

                                        Question 360: A business analyst reviews the results of several initiatives to improve the organization’s analysis practices. What is the most useful outcome of this review?<\/b><\/p>\n

                                          \n
                                        1. <\/b> A list of every requirement created across the initiatives<\/span><\/li>\n
                                        2. <\/b> A comparison of project budgets only<\/span><\/li>\n
                                        3. <\/b> A record of which stakeholder had the most meetings<\/span><\/li>\n
                                        4. <\/b> Identified patterns, lessons learned, successful practices, recurring challenges, and improvement opportunities<\/span><\/li>\n<\/ol>\n

                                          Correct Answer: 4. Identified patterns, lessons learned, successful practices, recurring challenges, and improvement opportunities<\/b><\/p>\n

                                          Explanation:<\/b>
                                          \n<\/b>Reviewing multiple initiatives can reveal patterns that are difficult to see from a single project. The business analyst can identify recurring challenges, successful approaches, stakeholder engagement practices, analysis techniques, decision-making issues, and opportunities for process improvement. These findings can be used to improve organizational business analysis practices and future initiatives. A simple inventory of requirements, budgets, or meetings does not explain why certain approaches worked or failed. The most valuable outcome is actionable organizational knowledge that can be applied to improve future analysis activities and outcomes.<\/span><\/p>\n

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

                                          View Full IIBA CBAP Exam Dumps and Practice Test Dumps   Question 341: A business analyst is asked to determine whether a proposed initiative addresses a valid business need. Which information should be examined first? The preferred technology platform The project team’s previous experience The problem or opportunity, desired outcomes, and organizational objectives The number […]<\/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\/20646"}],"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=20646"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/20646\/revisions"}],"predecessor-version":[{"id":20647,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/20646\/revisions\/20647"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=20646"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=20646"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=20646"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}