Municipal procurement prefers license-included Amazon RDS so the city does not have to track its own database license inventory. What trade-off does that preference reflect?
Select an answer to reveal the explanation.
Short Explanation
License-included is the “ticket comes with the seat” path — less hunting through the city’s license drawer. BYOL can be great when you already own rights, but it adds inventory tracking. Procurement is choosing simplicity over managing that drawer.
Full Explanation
License-included purchasing can simplify entitlement tracking compared with Bring Your Own License, often with different pricing—the trade-off municipal procurement prefers when choosing license-included Amazon RDS to avoid tracking its own database license inventory. Convenience and pricing differ; neither option is universally “free of thought.”
License-included and BYOL do not always have identical prices and tracking burden. BYOL is not required whenever a city wants any managed database. License-included options do not remove the database engine and leave only empty volumes.
Exam caveat: BYOL vs license-included is about entitlements and pricing mechanics, not whether RDS exists. Operational check: compare quote lines for BYOL versus license-included for the same RDS engine/version, confirm procurement can meet audit needs either way, and document the selected model.
Municipal teams should keep a one-page decision record linking this Cloud Practitioner concept to resident outcomes, revisit it after major traffic or compliance changes, and ensure runbooks still match the chosen design.
Municipal teams should keep a one-page decision record linking this Cloud Practitioner concept to resident outcomes, revisit it after major traffic or compliance changes, and ensure runbooks still match the chosen design.