Which four are true about creating and running a remote database scheduler jobs? (Choose four.)

A database destination object is essential for remote jobs to specify the target database connection information, enabling the scheduler to execute tasks on the designated remote system.

Remote jobs execute on the target database, thus they must run under a user account that is defined on that specific remote database and possesses the necessary privileges for the job's operations.

Remote jobs run as a user defined on the remote database, not necessarily the same user who submitted the job on the local database.

While a credential object can define the remote user for a scheduler job, it is optional if the remote connection, such as one established via a database link, already encapsulates the necessary authentication details.

A credential is not always mandatory for remote jobs as other authentication methods, like database links with embedded credentials, can be employed.

To enable a single job to execute across multiple remote databases, a database destination group must be created to logically bundle several individual database destinations, allowing the job to target all group members.

A database destination is required to define the connection to the remote database, even if a database link is utilized as part of that destination's configuration.