Question 21
Choose 1
As a part of business requirement , old CRM system needs to be integrated using Mule
application. CRM system is capable of exchanging data only via SOAP/HTTP protocol. As
an integration architect who follows API led approach , what is the the below step you will
perform so that you can share document with CRM team?
Correct answer:
C. Create WSDL specification using text editor
Explanation:
This question tests the understanding of how to apply API-led connectivity principles to a legacy SOAP-based system, specifically focusing on the design and specification phase.
Why D is correct:
The API-led approach emphasizes a contract-first design and creating reusable assets. The correct step for an Integration Architect is to create a well-defined contract to share with the CRM team for alignment.
The contract for a SOAP-based system is a WSDL (Web Services Description Language) file.
Design Center is the centralized tool within Anypoint Platform for designing APIs. It supports creating SOAP API specifications by importing an existing WSDL or by designing one graphically.
Creating the WSDL in Design Center (rather than a local text editor) makes it a reusable, discoverable asset within Anypoint Exchange, promoting governance and reuse across the organization. This aligns perfectly with the API-led methodology.
Let's examine why the other options are incorrect:
A. Create RAML specification using Design Center:
This is incorrect. RAML (RESTful API Modeling Language) is used for defining REST APIs, not SOAP web services. The CRM system uses SOAP/HTTP, so a REST contract is not the appropriate choice.
B. Create SOAP API specification using Design Center:
This wording is ambiguous, but it is essentially describing the correct action. However, option D is more precise because it explicitly names the artifact—the WSDL—which is the standard and correct term for a SOAP API's contract. Given the choice between a generic description and the precise technical term, the precise term (D) is the better answer.
C. Create WSDL specification using a text editor:
While technically possible, this goes against the collaborative and governed spirit of the API-led approach. Using a local text editor creates a siloed asset that is not easily shared, discovered, or governed within Anypoint Platform. The whole point of the platform is to use tools like Design Center to create assets that are automatically published to Exchange for the entire organization to use.
References/Key Concepts:
System API Layer:
In API-led connectivity, the integration with the legacy CRM would be encapsulated in a System API. The first step in building a System API is to define its interface, which in this case is a WSDL.
Contract-First Design:
The architect should design the contract (WSDL) before any implementation begins. This ensures both teams (integration and CRM) agree on the interface.
Anypoint Platform Tools:
Design Center is the designated tool for API design, and it supports both REST (RAML/OAS) and SOAP (WSDL) APIs.
This question tests the understanding of how to apply API-led connectivity principles to a legacy SOAP-based system, specifically focusing on the design and specification phase.
Why D is correct:
The API-led approach emphasizes a contract-first design and creating reusable assets. The correct step for an Integration Architect is to create a well-defined contract to share with the CRM team for alignment.
The contract for a SOAP-based system is a WSDL (Web Services Description Language) file.
Design Center is the centralized tool within Anypoint Platform for designing APIs. It supports creating SOAP API specifications by importing an existing WSDL or by designing one graphically.
Creating the WSDL in Design Center (rather than a local text editor) makes it a reusable, discoverable asset within Anypoint Exchange, promoting governance and reuse across the organization. This aligns perfectly with the API-led methodology.
Let's examine why the other options are incorrect:
A. Create RAML specification using Design Center:
This is incorrect. RAML (RESTful API Modeling Language) is used for defining REST APIs, not SOAP web services. The CRM system uses SOAP/HTTP, so a REST contract is not the appropriate choice.
B. Create SOAP API specification using Design Center:
This wording is ambiguous, but it is essentially describing the correct action. However, option D is more precise because it explicitly names the artifact—the WSDL—which is the standard and correct term for a SOAP API's contract. Given the choice between a generic description and the precise technical term, the precise term (D) is the better answer.
C. Create WSDL specification using a text editor:
While technically possible, this goes against the collaborative and governed spirit of the API-led approach. Using a local text editor creates a siloed asset that is not easily shared, discovered, or governed within Anypoint Platform. The whole point of the platform is to use tools like Design Center to create assets that are automatically published to Exchange for the entire organization to use.
References/Key Concepts:
System API Layer:
In API-led connectivity, the integration with the legacy CRM would be encapsulated in a System API. The first step in building a System API is to define its interface, which in this case is a WSDL.
Contract-First Design:
The architect should design the contract (WSDL) before any implementation begins. This ensures both teams (integration and CRM) agree on the interface.
Anypoint Platform Tools:
Design Center is the designated tool for API design, and it supports both REST (RAML/OAS) and SOAP (WSDL) APIs.
