1Z0-062 · Question #337
Which three statements are true about user account administration? (Choose three.)
The correct answer is A. A user's current session is not affected when the user's profile is changed. B. Only users with the SYSDBA privilege can change the tablespace quota for other users. C. A new user account can be created only by SYS or SYSTEM users. Oracle user account administration involves managing user profiles, permissions for resource allocation, and the creation of new user accounts within the database.
Question
Which three statements are true about user account administration? (Choose three.)
Options
- AA user's current session is not affected when the user's profile is changed.
- BOnly users with the SYSDBA privilege can change the tablespace quota for other users.
- CA new user account can be created only by SYS or SYSTEM users.
- DA user's quota can be set for any permanent tablespace but not for the default temporary
- EA user requires only the CREATE SESSION privilege to change his or her own password.
How the community answered
(29 responses)- A86% (25)
- D3% (1)
- E10% (3)
Why each option
Oracle user account administration involves managing user profiles, permissions for resource allocation, and the creation of new user accounts within the database.
Changes made to a user's profile, such as resource limits or password policies, take effect only upon the user's next successful login, meaning existing active sessions continue under the profile settings that were active when they connected.
While the `ALTER USER` system privilege is specifically required to change tablespace quotas for other users, the `SYSDBA` privilege encompasses all system privileges, making users with this high-level role fully authorized and typically responsible for such administrative tasks.
The `CREATE USER` system privilege is necessary to create new user accounts in Oracle. By default, only the foundational `SYS` and `SYSTEM` administrative users are granted this privilege in a fresh database installation, making them the primary account creators.
User tablespace quotas are specifically designed to limit space usage within *permanent* tablespaces, not temporary tablespaces, as temporary space is managed differently at the session level.
While `CREATE SESSION` privilege is necessary for a user to log in, changing one's own password involves executing the `ALTER USER` command, which is an action authorized for any connected user on their own account, not solely dependent on `CREATE SESSION` as the exclusive authorization.
Concept tested: Oracle User Account Administration and Privileges
Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/admin/managing-security-for-oracle-database.html#GUID-263B2369-CE11-4E65-B804-0C51F33202E3
Topics
Community Discussion
No community discussion yet for this question.