Exception handling and error management is the correct answer. This concept is most directly associated with the fail safe defaults principle because it ensures that when errors occur the system defaults to a safe state rather than granting access or revealing sensitive information.

Fail safe defaults means deny by default and do not assume correct behavior when an unexpected condition arises. Proper exception handling implements this by catching failures, avoiding permissive fallback behavior, and returning minimal or safe responses on error.

Least privilege access model is not the best fit because it focuses on granting users and processes only the permissions they need. That principle reduces exposure but it does not directly dictate how a system should behave when an error occurs.

Session management and lifecycle control deals with token handling, session expiration, and related lifecycle matters. Those concerns are about maintaining session integrity and are not primarily about failing to a safe default on exceptions.

Single point of failure concerns are about availability and architectural redundancy. They address reliability rather than the security behavior a system should adopt when an error or exception happens.

Full AWS Practitioner Certification Question