Q1. Software architecture is defined as:
(A) High-level structure of a software system
(B) Coding standards only
(C) Database schema
(D) User interface design
Answer: (A) High-level structure of a software system
Q2. The primary purpose of software architecture is:
(A) Guide system development and maintenance
(B) Install hardware
(C) Write code only
(D) Deploy network
Answer: (A) Guide system development and maintenance
Q3. Architectural style defines:
(A) A reusable solution pattern for system structure
(B) Coding shortcuts
(C) UI colors
(D) Hardware setup
Answer: (A) A reusable solution pattern for system structure
Q4. Layered architecture separates system into:
(A) Layers with distinct responsibilities
(B) Monolithic code
(C) Random modules
(D) Hardware components
Answer: (A) Layers with distinct responsibilities
Q5. Client-server architecture separates:
(A) Service provider and client
(B) Coding and testing
(C) Database only
(D) UI only
Answer: (A) Service provider and client
Q6. MVC architecture stands for:
(A) Model-View-Controller
(B) Module-View-Coding
(C) Main-Verification-Code
(D) Monitor-Variable-Control
Answer: (A) Model-View-Controller
Q7. In MVC, Model represents:
(A) Data and business logic
(B) UI
(C) Controller only
(D) Deployment scripts
Answer: (A) Data and business logic
Q8. In MVC, View represents:
(A) User interface
(B) Database
(C) Code modules
(D) Network configuration
Answer: (A) User interface
Q9. In MVC, Controller:
(A) Handles input and updates Model and View
(B) Manages hardware
(C) Writes database queries only
(D) Performs testing
Answer: (A) Handles input and updates Model and View
Q10. Event-driven architecture is based on:
(A) Events triggering actions
(B) Sequential coding
(C) Hardware interrupts
(D) Network messages only
Answer: (A) Events triggering actions
Q11. Repository architecture centralizes:
(A) Data storage for multiple components
(B) UI layout
(C) Hardware devices
(D) Coding files
Answer: (A) Data storage for multiple components
Q12. Microservices architecture emphasizes:
(A) Small, independent services
(B) Monolithic design
(C) Hardware reuse
(D) Single module only
Answer: (A) Small, independent services
Q13. Monolithic architecture is:
(A) Single large system
(B) Distributed microservices
(C) Client-server only
(D) Layered only
Answer: (A) Single large system
Q14. Peer-to-peer architecture allows:
(A) Equal nodes communication
(B) Central server only
(C) Monolithic system
(D) Single client-server
Answer: (A) Equal nodes communication
Q15. Service-oriented architecture (SOA) focuses on:
(A) Services with well-defined interfaces
(B) Hardware installation
(C) UI design
(D) Coding shortcuts
Answer: (A) Services with well-defined interfaces
Q16. Layered architecture benefits include:
(A) Modularity and maintainability
(B) Faster hardware
(C) Database optimization
(D) Coding speed
Answer: (A) Modularity and maintainability
Q17. Pipe-and-filter architecture is suited for:
(A) Data transformation pipelines
(B) Monolithic systems
(C) Peer-to-peer only
(D) UI design
Answer: (A) Data transformation pipelines
Q18. Broker architecture coordinates:
(A) Communication between clients and servers
(B) Hardware deployment
(C) UI only
(D) Database only
Answer: (A) Communication between clients and servers
Q19. MVC pattern improves:
(A) Separation of concerns
(B) Hardware reuse
(C) Coding errors
(D) Network speed
Answer: (A) Separation of concerns
Q20. Component-based architecture focuses on:
(A) Independent reusable software components
(B) Single monolithic code
(C) Hardware optimization
(D) UI layout
Answer: (A) Independent reusable software components
Q21. Design patterns in architecture help to:
(A) Provide reusable solutions
(B) Increase coding errors
(C) Hardware installation
(D) UI design only
Answer: (A) Provide reusable solutions
Q22. Singleton pattern ensures:
(A) Only one instance of a component
(B) Multiple instances
(C) Distributed system
(D) Peer-to-peer system
Answer: (A) Only one instance of a component
Q23. Observer pattern is used for:
(A) Event notification to multiple components
(B) UI redesign
(C) Hardware monitoring
(D) Database queries
Answer: (A) Event notification to multiple components
Q24. Adapter pattern helps:
(A) Connect incompatible interfaces
(B) Merge databases
(C) Improve network speed
(D) Hardware setup
Answer: (A) Connect incompatible interfaces
Q25. Broker pattern components include:
(A) Clients, servers, and broker
(B) UI, database, controller
(C) Hardware devices only
(D) Coding modules
Answer: (A) Clients, servers, and broker
Q26. Microkernel architecture is used in:
(A) Extensible systems
(B) Monolithic systems
(C) Peer-to-peer only
(D) Client-server only
Answer: (A) Extensible systems
Q27. Microkernel separates:
(A) Core system and plug-in modules
(B) Database and UI only
(C) Coding modules
(D) Hardware only
Answer: (A) Core system and plug-in modules
Q28. Layered architecture drawbacks include:
(A) Performance overhead
(B) Hardware failure
(C) UI redesign
(D) Coding shortcuts
Answer: (A) Performance overhead
Q29. Service-oriented architecture allows:
(A) Loose coupling of services
(B) Tight hardware integration
(C) Monolithic code
(D) UI redesign
Answer: (A) Loose coupling of services
Q30. Architectural documentation includes:
(A) Views, components, connectors
(B) Coding files only
(C) UI color charts
(D) Hardware manuals
Answer: (A) Views, components, connectors
Q31. 4+1 view model includes:
(A) Logical, Development, Process, Physical, Scenarios
(B) UI, Database, Network, Hardware, Coding
(C) Client, Server, Peer, Broker, Adapter
(D) Layer, Pipe, Microkernel, SOA, MVC
Answer: (A) Logical, Development, Process, Physical, Scenarios
Q32. Logical view represents:
(A) Object model of system
(B) Hardware layout
(C) UI only
(D) Deployment scripts
Answer: (A) Object model of system
Q33. Development view focuses on:
(A) Module organization for developers
(B) Database structure
(C) Hardware deployment
(D) UI layout
Answer: (A) Module organization for developers
Q34. Process view shows:
(A) Runtime behavior and concurrency
(B) Database only
(C) UI layout
(D) Coding style
Answer: (A) Runtime behavior and concurrency
Q35. Physical view shows:
(A) Hardware mapping of software
(B) Database tables
(C) UI screens
(D) Coding files
Answer: (A) Hardware mapping of software
Q36. Scenario view describes:
(A) Use case or sequence diagrams
(B) Coding shortcuts
(C) Hardware setup
(D) UI design
Answer: (A) Use case or sequence diagrams
Q37. Architectural decisions affect:
(A) System quality and maintainability
(B) Hardware cost only
(C) UI color only
(D) Deployment scripts only
Answer: (A) System quality and maintainability
Q38. Architectural patterns improve:
(A) Reusability and standardization
(B) Coding errors
(C) Hardware speed
(D) UI design
Answer: (A) Reusability and standardization
Q39. Layered pattern promotes:
(A) Separation of concerns
(B) Monolithic coding
(C) Hardware integration
(D) Deployment scripts
Answer: (A) Separation of concerns
Q40. Microservices are:
(A) Small, deployable services
(B) Monolithic modules
(C) Hardware devices
(D) UI screens
Answer: (A) Small, deployable services
Q41. Monolithic systems are:
(A) Single, large codebase
(B) Independent services
(C) Microservices only
(D) Layered architecture
Answer: (A) Single, large codebase
Q42. Peer-to-peer architecture lacks:
(A) Central server
(B) Client modules
(C) Coding files
(D) Hardware devices
Answer: (A) Central server
Q43. Broker architecture is suitable for:
(A) Distributed systems
(B) Monolithic systems
(C) UI only
(D) Hardware only
Answer: (A) Distributed systems
Q44. Microkernel is used for:
(A) Extensible applications
(B) Monolithic coding
(C) UI design
(D) Database queries
Answer: (A) Extensible applications
Q45. Architectural evaluation ensures:
(A) System meets quality attributes
(B) Hardware is ready
(C) UI is colorful
(D) Coding speed
Answer: (A) System meets quality attributes
Q46. Architectural metrics include:
(A) Coupling, cohesion, complexity
(B) Disk space
(C) CPU speed
(D) Network bandwidth
Answer: (A) Coupling, cohesion, complexity
Q47. Software connectors represent:
(A) Interactions between components
(B) UI screens
(C) Coding files
(D) Hardware only
Answer: (A) Interactions between components
Q48. Component diagrams show:
(A) Software components and interfaces
(B) Database tables
(C) UI only
(D) Hardware layout
Answer: (A) Software components and interfaces
Q49. Deployment diagrams represent:
(A) Software mapping onto hardware
(B) Coding modules
(C) UI layout
(D) Database only
Answer: (A) Software mapping onto hardware
Q50. Architectural review helps:
(A) Identify design issues early
(B) Deploy hardware
(C) Install OS
(D) Write code faster
Answer: (A) Identify design issues early
Q51. Architectural drivers include:
(A) Requirements, constraints, and quality attributes
(B) Hardware only
(C) UI colors only
(D) Coding shortcuts only
Answer: (A) Requirements, constraints, and quality attributes
Q52. Quality attributes in architecture refer to:
(A) Performance, security, maintainability
(B) Coding speed
(C) Hardware type
(D) UI layout
Answer: (A) Performance, security, maintainability
Q53. Scalability ensures:
(A) System can handle growth in load
(B) Faster coding
(C) Smaller database
(D) Hardware reuse
Answer: (A) System can handle growth in load
Q54. Availability refers to:
(A) System uptime and reliability
(B) Coding speed
(C) UI colors
(D) Hardware installation
Answer: (A) System uptime and reliability
Q55. Modifiability means:
(A) Ease of making changes to the system
(B) Faster deployment
(C) Hardware efficiency
(D) UI redesign
Answer: (A) Ease of making changes to the system
Q56. Security in architecture ensures:
(A) Protection against threats and vulnerabilities
(B) Coding shortcuts
(C) UI design
(D) Hardware setup
Answer: (A) Protection against threats and vulnerabilities
Q57. Performance attribute measures:
(A) Response time and throughput
(B) UI responsiveness only
(C) Database size
(D) Hardware power
Answer: (A) Response time and throughput
Q58. Reliability ensures:
(A) System operates correctly under specified conditions
(B) Hardware works
(C) Coding speed
(D) UI colors
Answer: (A) System operates correctly under specified conditions
Q59. Maintainability refers to:
(A) Ease of fixing defects and updating system
(B) Hardware reuse
(C) UI redesign
(D) Coding shortcuts
Answer: (A) Ease of fixing defects and updating system
Q60. Reusability in architecture:
(A) Promotes using components in multiple systems
(B) UI redesign
(C) Hardware setup
(D) Coding speed
Answer: (A) Promotes using components in multiple systems
Q61. Architectural tactics are:
(A) Techniques to achieve quality attributes
(B) Hardware tools
(C) UI layouts
(D) Coding shortcuts
Answer: (A) Techniques to achieve quality attributes
Q62. Fault tolerance tactic helps:
(A) System continue operation despite faults
(B) Faster coding
(C) UI redesign
(D) Hardware reuse
Answer: (A) System continue operation despite faults
Q63. Load balancing tactic improves:
(A) Performance and scalability
(B) Security only
(C) Coding speed
(D) UI colors
Answer: (A) Performance and scalability
Q64. Caching tactic enhances:
(A) Performance by storing frequently used data
(B) Security
(C) Modifiability
(D) Hardware efficiency
Answer: (A) Performance by storing frequently used data
Q65. Authentication and authorization tactics improve:
(A) Security
(B) Performance
(C) Scalability
(D) UI layout
Answer: (A) Security
Q66. Architectural patterns guide:
(A) System structure and component interactions
(B) UI design
(C) Hardware setup
(D) Database only
Answer: (A) System structure and component interactions
Q67. Layered pattern separates:
(A) Concerns into layers
(B) Hardware modules
(C) Coding shortcuts
(D) UI screens only
Answer: (A) Concerns into layers
Q68. Client-server pattern separates:
(A) Client and server responsibilities
(B) Database only
(C) UI only
(D) Hardware modules
Answer: (A) Client and server responsibilities
Q69. Event-driven pattern uses:
(A) Events to trigger processing
(B) Monolithic code
(C) Hardware interrupts only
(D) UI design only
Answer: (A) Events to trigger processing
Q70. Microservices pattern promotes:
(A) Independent deployable services
(B) Single large system
(C) Layered only
(D) Client-server only
Answer: (A) Independent deployable services
Q71. Pipe-and-filter pattern emphasizes:
(A) Sequential processing through filters
(B) Monolithic code
(C) Hardware optimization
(D) UI design
Answer: (A) Sequential processing through filters
Q72. Repository pattern centralizes:
(A) Shared data storage
(B) UI layout
(C) Coding modules
(D) Hardware only
Answer: (A) Shared data storage
Q73. Microkernel pattern separates:
(A) Core system and plug-ins
(B) Database and UI
(C) Hardware and software
(D) Coding only
Answer: (A) Core system and plug-ins
Q74. Broker pattern manages:
(A) Communication among distributed components
(B) UI layout
(C) Database only
(D) Hardware only
Answer: (A) Communication among distributed components
Q75. Architectural evaluation is done to:
(A) Assess if architecture meets requirements and quality goals
(B) Deploy hardware
(C) UI redesign
(D) Coding only
Answer: (A) Assess if architecture meets requirements and quality goals
Q76. ATAM stands for:
(A) Architecture Tradeoff Analysis Method
(B) Automated Testing Analysis Method
(C) Architecture Tactic Assessment Model
(D) Adaptive Testing and Maintenance
Answer: (A) Architecture Tradeoff Analysis Method
Q77. Architecture documentation includes:
(A) Views, components, connectors, rationale
(B) Coding shortcuts only
(C) Hardware manuals only
(D) UI designs only
Answer: (A) Views, components, connectors, rationale
Q78. 4+1 view model includes:
(A) Logical, Development, Process, Physical, Scenarios
(B) UI, Database, Coding, Hardware, Network
(C) Client, Server, Peer, Adapter, Layer
(D) Microservices, Monolith, Layered, MVC, SOA
Answer: (A) Logical, Development, Process, Physical, Scenarios
Q79. Logical view represents:
(A) Object model and functionality
(B) Hardware mapping
(C) Deployment only
(D) UI layout only
Answer: (A) Object model and functionality
Q80. Development view focuses on:
(A) Module organization for developers
(B) Network only
(C) Hardware only
(D) UI screens
Answer: (A) Module organization for developers
Q81. Process view shows:
(A) Runtime behavior and concurrency
(B) UI layout
(C) Coding style
(D) Hardware setup
Answer: (A) Runtime behavior and concurrency
Q82. Physical view shows:
(A) Hardware mapping of software
(B) Coding modules
(C) UI only
(D) Database only
Answer: (A) Hardware mapping of software
Q83. Scenario view describes:
(A) Use cases and sequences
(B) Hardware only
(C) Coding shortcuts
(D) UI screens only
Answer: (A) Use cases and sequences
Q84. Architecture evaluation assesses:
(A) Quality attributes like performance, modifiability, security
(B) Hardware only
(C) UI layout only
(D) Coding speed only
Answer: (A) Quality attributes like performance, modifiability, security
Q85. Architectural trade-offs occur when:
(A) Improving one quality may affect another
(B) Hardware is installed
(C) UI redesign
(D) Coding shortcuts
Answer: (A) Improving one quality may affect another
Q86. Coupling in architecture refers to:
(A) Degree of interdependence between components
(B) Coding style
(C) UI colors
(D) Hardware only
Answer: (A) Degree of interdependence between components
Q87. Cohesion in architecture refers to:
(A) Degree to which components work together to achieve single purpose
(B) Coding shortcuts
(C) UI layout
(D) Hardware reuse
Answer: (A) Degree to which components work together to achieve single purpose
Q88. Scalability tactics include:
(A) Load balancing and replication
(B) UI redesign
(C) Coding shortcuts
(D) Hardware only
Answer: (A) Load balancing and replication
Q89. Performance tactics include:
(A) Caching, concurrency, and batching
(B) Hardware only
(C) UI colors
(D) Database tables
Answer: (A) Caching, concurrency, and batching
Q90. Security tactics include:
(A) Authentication, authorization, encryption
(B) Caching only
(C) Performance only
(D) UI layout
Answer: (A) Authentication, authorization, encryption
Q91. Fault tolerance tactics include:
(A) Redundancy and recovery
(B) UI redesign
(C) Hardware only
(D) Coding shortcuts
Answer: (A) Redundancy and recovery
Q92. Architectural risk assessment identifies:
(A) Potential failures and mitigation strategies
(B) Hardware only
(C) UI layout only
(D) Coding shortcuts
Answer: (A) Potential failures and mitigation strategies
Q93. Architectural patterns improve:
(A) Reuse, maintainability, and standardization
(B) Hardware speed only
(C) UI colors only
(D) Coding shortcuts only
Answer: (A) Reuse, maintainability, and standardization
Q94. Layered architecture drawback:
(A) Potential performance overhead
(B) Hardware failure
(C) UI design
(D) Coding style
Answer: (A) Potential performance overhead
Q95. Microservices advantage:
(A) Independent deployment and scalability
(B) Monolithic code
(C) Single module only
(D) Hardware only
Answer: (A) Independent deployment and scalability
Q96. Monolithic system disadvantage:
(A) Difficult to maintain and scale
(B) Hardware efficiency
(C) UI redesign
(D) Coding shortcuts
Answer: (A) Difficult to maintain and scale
Q97. Client-server disadvantage:
(A) Single point of failure at server
(B) UI issues only
(C) Hardware issues only
(D) Coding speed only
Answer: (A) Single point of failure at server
Q98. Peer-to-peer disadvantage:
(A) Complexity in coordination
(B) UI design
(C) Coding shortcuts
(D) Hardware reuse
Answer: (A) Complexity in coordination
Q99. Repository architecture disadvantage:
(A) Centralized data bottleneck
(B) UI colors
(C) Hardware only
(D) Coding shortcuts
Answer: (A) Centralized data bottleneck
Q100. The ultimate goal of software architecture is:
(A) Provide a blueprint for high-quality, maintainable, and scalable system
(B) Install hardware only
(C) Write code only
(D) UI design only
Answer: (A) Provide a blueprint for high-quality, maintainable, and scalable system