Query Limits are used to manage Query environment in the repository for users and roles and
can_________.
A.
Control runaway queries
B.
Limit Queries by maximum run time
C.
Control aggregation
D.
Control User Authentication
E.
Control Write Back Capabilities
Explanation:
Query Limits. You can limit queries by the number of rows received, by maximum
run time, and by restricting to particular time periods. You can also allow or disallow direct
database requests or the Populate privilege.
See figure below.
There are 2 answers from the above list. B and E.
Option B –
Setting Query Limits
You can manage the query environment by setting query limits (governors) in the repository for particular application roles. You can limit queries by the number of rows received, by maximum run time, and by restricting to particular time periods. You can also allow or disallow direct database requests or the Populate privilege.
You should always set query limits for particular application roles rather than for individual users.
http://docs.oracle.com/cd/E23943_01/bi.1111/e10540/dataaccess.htm#BIEMG1437 —- Setting Query Limits Section
Option E –
Query Limit is also used to control Write back capabilities by allowing or disallowing the Execute Direct Database request option.
Refer to the link below.
http://obi4easy.blogspot.com/2013/04/writeback.html
No, the official answer is correct.
You can allow or deny direct DB requests in Query Limits.
Sure, it must be enabled for write-back, but write-back configuration
involves several steps, and this question assumes that you can do something that changes system behaviour in a single action.
B) e) are correct answers