Salesforce Certified MuleSoft Platform Architect Practice Questions

Salesforce Certified MuleSoft Platform Architect exam preparation

Salesforce Certified MuleSoft Platform Architect practice questions in English: 119 questions with explanations. The mock exam has 60 questions and 120 minutes.

Salesforce Certified MuleSoft Platform Architect free question 3 / 10 · Domain 3: Designing and sharing APIs

An API Designer project contains a root RAML file and a leftover JSON file from prototyping. Neither the root file nor any file it includes refers to the JSON file. The team publishes the project to Exchange as it is. How is the unreferenced file handled?

  1. No confirmation appears, and the whole project goes into the published asset
  2. Publishing is blocked until the unreferenced file has been deleted from the project
  3. A dialog asks whether to include it, and by default it is left out of the published project
  4. No confirmation appears, and by default the file is split off as a separate dependency asset
Show the answer and explanation

Answer: C

Why this is correct
The Publish an API Specification steps state that if the project includes files that are not referenced by the root file either directly or indirectly, a dialog asks you to confirm that you want to publish the project including them, and that by default API Designer excludes them from the published project in Anypoint Exchange. The Before You Begin section adds that unreferenced files are detected when you choose to publish, and you are given options on whether or not to publish them. The JSON leftover is unreferenced, so the dialog appears and the default is to leave it out.

Why the other options are wrong
"No confirmation appears, and the whole project goes into the published asset" … The page says a dialog asks you to confirm publishing the unreferenced files, and that API Designer excludes them by default.
"Publishing is blocked until the unreferenced file has been deleted from the project" … Removing unreferenced files first is described as good practice, but publishing is not blocked. Unreferenced files are detected when you publish, and you are given options on whether to include them.
"No confirmation appears, and by default the file is split off as a separate dependency asset" … The page describes a confirmation dialog and exclusion by default, not a separate dependency asset.

Asset version when publishing
A file counts as referenced when the root file reaches it through a chain of references, such as an include. The next section, Asset Version, says Anypoint Exchange requires an asset version number for each API specification you publish.

Go to the Salesforce Certified MuleSoft Platform Architect practice app (10 free questions; purchase unlocks all questions)

See the full practice set