Examine the command: SQL>DBMS_STATS.SET_TABLE_PREFS('SH','CUSTOMERS','PUBLISH','false'); Which statement describes the effect of the above command?

Setting PUBLISH to 'false' does not disable automatic statistics collection - the AUTOSTATS job still runs, but results are stored as pending instead of being published.

Locking statistics to prevent overwriting requires DBMS_STATS.LOCK_TABLE_STATS or LOCK_SCHEMA_STATS, not the PUBLISH preference.

Existing published statistics in the data dictionary remain valid and usable by the optimizer - only future gathered statistics are redirected to the pending area.

When the PUBLISH preference is set to 'false' using DBMS_STATS.SET_TABLE_PREFS, any statistics subsequently gathered on the CUSTOMERS table are stored in the pending statistics area (USER_TAB_PENDING_STATS) rather than being immediately written to the data dictionary. These pending statistics do not affect the query optimizer until explicitly published via DBMS_STATS.PUBLISH_PENDING_STATS, allowing DBAs to test new statistics before committing them.