A county 311 application stores MongoDB-compatible JSON case documents and currently runs a self-managed replica set on aging VMs. Architects must choose a new database platform that reduces undifferentiated operations unless a blocking engine feature is proven. Which recommendation is appropriate?
Select an answer to reveal the explanation.
Short Explanation
If the app already speaks Mongo-shaped JSON, don't volunteer to patch replica sets at 2 a.m. DocumentDB is the managed path unless a real engine feature truly blocks it. Self-managing on EC2 is an exception you document, not the default souvenir from the old rack.
Full Explanation
For MongoDB-compatible municipal applications, Amazon DocumentDB is the preferred managed target because it removes replica-set operations, patching, and backup toil. Self-managed MongoDB on EC2 remains valid only when a required engine feature is incompatible and that exception is documented. Neptune graphs and Windows registry keys are not the Mongo-compatible platform choice.