Hardcoded credentials and public database
An AI assistant wrote this RDS module for a PII-bearing customer database when you asked it to "spin up a Postgres instance for the customers table." Compliance review is in two days. What does the reviewer flag?
Implement
audit_db_instance(attributes: list[str]) → list[str]Examples
in
[["identifier=prod-customers","engine=postgres","username=admin","password=ChangeMe123!","publicly_accessible=true","skip_final_snapshot=true"]]out["deletion_protection_off","encryption_at_rest_off","hardcoded_password","no_final_snapshot","public_endpoint"]in
[["storage_encrypted=true","password=var.db_password","publicly_accessible=false","skip_final_snapshot=false","deletion_protection=true"]]out[]in
[[]]out["deletion_protection_off","encryption_at_rest_off"]What a strong answer looks like
Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it (tests, edge cases, reading critically), and how you’d re-prompt or decompose to get it right.
0:00 of about 14 min
Vibe & agentic: describe the solution in plain language (or narrate it) and the coach grades your approach.
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.