Question 1
IntermediateInitiating Integration Solutions on the Anypoint Platform · Functional vs Non-Functional Requirements
A multinational retail corporation is initiating a digital transformation project to integrate its legacy ERP system with a new Salesforce CRM and several third-party logistics providers. The integration solution must adhere to strict Service Level Agreements (SLAs) regarding latency and throughput. Specifically, order updates must propagate to the CRM within 2 seconds, and the system must handle 500 orders per second during peak hours. During the initial architectural assessment using the MuleSoft Catalyst methodology, how should these requirements be classified and what is their primary impact on the Anypoint Platform deployment architecture?
Answer and explanation
Correct answer: A
Latency and throughput are classic non-functional requirements (NFRs). While functional requirements define what the system does (process orders), NFRs define how well it does it. These specific NFRs dictate the physical architecture (runtime plane), such as requiring the isolation and resource guarantees of Runtime Fabric or specific vCore sizing in CloudHub to meet the performance SLAs.
