How would you handle a practical scenario involving Service Boundaries in Microservices Architecture?

For a practical scenario involving Service Boundaries, I would first clarify the business goal, scale, constraints, and the failure or quality attribute being tested. Service boundaries define which business capabilities and data responsibilities belong inside each microservice. The scenario centers on given an e-commerce platform, explain how you would separate catalog, ordering, payment, and fulfillment without creating excessive coupling. For production, model boundaries around business capabilities, keep ownership explicit, minimize cross-service transactions, and evolve boundaries when domain knowledge improves. I would then compare the main alternatives and tradeoffs, identify likely failure modes, and explain how I would validate the solution through testing, observability, security controls, and recovery or rollback planning.