Loading course title...

Loading assessment title...

Connecting to LMS... Progress: in progress

Assessment

1. What is the main purpose of secrets management? Make credentials easier to copy into chat Store all secrets in source code Control how sensitive access values are stored, used, rotated, and monitored Remove all audit trails

2. Which item is commonly considered a secret? An API key or private key A public product name A generic button label A non-sensitive help page title

3. Which is a common way secrets can leak? Through approved documentation that contains no credentials Through a public marketing page with no access values Through a normal meeting agenda Through source code, logs, tickets, chat, build output, or container images

4. Why should teams use an approved secret manager or vault? To make every user an administrator To centralize protected storage, access policy, auditing, and lifecycle controls To remove the need for ownership To make rotation impossible

5. What does least privilege mean for secrets? Everyone gets access to every secret Access reviews are never needed People and workloads receive only the secret access they need Secrets should be posted in shared channels

6. Why should applications avoid logging secrets? Logs are never reviewed Logging secrets improves security Secrets in logs cannot be copied Logs can be widely accessed, stored, exported, or retained

7. What does revocation mean? Invalidating a secret so it no longer works Copying a secret into source code Sharing a token with more teams Turning off monitoring

8. Which is the best secrets management operating routine? Hardcode, forget, and hope Identify, classify, store securely, restrict access, deliver safely, rotate, monitor, respond, and improve Put every secret in logs Give permanent access to every workload