A company has defined two RAML fragments, Book Data Type and Book Example to be used in APIs. What would be valid RAML to use these fragments?

A. 1. #%RAML 1.0
2. title: Books
3. types:
4. Book: ABC/Examples/bookDataType.raml
5. /books:
6. post:
7. body:
8. application/json:
9. type: Book
10. examples:
11. input: ABC/Examples/bookExample.raml
12. responses:
13. 201:
14. body:
15. application/json:
16. example:
17. message: Book added
B. 1.#%RAML 1.0
2.title: Books
3.Book: !include bookDataType.raml
4./books:
5. post:
6. body:
7. application/json:
8. type: Book
9. examples:
10. input: !include bookExample.raml
11. responses:
12. 201:
13. body:
14. application/json:
15. example:
16. message: Book added
C. 1.#%RAML 1.0
2.title: Books
3.Book: bookDataType.raml
4./books:
5. post:
6. body:
7. application/json:
8. type: Book
9. examples:
10. input: bookExample.raml
11. responses:
12. 201:
13. body:
14. application/json:
15. example:
16. message: Book added
D. 1.#%RAML 1.0
2.title: Books
3.Book: bookDataType.raml
4./books:
5. post:
6. body:
7. application/json:
8. type: Book
9. examples:
10. input: bookExample.raml
11. responses:
12. 201:
13. body:
14. application/json:
15. example:
16. message: Book added
Explanation:
* RAML file contains lot of information that could be considered as "not API-describing".
Sort of "economy-class" members.
Equally important, but not necessarily part of the main RAML file.
* Through !includes, RAML allows us to build file-distributed API definitions, which is not
only useful to encourage code reuse but also improves readability.
* We can create RAML fragments with such code and then include them in main RAML
project using !include like:
types:
Book: !include bookDataType.raml and
examples:
input: !include bookExample.raml
* Additionally for
What is the difference between a subflow and a sync flow?
A. No difference
B. Subflow has no error handling of its own and sync flow does
C. Sync flow has no error handling of its own and subflow does
D. Subflow is synchronous and sync flow is asynchronous
Explanation:
Correct answer is Subflow has no error handling implementation where as sync flow has Subflow:
A subflow processes messages synchronously (relative to the flow that triggered its
execution) and always inherits both the processing strategy and exception strategy
employed by the triggering flow. While a subflow is running, processing on the triggering
flow pauses, then resumes only after the subflow completes its processing and hands the
message back to the triggering flow.
Synchronous Flow:
A synchronous flow, like a subflow, processes messages synchronously (relative to the
flow that triggered its execution). While a synchronous flow is running, processing on the
triggering flow pauses, then resumes only after the synchronous flow completes its
processing and hands the message back to the triggering flow. However, unlike a subflow,
this type of flow does not inherit processing or exception strategies from the triggering flow.
This type of flow processes messages along a single thread, which is ideally suited to
transactional processing.
A web client submits a request tohttp://localhost:8081/books/0471767840. The value
"0471767840" is captured by a Set Variable transformer to a variable named booklSBN.
What is the DataWeave expression to access booklSBN later in the flow?
A.
booklSBN
B.
attributes.booklSBN
C.
flowVars.booklSBN
D.
vars. booklSBN
vars. booklSBN
From which application , Organization Administrators can approve/revoke/delete SLA tier access requests.
A. API Exchange
B. API Portal
C. API Gateway
D. API Manager
Organization Administrators can approve/revoke/delete SLA tier access requests via API Manager only.
An API specification is designed using RAML. What is the next step to create a REST
Connector from this API specification?
A.
Download the API specification and build the interface using APIkit
B.
Publish the API specification to Any pointExchange
C.
Implement the API specification using flow designer in Design Center
D.
Add the specification to a Mule project's src/main/resources/api folder
Publish the API specification to Any pointExchange
What does C4E stands for in MuleSoft recommended IT operating model?
A. Centre for Empowerment
B. Centre for Engagement
C. Centre for Enablement
D. Centre for Excellence
Centre for Enablement (C4E) is an IT operating model that enables an enterprise to build reusable assets, accumulate API’s, leverage best practices and knowledge to enable self service and efficient delivery in the organization and implement new solutions faster.
Which of the below is not a valid category for connector type?
A. Gold
B. Select
C. Premium
D. Community
Gold is not valid category for connector types.

Refer tothe exhibit.
The Mule application Is debugged in Any point Studio and stops at the breakpoint What is
the value of the payload displayed In the debugger at this breakpoint?
A.
0
B.
"Processing"
C.
"Start"
D.
Complete"
"Start"
| Page 1 out of 29 Pages |