Solutions Architect Interview Questions

T I. - "This is due to sticky sessions. The load balancer is not correctly configured with sticky session option. It is likely the servers were storing session data on the server themselves (in-memory), and thus when user makes a request, the load balancer routes this to a different server than the one they started with, that second server may not recognise the user's session. This could prompt the user to log in again. One way to resolve this, is to use a centralised session storage, something like"See full answer

Ali H. - "CIDR (Classless Inter-Domain Routing) -- also known as supernetting -- is a method of assigning Internet Protocol (IP) addresses that improves the efficiency of address distribution and replaces the previous system based on Class A, Class B and Class C networks."See full answer

Gopal R. - "Stateful Firewall Tracks the state of active network connections (TCP, UDP, etc.) and makes decisions based on both rules and connection state (e.g., established sessions). Stateless Firewall Makes decisions based only on packet header information (source IP, destination IP, port, protocol) without tracking connection states."See full answer

Anonymous Narwhal - "Ability for system to keep in service without much degradation in SLA or adding significant latency."See full answer

Archna M. - "Caching is a strategy to have the frequently accessed data in the memory to reduce the latency. whenever a client request the data from server, it is first accessed into cache and if not available then it is getting fetched from the storage and stored into cache. As cache is having limited memory, so amount of data can be stored in cache is less. Data will be flushed out from cache based on a criteria which is termed as caching strategy. There could be different mechanisms under which a data can"See full answer

Madhini G. - "Use sticky sessions in loadbalancer to save the user sessions. In case of DB, use Redis cache to maintain user sessions"See full answer