Identify the solution that is both applicable and quick in this situation.

Your client wants to publish the same content to multiple formats, in multiple languages
periodically, using a batch publishing job. Your plane is leaving, and you have only 20 minutes left
to solve this problem.
Identify the solution that is both applicable and quick in this situation.

A.
Publish each format and language to a separate folder and create a separate command-line
entry for each of them.

B.
Publish all formats, create copies of the publishing folder, and customize Publishing.Project.xml
in each folder for language.

C.
Publish all formats in each language to a separate folder and create a separate command-line
entry for each.

D.
Publish to all languages separately in one format, and customize Publishing.Project.xml to add
formats.

Explanation:
Command-Line Publishing
You can launch the publishing process from a command line. This allows you to create a
batch publishing task that can be scheduled and run automatically at a time when the
server or network is not as busy, such as at night or on the weekend.
You must publish content first to create a publishing task. This creates a folder structure
and at least three files that are needed for command line publishing. The selection.xml,
publishing.project.xml and at least one configuration (<format_guid>.config.xml) files are
created at the root of the destination folder.
The selection.xml file contains a list of the documents to publish, the
publishing.project.xml contains global parameters that apply to all publishing formats and

a list of all configuration files (<format_guid>.config.xml) – one for each output format.
The <format_guid>.config.xml contains the parameters that apply to a particular format.
The output from command line publishing will be stored in the same location as it would
be if the publishing process was launched from within the Developer.
Oracle User Productivity, Content Development, Command-Line Publishing