Remove any access keys for the root user and Assign distinct access keys to each application or automation script are the correct choices for strengthening IAM practices at NovaSight Analytics.

Remove any access keys for the root user eliminates the highest risk credential because the root account has full control of the AWS account. Removing root keys reduces the chance of a wide ranging compromise and follows AWS guidance to perform only a few account level tasks with the root account.

Assign distinct access keys to each application or automation script limits the blast radius by giving each identity only the permissions it needs and by making rotation and revocation targeted and auditable. Using separate keys or, preferably, roles and temporary credentials, makes it easier to enforce least privilege and to investigate or remediate incidents without affecting unrelated systems.

Rotate access keys every 24 hours is impractical for most environments and creates operational burden that can lead to risky workarounds. AWS advises regular rotation based on risk and operational readiness rather than an extreme daily schedule.

Store access keys directly in application code repositories is unsafe because code repositories can be shared or exposed and commits can leak secrets. The better approach is to use IAM roles, secret managers, or environment based temporary credentials instead of hard coding keys.

Use a single access key across all services for consistency centralizes risk and removes traceability. A single key makes incident response and targeted revocation difficult and contradicts the principle of least privilege.

Full AWS Practitioner Certification Question