Skip to main content

SDLC Interactive Mock Test

SDLC Interactive Mock Test SDLC Mock Test: Test Your Software Development Knowledge Instructions:

There are 40 multiple-choice questions.
Each question has only one correct answer.
The passing score is 65% (26 out of 40).
Recommended time: 60 minutes.

SDLC Mock Test: Test Your Software Development Knowledge

1. Which phase of the SDLC focuses on understanding and documenting what the system should do?

2. In which SDLC model are phases completed sequentially, with no overlap?

3. What is the primary goal of the Design phase in SDLC?

4. Which SDLC model emphasizes iterative development and frequent collaboration with customers?

5. What is 'Unit Testing' primarily concerned with?

6. Which phase involves writing the actual code based on the design specifications?

7. What is a key characteristic of the Maintenance phase in SDLC?

8. Which SDLC model is best suited for projects with unclear requirements that are likely to change?

9. What is 'Integration Testing' concerned with?

10. In the V-Model, which testing phase corresponds to the Requirements Gathering phase?

11. What is the primary purpose of a Feasibility Study in the initial phase of SDLC?

12. Which document is typically produced during the Requirements Gathering phase?

13. What does CI/CD stand for in the context of modern SDLC practices?

14. Which SDLC model is characterized by its emphasis on risk management and iterative refinement?

15. What is the primary output of the Implementation/Coding phase?

16. Which of the following is a non-functional requirement?

17. What is the purpose of 'User Acceptance Testing' (UAT)?

18. Which SDLC phase typically involves creating flowcharts, data models, and architectural diagrams?

19. What is the main characteristic of a 'prototype' in software development?

20. What is the purpose of 'Version Control Systems' (e.g., Git) in SDLC?

21. Which SDLC model is known for its high risk in large projects due to late defect discovery?

22. What is the 'Deployment' phase of the SDLC?

23. Which of the following is a benefit of adopting DevOps practices in SDLC?

24. What is a 'Sprint' in the Scrum Agile framework?

25. Which SDLC model is a sequential design process in which progress is seen as flowing steadily downwards (like a waterfall) through phases?

26. What is the primary purpose of a 'System Requirements Specification' (SRS)?

27. Which SDLC model includes distinct phases for risk analysis and prototyping at each iteration?

28. What is 'Refactoring' in the context of software development?

29. Which phase of the SDLC involves monitoring the system for performance, security, and user feedback after deployment?

30. What is a 'backlog' in Agile methodologies?

31. Which of the following is a benefit of using an Iterative SDLC model?

32. What is the role of a 'System Analyst' in the SDLC?

33. Which SDLC model explicitly links each development phase with a corresponding testing phase?

34. What is 'Scrum'?

35. What is the primary purpose of a 'Daily Stand-up' meeting in Agile?

36. Which SDLC phase would typically involve creating a 'Test Plan'?

37. What is the concept of 'Technical Debt' in software development?

38. Which of the following is a common challenge in the Requirements Gathering phase?

39. What is the purpose of a 'Post-Implementation Review'?

40. Which of the following best describes 'DevOps'?

Your Score: 0 / 40

Labels:

Comments

Post a Comment

Popular posts from this blog

How to Inspect Disappearing Elements Using "Emulate a Focused Page" in Chrome DevTools

As web developers, we often encounter frustrating scenarios where elements like dropdowns, tooltips, or custom select menus vanish the moment we try to inspect them in Chrome DevTools. This happens because these elements are often designed to disappear when they lose focus or the mouse moves away. Fortunately, Chrome DevTools provides a powerful feature called "Emulate a focused page" that lets you freeze the page's focus state, making it much easier to debug these elusive elements. The Challenge of Disappearing Elements 👻 Imagine you're styling a complex navigation menu with sub-menus that appear on hover. When you try to right-click and "Inspect" one of these sub-menus, it vanishes! This is a classic example of an element losing its active state because DevTools gains focus, causing the element's blur or focusout event to trigger its disappearance. Traditional methods like trying to quickly click and inspect often fail, leading to wasted time and f...
Post a Comment
Read more

Supercharging QA: How Playwright MCP Agents Are Transforming Test Automation

 In automated browser testing, QA teams spend a massive chunk of their engineering cycles doing two things: writing repetitive locator boilerplates and fixing flaky tests broken by minor UI changes. The arrival of the Model Context Protocol (MCP) and Microsoft’s official Playwright MCP Server changes that dynamic. By turning browser automation into a structured interface for AI agents, test generation and maintenance are shifting from manual step-by-step coding to intent-driven execution. What is Playwright MCP? The Model Context Protocol (MCP) is an open standard designed to let AI systems interact seamlessly with external databases, APIs, and tools. The Playwright MCP Server exposes Playwright’s browser context directly to an AI agent (such as Cursor, Claude Code, or custom LLM test runners). Rather than forcing the AI to guess coordinates from screenshots or parse raw, noisy DOM trees, Playwright MCP feeds the model structured accessibility snapshots. [ AI Agent / LLM ] <---...
Post a Comment
Read more

Mastering Waits in Playwright: The Art of Synchronizing Your Automation

Web applications are rarely static. Data loads asynchronously, elements animate in and out, and pages navigate. This dynamic nature means your automation script needs to be smart enough to wait for the application to be ready before interacting with it. Without proper waiting strategies, your tests will consistently break with "element not found," "element not clickable," or "timeout" errors. Playwright offers a sophisticated suite of waiting capabilities, ranging from intelligent auto-waiting for actions to explicit waits for specific network events, page loads, or custom conditions. Understanding and utilizing these waits effectively is fundamental to writing reliable and robust Playwright tests. Playwright's Core Philosophy: Intelligent Auto-Waiting The most significant departure Playwright makes from older automation tools is its built-in auto-waiting mechanism. For nearly all actions (like click() , fill() , check() , selectOption() , etc.), Play...
Post a Comment
Read more