Exam 350-901 topic 1 question 25 discussion

A and B seem correct. C: tightly coupled components are in a monolithic architectrure D: star topology being single point of failure E: waterfall projects

The two design approaches that contribute to the scalability of the application from your given options are: A. session management in a stateless architecture Explanation: Stateless architectures, where each request from the client to the server must contain all the information needed to understand and process the request, can greatly enhance scalability. This is because without needing to keep track of state information, servers can handle any incoming request at any time, making it easier to distribute the workload across multiple servers. B. modular design iteration Explanation: A modular design means the application is divided into smaller, independent modules that can be developed, tested, and scaled independently. This also allows for parallel development and can enhance the overall scalability of the system.

The two design approaches that contribute to the scalability of the application from your given options are: A. session management in a stateless architecture Explanation: Stateless architectures, where each request from the client to the server must contain all the information needed to understand and process the request, can greatly enhance scalability. This is because without needing to keep track of state information, servers can handle any incoming request at any time, making it easier to distribute the workload across multiple servers. B. modular design iteration Explanation: A modular design means the application is divided into smaller, independent modules that can be developed, tested, and scaled independently. This also allows for parallel development and can enhance the overall scalability of the system.

A. Session management in a stateless architecture: Stateless architectures do not maintain any session state on the server, instead, they store session data on the client-side, and each client request is treated as a new request. This approach helps to improve scalability by allowing requests to be distributed across multiple servers, without worrying about maintaining session state. B. Modular design iteration: A modular design approach breaks the application into smaller, more manageable components or modules, that can be developed and deployed independently. This approach allows for greater flexibility in scaling the application by allowing only the necessary modules to be scaled when needed, without impacting the entire application.

I'll go for A and B too.. ''..Simple, because in practice, scaling an application is very much dependent on its capability to be modular, with the modules being as independent or autonomous as possible, as stateless as possible, and with interfaces and APIs for interaction'

a&b C: Makes no sense, everything is already scattered. D: star topology being single point of failure E: Waterfall

I'd say A and B are correct. C makes no sense for a distributed system where everything has one function.

A and B C is incorrect Traditional monolithic applications are tightly coupled, meaning the components depend on each other and are aware of each other’s state.

A & B seem the right choice, for the same reasons already pointed out by duracell

one requirement is to provide one service or function, sounds like monolithic to me rather than a microservice and another requirement is uses session management which sounds like using tokens for stateful sessions. so i think i will stick with B and C.