1Z0-116 · Question #71
Which two statements are true about Database Vault factors?
The correct answer is A. A factor can reference a function In another schema to compute its value, provided execute C. You can configure a factor to be evaluated only once per session. A is correct because Oracle Database Vault factors use PL/SQL retrieval methods to compute their values, and those functions can reside in any schema - as long as the DVF schema (or the executing context) has been granted EXECUTE privilege on that function. C is correct because…
Question
Which two statements are true about Database Vault factors?
Options
- AA factor can reference a function In another schema to compute its value, provided execute
- BChanging a factor type can change how factors are evaluated.
- CYou can configure a factor to be evaluated only once per session.
- DYou get an error at the time of factor creation If the retrieval method function you have specified
- EYou can use a factor to enforce conditions for a command rule.
How the community answered
(29 responses)- A83% (24)
- B3% (1)
- D10% (3)
- E3% (1)
Explanation
A is correct because Oracle Database Vault factors use PL/SQL retrieval methods to compute their values, and those functions can reside in any schema - as long as the DVF schema (or the executing context) has been granted EXECUTE privilege on that function. C is correct because factors have a configurable evaluation frequency; setting it to "Session" means the value is computed once and cached for the session, reducing repeated function calls for stable attributes like authentication method.
B is wrong because factor type is a classification label (e.g., "Oracle Label Security," "Context") - it does not control how or when the retrieval method is invoked. Evaluation behavior is governed by the evaluation option, not the type. D is wrong because Database Vault does not validate that the retrieval method function exists at creation time; the error only surfaces at runtime when the factor is first evaluated. E is wrong because factors cannot directly enforce command rule conditions on their own - they must be referenced inside a rule expression within a rule set, which is then associated with a command rule. The factor is an input, not an enforcer.
Memory tip: Think of factors as smart session variables - they can pull data from any schema (A), be cached once per login for efficiency (C), but they're just data sources; the rule set is what actually makes decisions (why E is false), and creation-time validation is deferred (why D is false).
Topics
Community Discussion
No community discussion yet for this question.