A deployment definition for city cloud resources is stored as nested key/value text that many cloud APIs accept natively. Which common format is described?
Select an answer to reveal the explanation.
Short Explanation
JSON is the curly-brace language cloud APIs grew up speaking—nested keys and values that tools and templates share. It is not punch cards or audio files.
Full Explanation
JSON is a structured nested key/value text format widely used by cloud APIs and many IaC definitions. A deployment definition stored as nested key/value text that many cloud APIs accept natively points to JSON in this item. Binary firmware blobs signed only by BIOS vendors fails as the described format. Handwritten paper punch cards scanned at apply time fails. Uncompressed raw WAV files for infrastructure state fails. Exam caveat: format recognition questions are literal—match structural traits such as nested key/value text common to APIs to JSON versus YAML or HCL when those cues appear. Operational check: validate JSON with schema checks in the pipeline, keep files UTF-8, avoid comments if the parser forbids them, and pretty-print with indent 2 for municipal review diffs. In municipal platform operations, record the chosen control and the rejected alternatives in the change record so future on-call engineers understand the failure modes avoided for citizen services. Re-check the decision after the next provider feature change or compliance update to ensure the same answer still holds for the city's estate. Confirm monitoring, access reviews, and backup coverage still align with the selected approach before closing the civic hypercare period.