{"id":22347,"date":"2026-09-25T12:25:02","date_gmt":"2026-09-25T12:25:02","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=22347"},"modified":"2026-09-25T12:25:02","modified_gmt":"2026-09-25T12:25:02","slug":"pmi-pmi-pba-practice-test-questions-and-exam-dumps-part1-q1-20","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/pmi-pmi-pba-practice-test-questions-and-exam-dumps-part1-q1-20\/","title":{"rendered":"PMI PMI-PBA Practice Test Questions and Exam Dumps Part1 Q1-20"},"content":{"rendered":"

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

 <\/p>\n

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

A business analyst is beginning an initiative to replace an organization’s legacy customer management system. What should the business analyst do first to understand why the initiative is needed?<\/b><\/p>\n

    \n
  1. <\/b> Create detailed functional requirements<\/span>
    \n<\/span>2.<\/b> Evaluate the current business situation, problem, and organizational objectives<\/span>
    \n<\/span>3.<\/b> Develop test cases for the proposed system<\/span>
    \n<\/span>4.<\/b> Obtain final solution acceptance<\/span><\/li>\n<\/ol>\n

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

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

    Before defining detailed requirements, the business analyst should understand the business need that triggered the initiative. This involves examining the current situation, identifying problems or opportunities, and understanding relevant organizational objectives. Establishing this context helps ensure that later requirements address genuine business needs rather than prematurely focusing on a particular solution. Functional requirements, testing, and acceptance activities occur later. A clear understanding of the problem also provides a foundation for defining objectives, evaluating potential solution approaches, identifying stakeholders, and establishing meaningful success criteria.<\/span><\/p>\n

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

    A business analyst needs to identify stakeholders who may influence or be affected by a new business process. What is the most appropriate approach?<\/b><\/p>\n

      \n
    1. <\/b> Perform stakeholder analysis to identify roles, interests, influence, and impact<\/span>
      \n<\/span>2.<\/b> Interview only the project sponsor<\/span>
      \n<\/span>3.<\/b> Wait until stakeholders contact the project team<\/span>
      \n<\/span>4.<\/b> Include only people who will use the final system directly<\/span><\/li>\n<\/ol>\n

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

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

      Stakeholder analysis helps identify individuals and groups who influence, are affected by, or have an interest in the initiative. The analysis can consider authority, influence, expectations, expertise, communication needs, and the degree of impact from the proposed change. Focusing only on direct users can overlook sponsors, regulators, operational teams, customers, suppliers, support personnel, and other important stakeholders. Early identification allows the business analyst to select appropriate engagement and communication approaches and reduces the likelihood that significant requirements or concerns will emerge unexpectedly later.<\/span><\/p>\n

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

      During an elicitation workshop, two stakeholder groups provide conflicting requirements. What should the business analyst do?<\/b><\/p>\n

        \n
      1. <\/b> Select the requirement from the more senior stakeholder automatically<\/span>
        \n<\/span>2.<\/b> Document only the requirement that is easier to implement<\/span>
        \n<\/span>3.<\/b> Explore the underlying needs and facilitate resolution based on business objectives and agreed criteria<\/span>
        \n<\/span>4.<\/b> Remove both requirements from consideration<\/span><\/li>\n<\/ol>\n

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

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

        Conflicting requirements often arise because stakeholders have different objectives, constraints, assumptions, or perspectives. The business analyst should understand the underlying need behind each position and facilitate discussion using relevant business objectives, priorities, constraints, and decision criteria. Authority may influence final decisions, but automatically choosing the most senior stakeholder’s preference can overlook important business impacts. The analyst’s role includes helping stakeholders reach a transparent resolution and documenting the resulting decision, assumptions, and implications so the requirement set remains coherent.<\/span><\/p>\n

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

        A requirement has been approved, but a stakeholder requests a significant modification during solution development. What should the business analyst do?<\/b><\/p>\n

          \n
        1. <\/b> Implement the modification immediately<\/span>
          \n<\/span>2.<\/b> Reject the request because approved requirements can never change<\/span>
          \n<\/span>3.<\/b> Ask the development team to decide whether to accept it<\/span>
          \n<\/span>4.<\/b> Analyze the requested change and its impacts using the established change-control process<\/span><\/li>\n<\/ol>\n

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

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

          Requirements can change after approval, but significant modifications should be evaluated systematically. The business analyst should understand the reason for the request and analyze its potential impact on scope, objectives, dependencies, schedule, cost, risks, and other requirements. The change should then follow the initiative’s established governance and approval process. Automatically implementing the request can create uncontrolled scope growth, while automatically rejecting it can prevent valuable adjustments. Controlled change management allows stakeholders to make informed decisions using a clear understanding of consequences.<\/span><\/p>\n

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

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

            \n
          1. <\/b> To connect requirements with their origins, related requirements, solution components, and verification or validation information<\/span>
            \n<\/span>2.<\/b> To prevent requirements from ever changing<\/span>
            \n<\/span>3.<\/b> To replace stakeholder communication<\/span>
            \n<\/span>4.<\/b> To document only rejected requirements<\/span><\/li>\n<\/ol>\n

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

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

            Requirements traceability establishes relationships among business needs, requirements, design or solution elements, testing, and other relevant artifacts. These relationships help the business analyst understand the effects of proposed changes and verify that approved business needs are addressed by the resulting solution. Traceability can also help identify requirements that lack a clear business justification or solution coverage. It does not prevent changes; instead, it makes changes easier to analyze. Effective traceability supports scope management, impact analysis, verification, validation, and solution evaluation throughout the initiative.<\/span><\/p>\n

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

            A business analyst wants to understand how employees currently perform a complex operational process. Which elicitation technique is particularly useful when actual work may differ from documented procedures?<\/b><\/p>\n

              \n
            1. <\/b> Surveying senior executives only<\/span>
              \n<\/span>2.<\/b> Observation of employees performing the process<\/span>
              \n<\/span>3.<\/b> Reviewing the future-state architecture<\/span>
              \n<\/span>4.<\/b> Performing solution acceptance testing<\/span><\/li>\n<\/ol>\n

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

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

              Observation allows the business analyst to see how work is actually performed in the operational environment. This can reveal informal workarounds, exceptions, dependencies, manual steps, and practical constraints that may not appear in written procedures or interviews. Employees sometimes perform tasks differently from documented processes because operational conditions have evolved. Observation can therefore complement interviews and document analysis. The analyst should consider whether being observed could influence behavior and may need to validate findings with participants to ensure that the observed process is representative.<\/span><\/p>\n

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

              A business analyst has elicited a large number of requirements, but stakeholders disagree about which should be implemented first. What should the analyst do?<\/b><\/p>\n

                \n
              1. <\/b> Prioritize requirements alphabetically<\/span>
                \n<\/span>2.<\/b> Implement requirements in the order they were discovered<\/span>
                \n<\/span>3.<\/b> Facilitate prioritization using agreed factors such as business value, risk, dependencies, urgency, and implementation considerations<\/span>
                \n<\/span>4.<\/b> Assign every requirement the same priority<\/span><\/li>\n<\/ol>\n

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

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

                Requirements prioritization should reflect factors that matter to the initiative rather than arbitrary ordering. Business value, risk, regulatory urgency, dependencies, cost, implementation difficulty, stakeholder impact, and time sensitivity can all influence priority. The business analyst should help stakeholders establish suitable criteria and apply them consistently. Dependencies are particularly important because a high-value requirement may rely on foundational capabilities that must be delivered first. Transparent prioritization helps stakeholders understand trade-offs and directs limited resources toward the requirements that best support project and organizational objectives.<\/span><\/p>\n

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

                During requirements review, the business analyst discovers that one requirement can be interpreted in several different ways. What should be done?<\/b><\/p>\n

                  \n
                1. <\/b> Leave the wording unchanged and allow developers to interpret it<\/span>
                  \n<\/span>2.<\/b> Create several implementations and select one later<\/span>
                  \n<\/span>3.<\/b> Remove the requirement automatically<\/span>
                  \n<\/span>4.<\/b> Clarify and revise the requirement so its intended meaning is sufficiently unambiguous<\/span><\/li>\n<\/ol>\n

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

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

                  Ambiguous requirements can lead different stakeholders, designers, developers, and testers to reach different conclusions about what must be delivered. The business analyst should clarify the intended meaning with appropriate stakeholders and revise the requirement using precise language, models, examples, acceptance criteria, or other techniques as appropriate. Requirements should be understandable enough to support consistent interpretation. Discovering ambiguity during review is valuable because resolving it before implementation generally costs less than correcting a solution built from an incorrect interpretation.<\/span><\/p>\n

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

                  A business analyst is evaluating whether a proposed solution addresses the organization’s original business need. Which activity is most relevant?<\/b><\/p>\n

                    \n
                  1. <\/b> Solution evaluation against expected business outcomes and success measures<\/span>
                    \n<\/span>2.<\/b> Requirements elicitation only<\/span>
                    \n<\/span>3.<\/b> Stakeholder identification only<\/span>
                    \n<\/span>4.<\/b> Meeting scheduling<\/span><\/li>\n<\/ol>\n

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

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

                    Solution evaluation examines whether an implemented or proposed solution delivers the expected value and addresses the underlying business need. The business analyst can compare actual or expected performance with defined objectives, key performance indicators, acceptance measures, and desired outcomes. A solution may technically satisfy documented requirements yet still fail to generate the intended business value. Evaluation therefore extends beyond confirming individual features. It helps determine whether performance gaps exist, whether assumptions remain valid, and whether additional changes may be required to realize expected benefits.<\/span><\/p>\n

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

                    A project sponsor asks the business analyst to recommend a solution before stakeholder needs have been adequately investigated. What should the analyst do?<\/b><\/p>\n

                      \n
                    1. <\/b> Recommend the sponsor’s preferred technology immediately<\/span>
                      \n<\/span>2.<\/b> Clarify the business need and relevant requirements before evaluating solution options<\/span>
                      \n<\/span>3.<\/b> Ask the vendor to define the organization’s requirements<\/span>
                      \n<\/span>4.<\/b> Select the least expensive product without additional analysis<\/span><\/li>\n<\/ol>\n

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

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

                      Selecting a solution before understanding the underlying need can result in requirements being shaped around a predetermined product rather than business objectives. The analyst should clarify the problem or opportunity, stakeholder needs, constraints, and desired outcomes before comparing solution alternatives. This does not mean every detail must be known before options are considered, but sufficient business context is necessary for meaningful evaluation. A needs-based approach helps distinguish essential capabilities from preferences and provides objective criteria for comparing potential solutions.<\/span><\/p>\n

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

                      A business analyst wants to visually represent the sequence of activities, decisions, and handoffs within an existing business process. Which technique is most appropriate?<\/b><\/p>\n

                        \n
                      1. <\/b> Stakeholder register<\/span>
                        \n<\/span>2.<\/b> Risk register<\/span>
                        \n<\/span>3.<\/b> Process model or process flow diagram<\/span>
                        \n<\/span>4.<\/b> Product roadmap only<\/span><\/li>\n<\/ol>\n

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

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

                        A process model visually represents how work flows through activities, decisions, roles, events, and handoffs. It can help stakeholders understand the current state, identify inefficiencies, expose missing steps, and discuss potential future-state improvements. Visual models are particularly useful when textual descriptions become difficult to follow. The business analyst should validate the model with knowledgeable stakeholders to ensure it accurately reflects the process. Stakeholder and risk registers serve different purposes and do not provide the same representation of operational workflow.<\/span><\/p>\n

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

                        A requirement is technically feasible but does not support any identified business objective or stakeholder need. What should the business analyst do?<\/b><\/p>\n

                          \n
                        1. <\/b> Approve it because it is technically feasible<\/span>
                          \n<\/span>2.<\/b> Give it the highest priority<\/span>
                          \n<\/span>3.<\/b> Implement it before other requirements<\/span>
                          \n<\/span>4.<\/b> Challenge its necessity and determine whether sufficient business justification exists<\/span><\/li>\n<\/ol>\n

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

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

                          A requirement should normally have a clear connection to a business need, stakeholder need, regulatory obligation, risk response, or other legitimate project objective. Technical feasibility alone does not establish business value. The analyst should investigate why the requirement exists and determine whether it can be traced to an appropriate source or objective. If no valid justification exists, stakeholders can decide whether it should be removed or deprioritized. This helps prevent unnecessary scope and ensures resources remain focused on outcomes that contribute meaningful value.<\/span><\/p>\n

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

                          Why should a business analyst define acceptance criteria for requirements?<\/b><\/p>\n

                            \n
                          1. <\/b> To establish observable conditions that can help determine whether the requirement has been satisfactorily met<\/span>
                            \n<\/span>2.<\/b> To eliminate the need for stakeholder involvement<\/span>
                            \n<\/span>3.<\/b> To guarantee that the solution contains no defects<\/span>
                            \n<\/span>4.<\/b> To prevent all future requirement changes<\/span><\/li>\n<\/ol>\n

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

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

                            Acceptance criteria clarify the conditions that should be satisfied for stakeholders to consider a requirement or solution element acceptable. Well-defined criteria reduce ambiguity and provide useful input for development, verification, validation, and testing. They can also reveal misunderstandings while requirements are still being analyzed. Acceptance criteria do not guarantee a defect-free solution, nor do they eliminate stakeholder involvement. Instead, they create a shared and testable understanding of expected outcomes, making later evaluation more objective and reducing disagreement about whether a requirement has been fulfilled.<\/span><\/p>\n

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

                            A business analyst is preparing for an elicitation session with stakeholders who have very limited availability. What should the analyst do?<\/b><\/p>\n

                              \n
                            1. <\/b> Conduct the meeting without an objective or agenda<\/span>
                              \n<\/span>2.<\/b> Define the elicitation objectives, identify needed information, select suitable techniques, and prepare focused questions<\/span>
                              \n<\/span>3.<\/b> Invite everyone in the organization regardless of relevance<\/span>
                              \n<\/span>4.<\/b> Use the session only to present a completed solution<\/span><\/li>\n<\/ol>\n

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

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

                              Effective elicitation benefits from deliberate preparation, particularly when stakeholder availability is limited. The analyst should determine what information is needed, which participants can provide it, and which techniques will make the best use of available time. Preparing focused questions, relevant background information, models, or agendas helps participants engage productively. The analyst should also understand the desired outcome of the session. Preparation reduces unnecessary discussion and increases the likelihood that critical information, decisions, assumptions, and follow-up actions are captured efficiently.<\/span><\/p>\n

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

                              Stakeholders approve a requirement based on an assumption that a third-party service will support a specific capability. The assumption has not been verified. What should the business analyst do?<\/b><\/p>\n

                                \n
                              1. <\/b> Treat the assumption as confirmed because the requirement was approved<\/span>
                                \n<\/span>2.<\/b> Remove the third-party dependency from documentation<\/span>
                                \n<\/span>3.<\/b> Document and validate the assumption and assess the impact if it proves incorrect<\/span>
                                \n<\/span>4.<\/b> Wait until implementation fails before investigating it<\/span><\/li>\n<\/ol>\n

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

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

                                Unverified assumptions can introduce significant requirements and solution risk. The analyst should make the assumption visible, identify who can validate it, and determine what happens if it proves false. In this scenario, confirming the third-party capability may affect feasibility, scope, cost, schedule, or solution design. Requirement approval does not automatically validate every underlying assumption. Explicit assumption management allows the project team to investigate uncertainty early and develop alternatives or responses before the dependency becomes a costly implementation problem.<\/span><\/p>\n

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

                                A business analyst is reviewing requirements and finds two statements that specify incompatible outcomes for the same business rule. What should the analyst do?<\/b><\/p>\n

                                  \n
                                1. <\/b> Keep both and let developers choose<\/span>
                                  \n<\/span>2.<\/b> Delete both requirements<\/span>
                                  \n<\/span>3.<\/b> Implement whichever requirement was documented first<\/span>
                                  \n<\/span>4.<\/b> Analyze the conflict with relevant stakeholders and establish the authoritative requirement<\/span><\/li>\n<\/ol>\n

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

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

                                  Requirements should form a consistent set. When two requirements define incompatible outcomes, the analyst should identify the source of the conflict and engage the appropriate stakeholders to resolve it. Business rules, policies, regulations, objectives, and decision authority may help determine the correct outcome. The resolution should be documented and related requirements updated so downstream teams receive consistent direction. Leaving the decision to developers transfers a business decision to people who may not have the necessary authority or context.<\/span><\/p>\n

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

                                  What is an important reason for maintaining requirements version information?<\/b><\/p>\n

                                    \n
                                  1. <\/b> It helps stakeholders identify the current requirement and understand how it has changed over time.<\/span>
                                    \n<\/span>2.<\/b> It prevents authorized changes from occurring.<\/span>
                                    \n<\/span>3.<\/b> It eliminates the need for requirement approval.<\/span>
                                    \n<\/span>4.<\/b> It allows all versions to be used simultaneously.<\/span><\/li>\n<\/ol>\n

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

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

                                    Requirements can evolve as stakeholders gain information, priorities change, or approved changes occur. Version control helps distinguish current authorized requirements from superseded ones and provides useful history regarding modifications. Without it, different teams may unknowingly design, build, or test against inconsistent information. Version information supports traceability, impact analysis, audits, and communication. It does not prevent changes; rather, it helps ensure that authorized changes are controlled and that participants understand which requirement definition should currently guide their work.<\/span><\/p>\n

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

                                    A business analyst needs feedback from several hundred geographically dispersed users about a relatively standardized set of questions. Which elicitation technique is most suitable?<\/b><\/p>\n

                                      \n
                                    1. <\/b> Individual observation of every user<\/span>
                                      \n<\/span>2.<\/b> Survey or questionnaire<\/span>
                                      \n<\/span>3.<\/b> Daily executive workshop<\/span>
                                      \n<\/span>4.<\/b> Prototype testing before identifying the questions<\/span><\/li>\n<\/ol>\n

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

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

                                      Surveys and questionnaires can efficiently collect structured information from a large, geographically distributed stakeholder population. They are particularly useful when the analyst can formulate clear questions and wants comparable responses from many participants. Surveys may provide less depth than interviews, so follow-up techniques can be used where responses reveal areas requiring further investigation. The analyst should design questions carefully to avoid ambiguity or bias and should consider whether the respondents adequately represent the stakeholder population whose needs are being analyzed.<\/span><\/p>\n

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

                                      A proposed solution satisfies all mandatory functional requirements but creates an unacceptable regulatory compliance risk. What should the business analyst do?<\/b><\/p>\n

                                        \n
                                      1. <\/b> Recommend acceptance because functional requirements are satisfied<\/span>
                                        \n<\/span>2.<\/b> Ignore compliance because it is not a functional feature<\/span>
                                        \n<\/span>3.<\/b> Identify and communicate the compliance gap and evaluate necessary changes before recommending acceptance<\/span>
                                        \n<\/span>4.<\/b> Remove regulatory requirements from the project scope<\/span><\/li>\n<\/ol>\n

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

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

                                        Solution suitability is not determined solely by functional behavior. Regulatory, legal, security, operational, quality, and other nonfunctional constraints can be essential to business acceptance. The analyst should identify the compliance gap, understand its consequences, and work with relevant stakeholders to determine required corrective action. A solution that performs required functions but exposes the organization to unacceptable compliance risk may not satisfy the broader business need. Evaluation should therefore consider the complete set of applicable requirements and constraints.<\/span><\/p>\n

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

                                        An implemented solution meets its documented requirements, but expected business benefits are not being achieved. What should the business analyst do?<\/b><\/p>\n

                                          \n
                                        1. <\/b> Conclude that the initiative is successful because requirements were delivered<\/span>
                                          \n<\/span>2.<\/b> Rewrite the original benefits to match actual performance<\/span>
                                          \n<\/span>3.<\/b> Stop measuring business outcomes<\/span>
                                          \n<\/span>4.<\/b> Analyze the performance gap, underlying causes, assumptions, adoption factors, and potential improvement options<\/span><\/li>\n<\/ol>\n

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

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

                                          Delivering documented requirements does not automatically guarantee realization of expected business value. The analyst should compare actual outcomes with established success measures and investigate why the anticipated benefits are not occurring. Causes might include incorrect assumptions, inadequate adoption, process issues, training gaps, external changes, incomplete capabilities, or poorly defined original requirements. Understanding the cause allows stakeholders to evaluate appropriate corrective actions or additional changes. Business analysis continues beyond requirement delivery when necessary to determine whether the solution is producing the intended organizational outcomes.<\/span><\/p>\n

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

                                          View Full PMI PMI-PBA Exam Dumps and Practice Test Dumps   Question 1. A business analyst is beginning an initiative to replace an organization’s legacy customer management system. What should the business analyst do first to understand why the initiative is needed? Create detailed functional requirements 2. Evaluate the current business situation, problem, and organizational […]<\/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\/22347"}],"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=22347"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/22347\/revisions"}],"predecessor-version":[{"id":22348,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/22347\/revisions\/22348"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=22347"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=22347"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=22347"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}