What to Do When a Shared User with Instance Wallet Leaves the Company
Question
An Autonomous Database (ADB) user with an instance wallet has left the company and they shared a database user id with other users when accessing ADB.
Other than changing the shared user password, what can the admin do to protect the instance? (Choose the best answer.)
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.B.
When an Autonomous Database (ADB) user with an instance wallet leaves the company, it is important for the admin to take immediate action to secure the database. In this scenario, changing the shared user password is not sufficient, as the user still has access to the instance wallet.
The best option to protect the instance is to rotate the instance wallet and share the new wallet with the remaining users, as stated in option B. This will invalidate the old wallet and any associated credentials, preventing the former employee from accessing the database.
Option A, deleting the user, is not recommended as it could result in data loss or orphaned objects that are associated with the user. Furthermore, the deleted user may have already shared the wallet password with others, which would still allow access to the database.
Option C, shutting down and restarting the instance, is not a valid solution as it does not address the issue of the former employee having access to the instance wallet.
Option D, trusting the user who left to not access the database, is not a secure option. Once an employee has left the company, it is not possible to ensure that they will not attempt to access the database. Trusting the user could leave the database vulnerable to unauthorized access and data breaches.
Therefore, the best course of action to protect the Autonomous Database instance is to rotate the instance wallet and share the new wallet with the remaining users. This will ensure that only authorized users can access the database, and any unauthorized access attempts are prevented.
