CPSA-F Certified Professional for Software Architecture – Foundation Level Practice Questions

This statement is true. Conway's Law famously states that organizations which design systems are constrained to produce designs which are copies of the communication structures of these organizations. This highlights the powerful influence of team structure and organizational communication paths on the final software architecture.

CQRS is a pattern that separates the models for updating (Command) and reading (Query) data. This is ideal for scenarios with very different read/write patterns. It allows the read model to be highly optimized for queries (e.g., using denormalized views), while the write model is optimized for transactional consistency. The tolerance for eventual consistency ('does not need to be immediately available') is a classic indicator for a CQRS-based solution.

The Single Responsibility Principle states that a class should have only one reason to change. The ReportGenerator class has multiple responsibilities: data access, data formatting, and notification. A change in the database, the PDF format, or the email system would all require this single class to be modified. This violates SRP and indicates very low cohesion.

The most critical flaw is placing the database server in the Demilitarized Zone (DMZ). Security best practices dictate that data stores should be in a separate, private subnet with no direct access from the internet. Only the web servers in the DMZ should be able to communicate with the database. Placing the database in the DMZ exposes it to a much higher level of risk if a web server is compromised.

Quantitative analysis relies on objective, numerical measurements. Response time, throughput, and resource utilization (CPU/memory) are all direct, measurable metrics that can be used to identify performance issues. Developer sentiment is a form of qualitative data, valuable for assessing maintainability but not for quantitative performance analysis.

The Strangler Fig pattern is the optimal choice as it allows for an incremental, risk-managed migration. It directly addresses the goals of improving time-to-market and fault isolation by creating independent services. It also respects the team's Java skills (new services can be in Java) while allowing them to learn containerization gradually. A big-bang rewrite is too risky, a lift-and-shift doesn't solve the core architectural problems, and a modular monolith improves code structure but not independent deployability or fault isolation as effectively.

Cross-cutting concerns are aspects of a system that affect multiple components. Distributed tracing, centralized logging, and security (authN/authZ) are classic examples that require a consistent, system-wide approach to be effective. Inconsistent implementation would render them useless. Business logic and database schemas are specific to the bounded context of an individual service and are not cross-cutting.

This statement is true. A core advantage of the Pipes and Filters pattern is the decoupling of individual processing steps (filters). Because each filter only depends on the input data format and produces an output in the agreed-upon format, they can be developed, deployed, and tested independently, which enhances modularity and maintainability.

The Open/Closed Principle states that software entities (classes, modules, functions, etc.) should be open for extension but closed for modification. This directly addresses the requirement to add new functionality without changing the existing, core code, thus avoiding complex conditional logic. Patterns like Strategy or Decorator are common implementations of OCP.

The Dependency Inversion Principle states that high-level modules should not depend on low-level modules; both should depend on abstractions. By changing UserService (high-level) to depend on ILogger (abstraction) instead of PostgreSQL_Logger (low-level), the architect is directly applying DIP. This decouples the services from the concrete logging implementation, making the system more flexible and easier to test.