Title: Quiz 9 — Data Privacy, Secrets Management, and Access Control
Course: AIINFRA 302: AI Security, Guardrails & Governance > Section: Week 09 — Data Privacy, Secrets Management, and Access Control

Q: Storing an API key in an environment variable instead of hardcoding it in source code is sufficient to make it secure.
- True
- False
A: False

Q: On a Linux system, how can a same-UID process potentially read another process's environment variables?
- By querying the system's DNS cache
- By reading `/proc/[pid]/environ`
- By inspecting the CPU cache
- It is impossible under any circumstances
A: By reading `/proc/[pid]/environ`

Q: A developer commits an API key by accident, then deletes the file and pushes a "fix" commit. Why is the secret still exposed?
Feedback: Sample/expected answer: Because git history is append-only — the original commit containing the secret still exists in the repository's history and is reachable by anyone with repo/clone access, even though the current working tree no longer shows the file.

Q: What is the actual correct remediation after discovering a secret was committed and pushed to a shared repository?
- Delete the file and force-push
- Add the file to `.gitignore`
- Immediately rotate/revoke the exposed credential at its source
- Rename the branch
A: Immediately rotate/revoke the exposed credential at its source

Q: HashiCorp Vault's OpenAI secrets engine plugin can generate short-lived, auto-expiring API keys (e.g., expiring in as little as 5 minutes) instead of relying on a static key.
- True
- False
A: True

Q: What access-control mechanism did the November 2025 (2025-11-25) MCP spec revision formalize for remote MCP servers to prevent a compromised server from reusing a token against a different resource?
- IP allowlisting
- OAuth 2.1 with token-audience binding
- Basic auth over HTTPS
- Shared API keys rotated weekly
A: OAuth 2.1 with token-audience binding

Q: Why are over-privileged service accounts considered a top AI data risk in RAG systems specifically?
Feedback: Sample/expected answer: Because an AI agent authenticating with one broad service account can retrieve and expose far more data across many users' queries than any single human end user could reach manually — enforcing document-level RBAC/ABAC at retrieval time limits each user to only the chunks they're individually authorized to see.

Q: Because a vector store only contains numerical embeddings, it does not need the same access control, encryption, and audit logging as a traditional PII database.
- True
- False
A: False