Five containers are labeled microservices, yet they share one database and must always ship on the same release train because any schema change breaks all five. What have the architects actually built?
Select an answer to reveal the explanation.
Short Explanation
Five trailers locked to one hitch still move as one truck. Shared database and lockstep releases mean you have a distributed monolith, not independent microservices. The slide title does not override the coupling.
Full Explanation
True microservices require independent deployability and typically decentralized data. Processes that cannot ship separately because of a shared database and shared change window are a distributed monolith despite container packaging. Containerization alone does not create the pattern.