Difficulty: Easy
Correct Answer: Microsoft's Access
Explanation:
Introduction / Context:Some products provide not only a DBMS engine but also built-in tools to rapidly create forms, reports, and small applications. Recognizing this positioning helps match tools to use cases.
Given Data / Assumptions:
Concept / Approach:Microsoft Access is both a file-based desktop database and a RAD environment for building data-centric apps quickly, including forms and reports. Enterprise DBMSs (SQL Server, Oracle, DB2) emphasize server-scale features and expect external application tiers.
Step-by-Step Solution:
Check for integrated forms/reports designer → Access has native UI designers, macros, and VBA.SQL Server/Oracle/DB2 → rely on external app frameworks (e.g., .NET, Java, APEX is separate from the core DBMS install).Hence, the combined DBMS + app generator role is best matched by Access.Verification / Alternative check:Product literature describes Access as part of Microsoft Office, highlighting rapid form/report creation backed by Jet/ACE database engine.
Why Other Options Are Wrong:They are enterprise RDBMS platforms; while tools exist in their ecosystems, their core product is not an end-user application generator.
Common Pitfalls:Equating optional ecosystem tools with a fully integrated end-user app builder.
Final Answer:Microsoft's Access
Discussion & Comments