Explanation
O12c is integrated in database don't have his own agent like in O11G then you cannot start up or shut down a database.

Tracing information is present in multiple trace files and you must use the trcsess tool to collect it into a single file.
Incorrect:
Not 1: Parameterservice_name
Name of the service for which tracing is enabled.
module_name
Name of the MODULE. An optional additional qualifier for the service.
Note:
* The procedure enables a trace for a given combination of Service, MODULE and ACTION name. The specification is strictly hierarchical: Service Name or Service Name/MODULE, or Service Name, MODULE, and ACTION name must be specified. Omitting a qualifier behaves like a wild- card, so that not specifying an ACTION means all ACTIONs. Using the ALL_ACTIONS constant achieves the same purpose.
*SERV_MOD_ACT_TRACE_ENABLE Procedure
This procedure will enable SQL tracing for a given combination of Service Name, MODULE and ACTION globally unless an instance_name is specified.
*DBMS_MONITOR.SERV_MOD_ACT_TRACE_ENABLE(
service_name IN VARCHAR2,
module_name IN VARCHAR2 DEFAULT ANY_MODULE,
action_name IN VARCHAR2 DEFAULT ANY_ACTION,
waits IN BOOLEAN DEFAULT TRUE,
binds IN BOOLEAN DEFAULT FALSE,
instance_name IN VARCHAR2 DEFAULT NULL);

Restrictions When Moving the Location of Online Data Files
*(Not B) The online move data file operation may get aborted if the standby recovery process
takes the data file offline, shrinks the file (not B), or drops the tablespace.
*(Not D?) The online move data file operation cannot be executed on physical standby while standby recovery is running in a mounted but not open instance.
*You cannot use the SQL ALTER DATABASE MOVE DATAFILE command to rename or relocate an online data file on a physical standby that is a fast-start failover target if the standby is mounted, but not open
*On a primary database, the online move data file operation cannot be executed on a file that belongs to a pluggable database (PDB) that has been closed on all instances of the primary database.
Note:
You can move the location of an online data file from one physical file to another physical file while
the database is actively accessing the file. To do so, you use the SQL statement ALTER
DATABASE MOVE DATAFILE.
An operation performed with the ALTER DATABASE MOVE DATAFILE statement increases the
availability of the database because it does not require that the database be shut down to move
the location of an online data file. In releases prior to Oracle Database 12c Release 1 (12.1), you
could only move the location of an online data file if the database was down or not open, or by first
taking the file offline.
You can perform an online move data file operation independently on the primary and on the
standby (either physical or logical). The standby is not affected when a data file is moved on the
primary, and vice versa.
Reference: Oracle Data Guard Concepts and Administration 12c, Moving the Location of Online
Data Files

B: SYSDG administrative privilege has ability to perform Data Guard operations (including startup and shutdown) using Data Guard Broker or dgmgrl.
D: SYSASM
The new (introduced in 11g) SYSASM role to manage the ASM instance, variable extent sizes to reduce shared pool usage, and the ability of an instance to read from a specific disk of a diskgroup E (Not A): SYSDBA is like a role in the sense that it is granted, but SYSDBA is a special built-in privilege to allow the DBA full control over the database Incorrect Answers:
C: SYSKM. SYSKM administrative privilege has ability to perform transparent data encryption wallet operations.
Note:
Use the V$PWFILE_USERS view to see the users who have been granted administrative privileges.

An Online Move data file operation is not compatible when: The data file is an OFFLINE data file A concurrent flashback database operation is executing A media recovery is completing A file shrink operation or tablespace offline/drop operation involving the same file is performing