Practice Flashcards
7 cards from real B.S.W.E. Bachelor of Software Engineering practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Practice flashcards as text
Which software metric measures the percentage of source code executed by a test suite?
Answer: Code coverage
Code coverage measures what fraction of lines, branches, or paths are exercised by automated tests, helping identify untested code.
A developer notices that three classes all duplicate the same 20-line validation logic. Which refactoring best addresses this?
Answer: Move Method to a new shared utility class
Moving the duplicated validation to a shared utility class eliminates repetition and ensures a single point of maintenance for that logic.
In agile sprint planning, what does 'velocity' represent?
Answer: The average amount of work completed in past sprints
Velocity is the average number of story points (or units of work) a team completes per sprint, used to forecast future delivery.
Which design pattern allows new behaviors to be added to objects at runtime without altering their class?
Answer: Decorator
The Decorator pattern wraps objects in additional decorator objects, adding behavior dynamically while keeping the original class unchanged.
What is the primary purpose of a staging environment in a software delivery pipeline?
Answer: To mirror production for final validation before release
A staging environment replicates production conditions so teams can validate releases, run integration tests, and catch issues before going live.
Which technique decomposes a monolithic system by assigning each bounded domain context to its own independently deployable service?
Answer: Microservices architecture
Microservices architecture breaks a system into small services aligned to bounded contexts, each deployable and scalable independently.
A pull request shows a method that catches a generic Exception and silently swallows it. What risk does this introduce?
Answer: Hidden failures that become impossible to diagnose
Swallowing exceptions hides errors silently, preventing logging, alerting, and proper error handling, making bugs extremely difficult to diagnose.