1Z0-062 · Question #198
In your database instance, the RESOURCE_LIMIT parameter is set to TRUE. You create the profile: CREATE PROFILE app_user LIMIT SESSIONS_PER_USER 5 CPU_PER_SESSION UNLIMITED CPU_PER_CALL 3000 IDLE_TIME
The correct answer is B. These users can never reuse a password D. In each user session, the limit for LOGICAL_READS_PER_SESSION is the same as defined in. With PASSWORD_REUSE_MAX set to UNLIMITED, passwords can never be reused, and any profile limit not explicitly set inherits its value from the DEFAULT profile.
Question
In your database instance, the RESOURCE_LIMIT parameter is set to TRUE. You create the profile:
CREATE PROFILE app_user LIMIT SESSIONS_PER_USER 5 CPU_PER_SESSION UNLIMITED CPU_PER_CALL 3000 IDLE_TIME 10 PASSWORD_LIFE_TIME 60 PASWORD_REUSE_TIME 60 PASWORD_REUSE_MAX UNLIMITED Which two statements are true about users and their sessions that are subject to this profile?
Options
- AThe CPU_PER_CALL is ignored in the user sessions because of the unlimited value of
- BThese users can never reuse a password
- CThe PASSWORD_LIFE_TIME value is ignored because of the unlimited value of
- DIn each user session, the limit for LOGICAL_READS_PER_SESSION is the same as defined in
How the community answered
(42 responses)- A12% (5)
- B81% (34)
- C7% (3)
Why each option
With PASSWORD_REUSE_MAX set to UNLIMITED, passwords can never be reused, and any profile limit not explicitly set inherits its value from the DEFAULT profile.
CPU_PER_CALL and CPU_PER_SESSION are independent kernel-level resource limits enforced separately; an UNLIMITED value for CPU_PER_SESSION does not disable or override the CPU_PER_CALL limit of 3000.
When PASSWORD_REUSE_MAX is UNLIMITED, the user would need to change their password an unlimited number of times before reuse is permitted, a condition that can never be satisfied, so passwords are permanently non-reusable.
PASSWORD_LIFE_TIME is an independent password aging parameter and is not affected or overridden by the UNLIMITED setting on PASSWORD_REUSE_MAX.
Any resource or password limit not explicitly specified in a user-defined profile falls back to the value defined in the DEFAULT profile, so LOGICAL_READS_PER_SESSION is governed by whatever the DEFAULT profile specifies.
Concept tested: Oracle profile password reuse policy and DEFAULT profile inheritance
Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/dbseg/managing-security-for-oracle-database-users.html
Topics
Community Discussion
No community discussion yet for this question.