1Z0-050 · Question #94
Your company wants to upgrade the current production database to the RAC environment. To perform testing before migrating to the RAC environment, you performed the workload capture on the production…
The correct answer is C. 1, 4, 5, 3 (2 is not required.). See the full explanation below for the reasoning.
Question
Options
- A2, 1, 5, 3, 4
- B1, 2, 4, 5, 3
- C1, 4, 5, 3 (2 is not required.)
- D1, 2, 4, 5 (3 is not required.)
- E1, 4, 3, 5 (2 is not required.)
How the community answered
(26 responses)- A4% (1)
- B4% (1)
- C81% (21)
- D12% (3)
Community Discussion
8
Anjali D.Jan 14, 2026The correct answer is C, the sequence being preprocess the workload first, restore the test database to the capture start point, remap connections for the RAC environment, then set up the Replay Clients. Restarting in RESTRICTED mode is not actually required for workload replay, and the Replay Clients come last because they cannot be configured until the database is restored and connections are remapped. Does anyone in the group remember seeing RESTRICTED mode come up in the official Oracle docs for this workflow, or did we all land on the same conclusion that it just does not belong here?
Carlos M.Jan 15, 2026Restricted mode is called out in older 11g replay guides as an optional step for ensuring no stray sessions interfere, so it is not total noise, but you are right that it is not a required sequence step and does not belong in the ordered list.
Dervla O.Jan 8, 2026The stem is testing whether you know that RESTRICTED mode is not part of the Database Replay workflow, and B is the trap that catches people who hear "replay on a controlled test system" and assume you lock the database down first. Read it twice and you will notice the stem never introduces any scenario that would call for restricted mode, so any option containing step 2 is already suspect. Preprocessing the capture files has to come first because the replay engine cannot read raw capture data, full stop, and after that you restore to the capture start point so you have a clean baseline, then remap connections to fit the test environment, then stand up your replay clients and go. C is the answer, and the parenthetical in C is doing real work here, it is not just a footnote, it is the whole point of the question. If you are torn between B and C on test day, ask yourself whether the question gave you any reason to restrict access to the database, and if the answer is no, eliminate every option that includes step 2.
Carlos M.Dec 22, 2025Has to be A, restart restricted before remapping anything makes total sense.
Dervla O.Dec 24, 2025The restart restriction applies only to the specific subsystem being reconfigured, not to the entire process, which is why C holds up under the stem's exact wording. A is a common pull because it sounds procedurally safe, but the question is testing sequence logic, not general caution.
Brenda K.Dec 27, 2025Two is first because you cannot preprocess without a running database, fight me.
Anjali D.Dec 28, 2025Brenda, I hear you, but the group landed on C because that step can actually be completed before the database instance is active, so the dependency you're describing runs in the other direction. Happy to walk through the sequence again if it helps clarify where option 2 fits later in the order.
Mei-Ling H.Jan 22, 2026The correct sequence is C: preprocess first, restore the database to the capture point, remap connections, then set up the Replay Clients, and step 2 (RESTRICTED mode restart) is NOT required for workload replay. A lot of people get tripped up by step 2 because some Oracle maintenance tasks do require RESTRICTED mode, so it looks familiar and "safe" to include, but the Database Replay process does not mandate it. The word "required" in the question is the qualifier to watch here, since technically you could put the database in RESTRICTED mode, but the documented replay procedure does not list it as a required step. Also notice option B tries to sneak in that RESTRICTED restart between preprocess and restore, which breaks the logical order anyway because you obviously need to restore to the capture SCN before you can remap connections or start clients.