1Z0-050 · Question #98
The following command is executed to create the baseline template: SQL> EXECUTE DBMS_WORKLOAD_REPOSITORY.CREATE_BASELINE_TEMPLATE(START_TIME=> TO_TIMESTAMP(SYSDATE+2)…
The correct answer is A. It creates a baseline template that never expires. See the full explanation below for the reasoning.
Question
The following command is executed to create the baseline template:
SQL> EXECUTE DBMS_WORKLOAD_REPOSITORY.CREATE_BASELINE_TEMPLATE(START_TIME=> TO_TIMESTAMP(SYSDATE+2), END_TIME=>TO_TIMESTAMP(SYSDATE+10), BASELINE_NAME=>'Mybase4', TEMPLATE_NAME=>'Mytemp4', EXPIRATION=>NULL); Which statement is true about the effect of the above command?
Options
- AIt creates a baseline template that never expires.
- BIt produces an error because no snapshot information is provided to create the baseline.
- CIt creates a baseline template that expires after the Automatic Workload Repository (AWR) retention
- DIt creates a repeating baseline template that repeats after the Automatic Workload Repository (AWR)
How the community answered
(23 responses)- A78% (18)
- B4% (1)
- C13% (3)
- D4% (1)
Community Discussion
8
Dervla O.Dec 27, 2025The correct answer is A. The EXPIRATION parameter set to NULL is the controlling detail here, and Oracle documentation is explicit that passing NULL for expiration means the template persists indefinitely. Read the stem twice and you will notice that the question is not asking about snapshots at all, so B collapses on its own premise. C and D both try to tie the behavior to AWR retention or a repeating schedule, neither of which is triggered by this syntax. On elimination alone you can land on A, but knowing that NULL equals no expiration locks it in cold.
Mei-Ling H.Jan 12, 2026A is right. EXPIRATION=>NULL means the template never expires.
Anjali D.Jan 1, 2026Our group landed on A pretty quickly once someone pointed out that passing NULL for EXPIRATION is the key signal here, since the Oracle docs treat NULL as "no expiration" rather than as a missing or invalid value. Can anyone explain why they think B is tempting on first read, and what would actually need to be different in the command for that error condition to apply?
Carlos M.Jan 2, 2026B makes sense as a trap because if the syntax required a keyword like UNLIMITED or DEFAULT instead of NULL, you would get an error, so the distinction hinges entirely on whether that specific parameter is documented to accept NULL as a valid sentinel value, which the Oracle docs confirm it does here.
Brenda K.Dec 17, 2025Quick win, 30 seconds tops: EXPIRATION=>NULL means it lives forever, pick A.
Mei-Ling H.Dec 18, 2025Agree on A, but I would say "lives forever" is a little loose since the item still goes away if you delete it manually or drop the table, and if the exam question uses the word "automatically" then that is the exact qualifier that locks in the NULL-means-no-auto-expiry logic.
Carlos M.Dec 7, 2025EXPIRATION=>NULL is the key, that means the template never expires, so A is correct. D tries to trick you into thinking "repeating" but there is no REPEAT_INTERVAL set here, so that is not what is happening.
Brenda K.Dec 9, 2025Carlos is right that A locks in fast, but flag D for a second look anyway because on the real exam they sometimes pair a NULL EXPIRATION with a REPEAT_INTERVAL elsewhere in the same question stem and that reuse of the same visual pattern is exactly how they bait you into a wrong click under time pressure.