In your database instance, the user sessions are connected to the database server from the remote machines. You want to achieve the following for these users: 1. The user account must be locked after four unsuccessful login attempts. 2. The user must be prompted to change the password at regular intervals. 3. The user may not have more than three simultaneous sessions. 4. The user session must automatically be logged off if more than 10 minutes elapsed time used. How would you accomplish the above?

Question

Accepted Answer

A. By assigning profiles for the users Oracle profiles allow a DBA to set resource and password parameters including FAILED_LOGIN_ATTEMPTS (locks account after N failed logins), PASSWORD_LIFE_TIME (forces periodic password changes), SESSIONS_PER_USER (limits concurrent sessions), and CONNECT_TIME (auto-logs off sessions exceeding elapsed time). A single profile assigned to a user enforces all four requirements simultaneously.

Answer

B. By implementing Fine-Grained Auditing (FGA) Fine-Grained Auditing is used to audit access to specific table rows or columns based on conditions - it does not enforce login attempt limits, session counts, or password policies.

Answer

C. By granting a secure application role to the users A secure application role controls which privileges are granted to an application session - it does not manage password aging, login lockouts, or session resource limits.

Answer

D. By implementing the Database Resource Manager plan Database Resource Manager controls CPU, parallel execution, and I/O resource allocation among sessions - it does not handle password management or failed login attempt tracking.

In your database instance, the user sessions are connected to the database server from the remote machines. You want to achieve the following for these users: 1. The user account must be locked…

Question

Options

How the community answered

Why each option

Topics

Community Discussion