FC0-U71 Software Development Concepts Practice Question
A quality assurance team is executing system testing on a new banking application. They need to verify that the entire application works correctly from start to finish. Which THREE of the following testing types would be included in system testing?
⚠ Common exam trap
The trap is including integration or unit testing as part of system testing — candidates conflate the levels of the V-model, but system testing only begins after integration is complete and the full application is assembled.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Security testing
System testing validates the complete, integrated application against its requirements, so Security testing (A) is included because it verifies authentication, authorization, encryption, and protection against vulnerabilities across the whole banking system. Functional testing (C) is included because it confirms end-to-end business functions and requirements work correctly from start to finish. Performance testing (E) is included because it assesses responsiveness, throughput, scalability, and stability of the fully integrated application under load. Integration testing (B) is not part of system testing because it focuses on interfaces between combined units/modules and is performed earlier at the integration level. Unit testing (D) is not included because it tests individual components or functions in isolation, typically done by developers before integration.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Security testing
Why this is correct
System testing validates the complete, integrated application against requirements, and security testing examines authentication, authorisation, encryption and vulnerability handling across that whole system. It therefore belongs within end-to-end system testing rather than unit or component-level verification.
- ✗
Integration testing
Why it's wrong here
Integration testing verifies interfaces between combined components and occurs before system testing begins; system testing then validates the complete integrated application end to end. It is tempting because integration is a broader test level, but it is a distinct preceding phase, not a type contained within system testing.
- ✓
Functional testing
Why this is correct
Functional testing validates that each feature behaves according to its requirements, so it forms part of system testing's end-to-end verification of the banking application's business workflows. It confirms the complete application functions correctly from start to finish, matching the stem's scope.
- ✗
Unit testing
Why it's wrong here
Unit testing validates individual functions or methods in isolation and is performed by developers before components are combined, so it cannot form part of system testing. It is tempting because unit tests are a recognised testing type, but they sit at the lowest level, well below whole-application verification.
- ✓
Performance testing
Why this is correct
Performance testing measures responsiveness, throughput and stability under load, which system testing includes to verify the whole application meets non-functional requirements. It exercises the integrated banking system end to end, satisfying the stem's demand that the entire application work correctly.
Go deeper
Related to this question
About these practice questions
One of 988 original FC0-U71 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
2 more ways this is tested on FC0-U71
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. During the SDLC, testing is performed at different levels. Which TWO of the following are recognized levels of testing? (Select TWO.)
easy- A.Maintenance
- B.Code review
- ✓ C.Integration testing
- ✓ D.Unit testing
- E.Deployment
Why C: Integration testing (C) is a recognized level of testing in the SDLC, sitting between unit and system testing, where individual modules are combined and tested as a group to verify interfaces and interactions between components. Unit testing (D) is also a recognized level, focusing on verifying the smallest testable parts of an application, such as individual functions or methods, in isolation. These two are standard levels in the classic testing hierarchy (unit, integration, system, acceptance). Maintenance (A) is an SDLC phase that follows deployment, not a testing level. Code review (B) is a static verification technique or peer-review activity, not a defined test level. Deployment (E) is a release/implementation phase, not a testing level.
Variation 2. A software testing team is planning to verify a new e-commerce application. Which THREE testing types should be performed to ensure comprehensive quality? (Select the three correct answers.)
hard- A.Smoke testing
- ✓ B.Integration testing
- ✓ C.Unit testing
- D.Alpha testing
- ✓ E.System testing
Why B: Integration testing (B) is correct because it verifies that the individually developed modules and interfaces of the e-commerce application communicate and exchange data correctly (e.g., checkout service calling the payment gateway API), which is essential for a multi-component system. Unit testing (C) is correct because it validates the smallest testable pieces of code, such as individual functions or classes, in isolation, catching defects early before they propagate into higher-level testing. System testing (E) is correct because it evaluates the fully integrated application end-to-end against its specified requirements, covering complete business flows like browsing, cart, checkout, and order confirmation in a production-like environment. Smoke testing (A) is not among the marked answers because it is a shallow build-verification technique rather than one of the three comprehensive quality-assurance levels, and alpha testing (D) is not marked because it is a user-acceptance activity performed by internal users at the developer's site, not a core functional testing type for verifying the application's quality.
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CompTIA exam blueprint
This FC0-U71 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the FC0-U71 exam.