Profiling a receipt-generation Lambda shows JSON serialization dominating CPU on the hot path. What should the municipal developer do first?
Select an answer to reveal the explanation.
Short Explanation
When the profiler points at JSON packing as the furnace, don't rebuild the whole house. Fix that hot serialization path first. Guessing that auth is the villain wastes a sprint.
Full Explanation
Performance work should follow measured hotspots. If profiling shows JSON serialization dominating CPU on a receipt path, optimize that path before speculative rewrites elsewhere. Changing log retention or disabling metrics does not reduce CPU on the hot path. Evidence-based remediation is the Domain 4 expectation.