The SQL Tuning Advisor has been configured with default configurations in your database instance. Which recommendation is automatically implemented without the DBA's intervention after the SQL…

Lena V.Mar 6, 2026

The correct answer is B, SQL profile recommendations. When the SQL Tuning Advisor runs automatically via the AUTOTASK framework (the Automatic SQL Tuning task that fires during the maintenance window), it will accept and implement SQL profile recommendations on its own if it determines the profile offers a significant performance benefit, typically a 3x or better improvement factor. The other three options all require explicit DBA review and manual action: statistics recommendations tell you what to gather but do not gather them, index recommendations go to the DBA to evaluate before any DDL runs, and restructuring suggestions are advisory only since the optimizer cannot rewrite your SQL for you. This auto-implementation behavior of SQL profiles is a favorite 1Z0-050 test point precisely because it is the one exception where the advisor does more than just advise.

Dervla O.Feb 6, 2026

Saw this exact stem on my 1Z0-050 sitting and the thing that saved me was reading it twice, specifically the phrase "without the DBA's intervention." That phrase is your eliminator. Index creation and statistics gathering both require a DBA to pull the trigger, and restructuring SQL means touching application code, which Oracle cannot do on its own. SQL profiles are the one output the AUTOTASK framework is permitted to implement automatically because a profile only instructs the optimizer, it does not alter schema objects or code. So when you see "automatically implemented" paired with "AUTOTASK," you are looking for the least invasive, non-schema-changing option, and B is the only one that fits that description. I almost burned time second-guessing C because index hints feel like optimizer guidance too, but indexes are schema objects and that distinction is the whole key.

Nina C.Feb 9, 2026

A is the trap here, SQL profiles auto-implement, so B.

Ingrid P.Feb 25, 2026

The distractor that burns people here is A, statistics recommendations, because AUTOTASK does run automatic statistics gathering as a separate maintenance task and your brain conflates the two. They are different jobs. The SQL Tuning Advisor is its own AUTOTASK component, and the only recommendation it implements on its own, without any DBA approval step, is the SQL profile, option B. Index recommendations and restructuring suggestions both require human sign-off because they carry real schema or code risk. If you are building a deck for this exam, the card I would write is: "SQL Tuning Advisor via AUTOTASK, auto-implements: SQL profiles only" and I would put statistics, indexes, and restructuring on the back as the three things that still need DBA action, because the exam likes to test that boundary specifically.

Viktor S.Feb 18, 2026

B is correct, and here is the why that actually matters. When the Automatic SQL Tuning task runs inside the AUTOTASK framework during the maintenance window, Oracle will automatically accept a SQL profile if it demonstrates a performance benefit of roughly three times or better, no DBA sign-off needed. The other three options are things the advisor recommends and then stops, because implementing new indexes or rewriting your SQL touches schema and application logic that Oracle has no business touching on its own. The sneaky wrong answer is A, because people conflate the auto stats gathering task with the SQL Tuning Advisor, but those are two separate AUTOTASK jobs, and the advisor recommending statistics does not mean it goes and gathers them. SQL profiles are metadata hints that Oracle can safely attach to a statement without restructuring anything, which is exactly why they are the one thing that gets the green light automatically.