Salesforce Updated Salesforce-MuleSoft-Developer-I Exam Questions and Answers by maira

Correct answer is Change the method attributes value to "POST".

It can be fixed in either of the two ways as below.

1) Changing method attribute to POST in ClientRequestFlow

2) Setting allowedMethods as PUT in ShippingFlow (but doesn't fit as question mentions about changing ClientRequestFlow)

APIKIt Creates a separate flow for each HTTP method

Lets revise few concepts RAML which can help us to find the answer of this question.

URI Parameters

Lets have a look at below example.

/foos:

/{id}:

/name/{name}:

Here, the braces { } around property names define URI parameters. They represent placeholders in each URI and donot reference root-level RAML file properties as we saw above in the baseUri declaration. The added lines represent the resources /foos/{id} and /foos/name/{name}.

Query Parameters

Now we'll define a way to query the foos collection using query parameters.Note that query parameters are defined using the same syntax that we used above for data types:

/foos:

get:

description:ListallFoosmatching query criteria,ifprovided;

otherwise list allFoos

queryParameters:

name?:string

ownerName?:string

Based on the above information , below is the only option which defines storeid as uri parameter and department as query parameter.

/{storeId}:

get:

queryParameter:

department:

client-id-required enforces clients to add client_id and client_secret.

Please refer to below steps.

Add a section called traits: at the root level to define query parameters:

traits:

- client-id-required:

queryParameters:

client_id:

type: string

client_secret:

type: string

2) Reference the trait in each of the methods to specify that each of the methods require these queryparameters. After each method in the RAML file, add is: [client-id-required]. For example:

/users:

get:

is: [client-id-required]

description: Gets a list of JSONPlaceholder users.