




























































































Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Focuses on Scrum implementation in front-end and full-stack web development environments. Topics include sprint-based web development workflows, user experience integration, code review practices, responsive design refinement, and collaborative delivery. The exam features real-world web development challenges aligned with Scrum practices.
Typology: Exams
1 / 119
This page cannot be seen from the preview
Don't miss anything!





























































































Question 1. Which Scrum value emphasizes delivering a functional web increment over exhaustive documentation? A) Courage B) Focus C) Working software D) Respect Answer: C Explanation: The Scrum value “Working software” (or “working web increment”) stresses that the primary measure of progress is functional, usable code, not the amount of documentation produced. Question 2. In Scrum, who is accountable for the Sprint Backlog? A) Product Owner B) Scrum Master C) Development Team D) Stakeholders Answer: C Explanation: The Development Team owns the Sprint Backlog, continuously updating it as they learn more about the work needed to achieve the Sprint Goal. Question 3. Which of the following best describes the Definition of Done (DoD) for a web developer?
A) Only unit tests passed B) Code merged to master branch C) Cross‑browser compatibility, security scan passed, performance benchmark met, and all acceptance criteria satisfied D) Feature demoed to the Product Owner Answer: C Explanation: The DoD for web work must include technical quality criteria such as cross‑browser support, security checks, and performance targets, in addition to functional acceptance. Question 4. A developer estimates a PBI using Planning Poker and assigns a 5 ‑point value. What does this point value represent? A) Number of hours required B) Relative effort and complexity compared to other PBIs C) Priority level of the item D) Number of team members needed Answer: B Explanation: Story points are a relative measure of effort, complexity, and uncertainty, not a direct time estimate. Question 5. Which practice helps a web developer keep the codebase clean and maintainable?
C) End‑to‑end test D) Integration test Answer: D Explanation: Integration tests validate the interaction between components such as a REST API and its data layer, ensuring correct responses. Question 8. Which Git branching strategy encourages short‑lived feature branches merged directly into the main line? A) Gitflow B) Trunk‑based development C) Release branching D) Feature toggles only Answer: B Explanation: Trunk‑based development uses a single main branch (trunk) with short‑lived feature branches that are merged quickly, supporting continuous integration. Question 9. What is the primary purpose of a pull request (PR) in a Scrum team’s CI workflow? A) To automatically deploy to production B) To enforce code review and quality gates before merging C) To assign tasks to developers
D) To generate user stories Answer: B Explanation: PRs provide a mechanism for peer review, automated checks, and discussion before code is merged, ensuring quality and shared knowledge. Question 10. Which CI step should run immediately after a code commit to catch compilation errors early? A) Deployment to staging B) Static code analysis and linting C) Load testing D) User acceptance testing Answer: B Explanation: Running static analysis and linting early detects syntax and style issues before the code proceeds to later stages. Question 11. Which of the following is a common web performance bottleneck? A. Using HTTPS B. Large unoptimized images C. Minified JavaScript D. HTTP/2 protocol Answer: B
Question 14. During Sprint Planning, how does a developer contribute to capacity planning? A) By setting the Sprint Goal alone B) By estimating personal availability and any planned time off C) By assigning story points to the Product Owner D) By deciding the order of the Product Backlog items Answer: B Explanation: Developers provide realistic capacity data, including work hours and any vacations, helping the team forecast achievable work. Question 15. In the Daily Scrum, a developer should primarily discuss: A) Detailed design decisions for future sprints B) Progress toward the Sprint Goal and any impediments C) Personal performance reviews D) New product ideas unrelated to current work Answer: B Explanation: The Daily Scrum is a short coordination meeting focused on current progress and obstacles affecting the Sprint Goal. Question 16. Which activity during Product Backlog Refinement helps address technical debt? A) Adding new user stories without estimation
B) Prioritizing only business value items C) Creating dedicated “technical debt” backlog items and estimating them D) Removing all unfinished tasks from the Sprint Backlog Answer: C Explanation: Explicitly creating and estimating technical‑debt items ensures they are visible, prioritized, and addressed in future sprints. Question 17. A “spike” in Scrum is used for: A) Delivering a high‑value feature quickly B) Conducting research or prototyping to reduce uncertainty C. Measuring team velocity D. Conducting a retrospective Answer: B Explanation: Spikes are time‑boxed investigations that provide knowledge needed for accurate estimation or technical decisions. Question 18. During a Sprint Review, a developer should: A) Only answer questions from the Scrum Master B) Demonstrate the working Increment, highlighting technical quality and user value C. Rewrite the Definition of Done
Explanation: The Scrum of Scrums is a coordination meeting where representatives discuss inter‑team dependencies and integration challenges. Question 21. Which visualization technique helps a Scrum of Scrums track shared API dependencies? A. Gantt chart B. Dependency matrix C. Burn‑down chart D. Kanban board Answer: B Explanation: A dependency matrix clearly shows which teams rely on which APIs, facilitating risk identification and planning. Question 22. When implementing WCAG 2.1 AA level, a developer should: A. Use only inline CSS B. Add appropriate ARIA roles and ensure semantic HTML structure C. Disable JavaScript for accessibility D. Rely solely on visual design tools Answer: B Explanation: ARIA attributes and semantic HTML provide assistive technologies with the necessary context to meet accessibility standards.
Question 23. Which Jira issue type is most appropriate for a research spike? A. Bug B. Epic C. Task D. Story Answer: C Explanation: A “Task” can represent a time‑boxed research activity (spike) that does not deliver user‑visible value but informs future work. Question 24. An information radiator in Scrum is best described as: A. A private email thread for the team B. A visible board or chart that displays real‑time progress metrics to all stakeholders C. A confidential performance review document D. A secret backlog item Answer: B Explanation: Information radiators (e.g., task boards, burn‑down charts) provide transparent, easily accessible status information. Question 25. Which document is considered part of “Done” for a new API endpoint? A. High‑level marketing brochure
D. Authority Answer: B Explanation: Self‑management means the Development Team decides how to accomplish the Sprint Goal without external direction. Question 28. Which of the following best illustrates a T‑shaped skill set for a web developer? A. Expertise only in backend Java services B. Ability to work on frontend, backend, DevOps, and database tasks, with deep expertise in one area C. Knowledge of only UI design tools D. Specialization in network hardware Answer: B Explanation: A T‑shaped developer has broad knowledge across the stack (the horizontal bar) and deep expertise in at least one domain (the vertical stem). Question 29. When breaking down a large PBI into tasks, a developer should aim for tasks that: A. Take an entire sprint to complete B. Are small enough to be completed within a day and deliverable incrementally C. Require multiple developers to finish D. Are vague to allow flexibility
Answer: B Explanation: Small, daily‑sized tasks improve predictability, enable daily progress tracking, and reduce risk. Question 30. Which of the following is a key responsibility of a developer when collaborating with the Product Owner? A. Writing user stories for the Product Owner B. Defining acceptance criteria and clarifying technical feasibility C. Deciding release dates alone D. Managing stakeholder communications Answer: B Explanation: Developers work with the Product Owner to ensure acceptance criteria are clear, testable, and technically realistic. Question 31. During a Sprint, a developer discovers a security vulnerability that was not part of the original DoD. The appropriate action is: A. Ignore it until the next sprint B. Raise the issue immediately, update the DoD if needed, and address it within the current sprint if possible C. Wait for the Scrum Master to assign it D. File a bug and close it without fixing Answer: B
Question 34. Which HTTP header helps protect against XSS attacks? A. Content-Type B. X-Content-Type-Options C. X-XSS-Protection D. Cache-Control Answer: C Explanation: The X-XSS-Protection header enables the browser’s built‑in XSS filter, mitigating reflected XSS attacks. Question 35. When a developer uses feature flags to hide incomplete functionality, they are practicing: A. Continuous integration B. Technical debt reduction C. Trunk‑based development with safe releases D. Waterfall planning Answer: C Explanation: Feature flags allow code to be merged to the main branch while keeping unfinished features disabled, supporting continuous delivery. Question 36. In a Scrum team, who is responsible for removing impediments that are outside the Development Team’s control? A. Product Owner
B. Scrum Master C. Development Team lead D. Stakeholder Answer: B Explanation: The Scrum Master facilitates the removal of impediments, especially those beyond the team’s direct authority. Question 37. Which metric is most useful for a developer to assess whether the Sprint Goal was met? A. Number of story points completed B. Velocity trend over the last five sprints C. Functional demonstration of the Increment against the Sprint Goal D. Burn‑up chart of total backlog size Answer: C Explanation: The Sprint Goal is a qualitative target; confirming that the Increment satisfies it determines success. Question 38. A developer notices that the build time has increased dramatically after adding a new library. The best first action is: A. Remove the library without discussion B. Optimize the CI pipeline by caching dependencies and parallelizing tasks C. Increase the sprint length
Explanation: ARIA labels provide assistive technologies with descriptive information, enhancing accessibility. Question 41. Which of the following is a characteristic of a “self‑organizing” Development Team? A. The Scrum Master assigns tasks daily B. Team members decide how to accomplish work without external direction C. The Product Owner dictates the technical design D. Management sets individual performance targets Answer: B Explanation: Self‑organization means the team determines the best way to meet the Sprint Goal autonomously. Question 42. A developer uses a static code analysis tool that flags “unused variables.” This practice supports which Scrum principle? A. Commitment B. Transparency C. Focus D. Courage Answer: B Explanation: Static analysis makes hidden issues visible, increasing transparency of code quality.
Question 43. In a multi‑team environment, what is the purpose of a “shared definition of done”? A. To allow each team to define its own quality standards B. To ensure all teams produce increments that are truly releasable and interoperable C. To reduce the need for integration testing D. To eliminate the need for a Scrum Master Answer: B Explanation: A shared DoD guarantees that each team’s Increment meets common quality and integration criteria, enabling seamless product integration. Question 44. Which practice helps a developer keep the Sprint Backlog up to date? A. Updating tasks only at the end of the sprint B. Adding new tasks without consulting the team C. Daily updating of task status during the Daily Scrum D. Ignoring changes in scope Answer: C Explanation: Frequent updates keep the Sprint Backlog accurate, reflecting real progress and any emerging work.