A developer writes environment settings in a file that uses curly braces, double-quoted property keys, and no trailing commas. During a test of the automated rollout, there is a parsing error caused by an extra comma at the end of one section. Which approach would fix the error and preserve the file’s supported structure?
Put all data on one line for minimal spacing
Place a semicolon after the final element
Use angled brackets instead of curly braces
Delete the comma after the last pair in each section
Removing the trailing comma at the end of a group adheres to strict JSON formatting rules by ensuring that each object’s final pair has no extra punctuation. Using alternative brackets or adding other punctuation would not comply with the file’s structure, and single-line or angled bracket approaches break the syntax expected by JSON viewers. Maintaining the core style of double-quoted keys and curly braces is essential for successful parsing.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
Why does JSON not allow trailing commas?
Open an interactive chat with Bash
What happens if alternative brackets are used instead of curly braces in JSON?