New 2024 PSPO-I Dumps for Professional Scrum Product Owner Certified Exam Questions and Answer
Realistic Verified PSPO-I exam dumps Q&As - PSPO-I Free Update
NEW QUESTION # 78
Why is the Daily Scrum held at the same time and same place?
(choose the best answer)
- A. Rooms are hard to book and must be booked in advance.
- B. The Product Owner demands it.
- C. The place can be named.
- D. The consistency reduces complexity.
Answer: D
Explanation:
The Daily Scrum is held at the same time and same place because:
The consistency reduces complexity. By having a fixed time and place for the Daily Scrum, the Developers can avoid wasting time and energy on scheduling, logistics, or coordination issues. They can also establish a routine and a rhythm that helps them focus on their work and their Sprint Goal.
The consistency increases transparency. By having a fixed time and place for the Daily Scrum, the Developers can ensure that everyone is aware of when and where the meeting takes place, and that everyone has an opportunity to participate and share their progress, plans, and challenges. They can also invite other stakeholders or observers, if they find it useful, to provide feedback or support.
The consistency enhances collaboration. By having a fixed time and place for the Daily Scrum, the Developers can create a safe and comfortable space for them to communicate, interact, and collaborate with each other. They can also build trust, rapport, and accountability among themselves, and foster a sense of team spirit and ownership.
Reference:
Scrum Guide 2020, page 12: "The Daily Scrum is held at the same time and place each day to reduce complexity." Scrum Guide 2020, page 12: "The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work." Scrum Guide 2020, page 13: "The Daily Scrum is an internal meeting for the Developers. If others are present, the Scrum Master ensures that they do not disrupt the meeting."
NEW QUESTION # 79
Select typical responsibilities of a Scrum Master to serve the organization.
- A. Working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization.
- B. Adapting the Scrum terms and events in a way that it fits the organization.
- C. Leading and coaching the organization in its Scrum adoption.
- D. Helping employees and stakeholders understand and enact Scrum and empirical product development.
Answer: A,C,D
NEW QUESTION # 80
The Product Owner is the person who will be held accountable if a product does not achieve its goals or deliver value. Does this mean that the Product Owner has the final say over the Definition of Done?
(choose the best answer)
- A. No, the Scrum Team decides the Definition of Done, if it is not a standard of the organization. The Product Owner is just one member of the Scrum Team.
- B. Yes, the Product Owner decides the Definition of Done. The Developers may be consulted.
Answer: A
Explanation:
Explanation
* The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. The Definition of Done is used to assess when work is complete on the product Increment.
* The Definition of Done is defined by the Scrum Team, not by the Product Owner alone. The Scrum Team consists of one Product Owner, one Scrum Master, and Developers. They are all accountable for creating a valuable, useful, and potentially releasable product Increment each Sprint.
* The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner is responsible for managing and refining the Product Backlog, collaborating with the stakeholders and the Developers, and ordering the items in a way that best achieves goals and missions. The Product Owner represents the interests of everyone with a stake in the product and ensures that the Scrum Team works on the right things at the right time.
* The Developers are accountable for creating a "Done" Increment that meets the Definition of Done each Sprint. The Developers are responsible for planning and executing the Sprint Backlog, designing and building the product functionality, testing and improving the product quality, and delivering a potentially releasable Increment. The Developers work closely with the Product Owner to understand
* and clarify the Product Backlog items, provide feedback and estimates, and suggest improvements and innovations.
* The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. The Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide. The Scrum Master does this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization.
* The Definition of Done may vary from one Scrum Team to another, depending on the context and domain of work. However, it must be consistent within one team. If there are multiple Scrum Teams working on one product, they must share a common Definition of Done. If there is an organizational standard for a Definition of Done, all Scrum Teams must follow it as a minimum.
References:
* Scrum Guide: https://www.scrumguides.org/scrum-guide.html
* Definition of Done: https://www.scrum.org/resources/what-is-a-definition-of-done
* Product Owner: https://www.scrum.org/resources/what-is-a-product-owner
* Developers: https://www.scrum.org/resources/what-is-a-developer-in-scrum
* Scrum Master: https://www.scrum.org/resources/what-is-a-scrum-master
NEW QUESTION # 81
Which of the following is correct about the Product Vision?
- A. It helps the Product Owner to decide when the product is releasable.
- B. It is an old concept and overall not recommended.
- C. It gives an overall direction to all Sprints, makes it easier to prioritize Product Backlog items and helps the team to stay focused.
Answer: C
NEW QUESTION # 82
True or False: A Product Owner should measure product value by the increase in the team's velocity.
- A. False
- B. True
Answer: A
Explanation:
A Product Owner should not measure product value by the increase in the team's velocity. This is because:
Velocity is a measure of how much work a Scrum Team can deliver in a Sprint. It is based on the estimation of Product Backlog items that are selected for a Sprint and completed according to the Definition of Done.
Velocity is not a measure of product value. It does not reflect how well the product meets the needs and expectations of the customers, users, and stakeholders. It does not reflect how much value or impact the product creates in terms of revenue, satisfaction, or social good.
Velocity is not a goal or a target for a Scrum Team. It is a planning tool that helps them forecast their future work based on their past performance. It is not a metric that should be used to compare or judge teams or individuals.
A Product Owner should measure product value by using indicators that are relevant, meaningful, and actionable for their product context. These may include metrics such as customer feedback, usage data, market share, return on investment, or social impact.
Reference:
[Scrum Guide], page 7, section "Developers"
[Scrum Guide], page 10, section "Definition of Done"
[Scrum Guide], page 15, section "Sprint Backlog"
[Professional Scrum Product Owner Training], page 5, section "Product Value"
[Professional Scrum Product Owner Training], page 9, section "Business Strategy"
NEW QUESTION # 83
When can Developers cancel a Sprint?
(choose the best answer)
- A. When the selected Product Backlog items for the Sprint become unachievable.
- B. When a technical dependency cannot be resolved.
- C. They cannot. Only Product Owners can cancel Sprints.
- D. When functional expectations are not well understood.
- E. When the Product Owner is absent too often.
Answer: C
Explanation:
According to the Scrum Guide, a Sprint can be canceled before the Sprint time-box is over. Only the Product Owner has the authority to cancel the Sprint, although he or she may do so under influence from the stakeholders, the Developers, or the Scrum Master. A Sprint would be canceled if the Sprint Goal becomes obsolete. This might occur if the company changes direction or if market or technology conditions change. In general, a Sprint should be canceled if it no longer makes sense given the circumstances. But, due to the short duration of Sprints, cancellation rarely makes sense. Developers cannot cancel a Sprint on their own, even if they face challenges or difficulties with the selected Product Backlog items, the functional expectations, the technical dependencies, or the Product Owner's availability. Instead, they should collaborate with the Product Owner and the Scrum Master to find the best way to deliver value within the Sprint and adapt to the changing situation.
References:
* The Scrum Guide
* Understanding and Applying the Scrum Framework
* Professional Scrum Product Owner™ I Certification
NEW QUESTION # 84
True or False: The value delivered by a product can only be determined by revenue.
- A. False
- B. True
Answer: A
Explanation:
Explanation
The value delivered by a product can not be determined by revenue alone, because:
* Revenue is only one aspect of value, and it may not reflect the true impact or benefit of the product for the stakeholders, the users, and the society. For example, a product may generate high revenue, but also cause environmental damage, ethical issues, or customer dissatisfaction.
* Value is a subjective and relative concept, and it may vary depending on the context, the perspective, and the criteria of the evaluation. For example, a product may have different value for different segments of customers, or for different markets or regions.
* Value is dynamic and emergent, and it may change over time due to various factors, such as feedback, competition, innovation, or regulation. For example, a product may lose its value as new alternatives or solutions become available, or as customer needs or preferences evolve.
References:
* Scrum Guide 2020, page 6: "The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team."
* Scrum Guide 2020, page 11: "The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against."
* Scrum Guide 2020, page 11: "The Product Owner is accountable for effective Product Backlog management, which includes ... optimizing the value of the work the Scrum Team performs."
NEW QUESTION # 85
What is a Product Owner typically responsible for during a Sprint?
(choose the best two answers)
- A. Working with the Scrum Team on Product Backlog refinement.
- B. Creating financial reporting upon the spent hours reported by the Developers.
- C. Updating the work plan for the Developers on a daily basis.
- D. Collaborating with stakeholders, users, and customers.
- E. Nothing.
- F. Attending every Daily Scrum to answer questions about the Sprint Backlog items.
Answer: A,D
Explanation:
Explanation
* The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner is responsible for managing and refining the Product Backlog, collaborating with the stakeholders and the Developers, and ordering the items in a way that best achieves goals and missions. The Product Owner represents the interests of everyone with a stake in the product and ensures that the Scrum Team works on the right things at the right time.
* A Sprint is a timebox of one month or less within which a "Done" product Increment is created. A Sprint consists of the Sprint Planning, Daily Scrums, the development work, the Sprint Review, and the Sprint Retrospective. A Sprint is also a feedback loop that allows the Scrum Team and the stakeholders to inspect and adapt the product and the process.
* During a Sprint, a Product Owner is typically responsible for:
* Collaborating with stakeholders, users, and customers: The Product Owner engages in frequent and regular interactions with the people who have a stake or interest in the product, such as customers, users, sponsors, managers, or other teams. The Product Owner solicits and incorporates their input, feedback, and insights to understand their needs and expectations, discover new opportunities or ideas, align and collaborate on the product direction and priorities, and validate and deliver value to them.
* Working with the Scrum Team on Product Backlog refinement: The Product Owner works closely with the Developers to clarify, refine, and review the Product Backlog items and their acceptance criteria. The Product Owner provides clear and concise descriptions of what is needed and why it is valuable for each Product Backlog item. The Product Owner also empowers and trusts the Developers to make technical decisions and trade-offs that best meet the product goals and quality standards. The Product Owner also involves key stakeholders in defining and prioritizing the Product Backlog items and their acceptance criteria.
* The other options are not valid or relevant responsibilities of a Product Owner during a Sprint. They are either too administrative, micromanaging, or unrelated to the product value delivery. They are:
* Creating financial reporting upon the spent hours reported by the Developers: This is not a responsibility of a Product Owner during a Sprint. This is an administrative task that does not contribute to the value or quality of the product or service delivered. It may also create unnecessary overhead or bureaucracy for the Developers. The Product Owner should focus on maximizing value rather than tracking hours.
* Updating the work plan for the Developers on a daily basis: This is not a responsibility of a Product Owner during a Sprint. This is a micromanaging task that does not respect the self-organization or cross-functionality of the Developers. The Developers are responsible for planning and executing their own work during a Sprint, based on their empirical experience and collaboration. The Developers also update their progress daily during the Daily Scrum event.
* Nothing: This is not a valid answer for a Product Owner's responsibility during a Sprint. A Product Owner has many important responsibilities during a Sprint, as mentioned above. A Product Owner should be actively involved in collaborating with stakeholders, users, customers, and Developers throughout a Sprint to maximize value delivery.
* Attending every Daily Scrum to answer questions about the Sprint Backlog items: This is not a mandatory responsibility of a Product Owner during a Sprint. The Daily Scrum is an event for the Developers to inspect their progress toward the Sprint Goal and adapt their plan for the next 24
* hours. The Daily Scrum is not a status meeting or a reporting session for anyone else. The Product Owner may attend the Daily Scrum as an observer or as an invited participant if they have something valuable to contribute or if they need some clarification from the Developers.
References:
* Scrum Guide: https://www.scrumguides.org/scrum-guide.html
* Product Owner: https://www.scrum.org/resources/what-is-a-product-owner
* Sprint: https://www.scrum.org/resources/what-is-a-sprint-in-scrum
* Stakeholders: https://www.agilealliance.org/glossary/stakeholders
* Daily Scrum: https://www.scrum.org/resources/what-is-a-daily-scrum
NEW QUESTION # 86
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team.
- A. TRUE
- B. FALSE
Answer: A
NEW QUESTION # 87
Who determines how many Product Backlog items the Developers select for a Sprint?
(choose the best answer)
- A. The stakeholders attending Sprint Planning.
- B. The Product Owner.
- C. The Scrum Master.
- D. The Developers.
- E. The Scrum Team
Answer: D
Explanation:
The Developers are the ones who determine how many Product Backlog items they select for a Sprint. The Developers are self-managing and decide how much work they can do in a Sprint1. The Product Owner and the Developers collaborate on the scope of the Sprint during Sprint Planning, but the final decision is up to the Developers2. The Product Owner, the Scrum Master, and the stakeholders do not have the authority to tell the Developers how many Product Backlog items they should select, as this would violate the principle of self-management[3][3].
References:
1: The Scrum Guide, November 2020, p. 6
2: The Scrum Guide, November 2020, p. 10
[3][3]: Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023
NEW QUESTION # 88
True or False: During the Sprint Review the stakeholder's role is to reorder the Product Backlog.
- A. False
- B. True
Answer: A
Explanation:
Explanation
During the Sprint Review, the stakeholder's role is not to reorder the Product Backlog, but rather to provide feedback and suggestions on the product and the process. Therefore, the answer is false because:
* The Sprint Review is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration. The stakeholders are invited to attend the Sprint Review as observers, participants, or customers, and they can share their opinions, ideas, or requests regarding the product and its features, functionality, quality, value, etc.
* The ordering of the Product Backlog is the sole responsibility of the Product Owner. They order Product Backlog items to best achieve goals and missions. The Product Owner may consider the feedback and suggestions from the stakeholders, as well as other factors such as dependencies, risks, costs, etc., when ordering the Product Backlog. However, they are not obliged to follow or implement them.
* The Product Backlog is not a fixed or final list of requirements, but rather an emergent and dynamic artifact that represents all the possible changes to the product. The Product Owner is accountable for effective Product Backlog management, which includes refining, communicating, and optimizing the Product Backlog items. The Product Owner may update the Product Backlog at any time, not only during the Sprint Review.
References:
* Scrum Guide 2020, page 11: "The ordering of the items in the Product Backlog is the sole responsibility of the Product Owner."
* Scrum Guide 2020, page 11: "The Product Owner is accountable for effective Product Backlog management, which includes ... ordering Product Backlog items; and ensuring that the Product Backlog is transparent, visible and understood."
* Scrum Guide 2020, page 15: "The Sprint Review is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration."
NEW QUESTION # 89
The Product Owner is not available and cannot answer the developers questions before the Sprint Planning. Therefore, the developers feel a high level of uncertainty to make a reliable forecast .
What should the team do?
- A. The Sprint Planning meeting should be cancelled or postponed.
- B. Extend the duration of the current Sprint and try to answer all questions.
- C. The developers should make a best guess and should not worry too much.
- D. The upcoming Sprint should be cancelled.
Answer: C
NEW QUESTION # 90
What is the timebox for the Sprint Review?
(choose the best answer)
- A. As long as needed.
- B. 4 hours for a one-month Sprint.
- C. 2 hours for a one-month Sprint.
- D. 1 day.
Answer: B
Explanation:
Explanation
The timebox for the Sprint Review is four hours for a one-month Sprint. This is because:
* The Sprint Review is an event where the Scrum Team and stakeholders inspect the Increment and adapt the Product Backlog if needed. The purpose of the Sprint Review is to elicit feedback and foster collaboration.
* The timebox for each Scrum event is proportional to its frequency and duration. A one-month Sprint corresponds to a maximum calendar month.
* The timebox for a one-month Sprint Review is four hours. For shorter Sprints, it is usually shorter.
* The timebox ensures that there is enough time to inspect what has been done in relation to what could be done next and make any necessary adaptations to optimize value.
Other options, such as two hours for a one-month Sprint, one day, or as long as needed, are not valid answers as they do not reflect the correct timebox for the Sprint Review.
References:
* [Scrum Guide], page 17, section "Sprint Review"
* [Scrum Guide], page 9, section "Sprint"
* [Scrum Guide], page 9, section "Timeboxing Scrum Events"
NEW QUESTION # 91
What is the main reason for the Product Owner to be part of the Daily Scrum?
- A. To track the progress of the Project.
- B. It is not required for the Product Owner to participate.
- C. To assign the Developers the daily tasks.
Answer: B
NEW QUESTION # 92
A Scrum Team member should take over both accountabilities Scrum Master and Product Owner.
- A. TRUE
- B. FALSE
Answer: B
NEW QUESTION # 93
True or False: All planned work for the Product done by the Scrum Team must originate from the Product Backlog.
- A. True
- B. False
Answer: A
Explanation:
* The Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of truth for the Scrum Team and the stakeholders. It contains all the requirements, features, functions, enhancements, fixes, and anything else that can deliver value to the customers and users of the product.
* The Product Owner is accountable for managing and refining the Product Backlog, collaborating with the stakeholders and the Developers, and ordering the items in a way that best achieves goals and missions. The Product Owner represents the interests of everyone with a stake in the product and ensures that the Scrum Team works on the right things at the right time.
* The Developers are accountable for creating a "Done" Increment that meets the Definition of Done each Sprint. The Developers are responsible for planning and executing the Sprint Backlog, designing and building the product functionality, testing and improving the product quality, and delivering a potentially releasable Increment. The Developers work closely with the Product Owner to understand and clarify the Product Backlog items, provide feedback and estimates, and suggest improvements and innovations.
* All planned work for the Product done by the Scrum Team must originate from the Product Backlog.
The Scrum Team does not work on anything that is not in the Product Backlog. The Scrum Team does not add or remove anything from the Product Backlog without consulting with the Product Owner. The
* Scrum Team does not accept or implement any requests or changes that are not in the Product Backlog.
The Scrum Team does not create any other artifacts or documents that are not derived from or related to the Product Backlog.
References:
* Scrum Guide: https://www.scrumguides.org/scrum-guide.html
* Product Backlog: https://www.scrum.org/resources/what-is-a-product-backlog
* Product Owner: https://www.scrum.org/resources/what-is-a-product-owner
* Developers: https://www.scrum.org/resources/what-is-a-developer-in-scrum
NEW QUESTION # 94
What are two effective ways for the Scrum Team to make non-functional requirements visible?
(choose the best two answers)
- A. Put them on a separate list on the Scrum board, available for all to see.
- B. Add them to the Product Backlog to ensure transparency.
- C. Add them to the Definition of Done so the work is taken care of every Sprint.
- D. Run the integration and regression tests before the end of the Sprint, and capture the open work for the Sprint Backlog of the next Sprint.
Answer: B,C
Explanation:
Explanation
Non-functional requirements are the criteria that define the quality, performance, security, usability, and other aspects of a product1. They are often implicit or assumed, but they are important to make visible and explicit, as they affect the value and satisfaction of the product2. One effective way to make non-functional requirements visible is to add them to the Product Backlog, which is an ordered list of everything that is known to be needed in the product[3][3]. By adding non-functional requirements to the Product Backlog, the Product Owner and the Developers can prioritize, refine, and estimate them, and make them transparent to the stakeholders4. Another effective way to make non-functional requirements visible is to add them to the Definition of Done, which is a shared understanding of what it means for work to be complete, and ensures transparency of the quality of the work done5. By adding non-functional requirements to the Definition of Done, the Developers can ensure that every Product Backlog item and Increment meets the expected quality standards, and that the work is taken care of every Sprint.
References:
1: Non-functional requirement, Wikipedia, accessed on December 16, 2023
2: Managing Products with Agility, Scrum.org, accessed on December 16, 2023
[3][3]: The Scrum Guide, November 2020, p. 6
4: The Scrum Guide, November 2020, p. 7
5: The Scrum Guide, November 2020, p. 13
Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023
NEW QUESTION # 95
What are two effective ways for a Scrum Team to ensure security concerns are satisfied? (choose the best two answers)
- A. Add a Sprint to specifically resolve all security concerns.
- B. Add security concerns to the Definition of Done.
- C. Have the Scrum Team create Product Backlog items for each concern.
- D. Delegate the work to the security department.
- E. Postpone the work until a specialist can perform a security audit and create a list of security-related Product Backlog items.
Answer: B,C
Explanation:
These are the best answers because they ensure that security concerns are addressed in a transparent and consistent way. By adding security criteria to the Definition of Done, the Scrum Team can make sure that every Increment meets a high standard of quality and security. By creating Product Backlog items for specific security concerns, the Scrum Team can prioritize and plan them in collaboration with the Product Owner and stakeholders. Reference:
Scrum Guide, page 14: "The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product." Scrum Guide, page 15: "The Product Backlog is an emergent, ordered list of what is needed to improve the product."
NEW QUESTION # 96
How many Developers are recommended in one Scrum Team?
- A. 1-9
- B. 3-10
- C. 3-9
Answer: C
NEW QUESTION # 97
Who creates the Definition of Done?
(choose the best answer)
- A. The Product Owner
- B. The Developers
- C. The Scrum Master
- D. The Scrum Team
Answer: D
Explanation:
The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. The Definition of Done is created by the Scrum Team, not just the Developers. The Scrum Team must have a shared understanding of what it means for work to be complete, to ensure transparency. The Definition of Done is used to assess when work is complete on the product Increment. The Definition of Done may vary significantly per Scrum Team, depending on the context. The Definition of Done evolves over time and is updated whenever the Scrum Team learns more about the product and the environment in which it operates.
Reference:
The Scrum Guide
Understanding and Applying the Scrum Framework
Professional Scrum Product Owner I Certification
NEW QUESTION # 98
Product Backlog refinement should be done during the Sprint.
- A. TRUE
- B. FALSE
Answer: A
NEW QUESTION # 99
Which of the following are criteria to order Product Backlog items?
(choose all that apply)
- A. Dependencies between Product Backlog items.
- B. Value of Product Backlog items.
- C. The availability of the Scrum Master.
- D. All of the above.
- E. Dependencies to other products.
Answer: A,B,E
Explanation:
Explanation
The Product Owner orders the Product Backlog items according to various criteria, such as:
The value of Product Backlog items. The Product Owner aims to maximize the value of the product and the work of the Scrum Team. Therefore, they prioritize the items that deliver the most value to the stakeholders and the users, considering factors such as customer satisfaction, market share, revenue, social impact, etc.
The dependencies between Product Backlog items. The Product Owner tries to minimize the dependencies between items, as they may create complexity, uncertainty, and risk. Therefore, they order the items in a way that reduces or eliminates the dependencies, or resolves them as early as possible.
The dependencies to other products. The Product Owner also considers the dependencies that the product has to other products, such as platforms, frameworks, libraries, services, etc. Therefore, they order the items in a way that aligns with the availability and compatibility of those products.
References:
Scrum Guide 2020, page 11: "The Product Owner is accountable for effective Product Backlog management, which includes ... ordering Product Backlog items; and, ensuring that the Product Backlog is transparent, visible and understood." Scrum Guide 2020, page 11: "The ordering of the items in the Product Backlog is the sole responsibility of the Product Owner. They order Product Backlog items to best achieve goals and missions." Scrum Guide 2020, page 11: "Higher ordered Product Backlog items are clearer and more refined than lower ordered ones."
NEW QUESTION # 100
The Scrum Team consists of one Scrum Master, one Product Owner, and Developers.
- A. TRUE
- B. FALSE
Answer: A
NEW QUESTION # 101
The Daily Scrum is a formal opportunity to inspect and adapt Scrum artifacts.
- A. TRUE
- B. FALSE
Answer: A
NEW QUESTION # 102
......
Use Real PSPO-I Dumps - 100% Free PSPO-I Exam Dumps: https://www.examdumpsvce.com/PSPO-I-valid-exam-dumps.html
PSPO-I Exam Dumps, Test Engine Practice Test Questions: https://drive.google.com/open?id=1FywVca4-j3hlUUMh22v5-qvWA3Oamkq0
