MCPA-LEVEL-1 practice question 4 of 15

An organization makes a strategic decision to move towards an IT operating model that emphasizes consumption of reusable IT assets using modern APIs (as defined by MuleSoft). What best describes each modern API in relation to this new IT operating model?

Full set: 95 questions
Answer options
A: Each modern API has its own software development lifecycle, which reduces the need for documentation and automation
B: Each modem API must be treated like a product and designed for a particular target audience (for instance, mobile app developers) Correct answer
C: Each modern API must be easy to consume, so should avoid complex authentication mechanisms such as SAML or JWT D
D: Each modern API must be REST and HTTP based
Correct Answer:
B. Each modem API must be treated like a product and designed for a particular target audience (for instance, mobile app developers)
Explanation

In MuleSoft's recommended IT operating model, a "modern API" is treated as a product, not just a technical interface. This "product mindset" is crucial for driving the consumption and reuse of IT assets. It means each API is purposefully designed with a specific consumer or target audience in mind (e.g., internal developers, partners, or mobile app developers). This approach ensures the API is discoverable, well-documented, secure, and managed throughout its entire lifecycle, maximizing its value and adoption within the organization.

Why Incorrect

A. Modern APIs have a full software development lifecycle that increases the need for comprehensive documentation (for discoverability and consumption) and automation (for CI/CD and quality).
C. While modern APIs must be easy to consume, they must also be secure. Standard, robust authentication mechanisms like SAML or JWT are essential for security and are not avoided.
D. While REST over HTTP is a prevalent style for modern APIs, it is not a strict requirement. MuleSoft supports various specifications and protocols, including SOAP, GraphQL, and asynchronous protocols.

References

1. MuleSoft Whitepaper, "API-led connectivity: The next-generation of integration": This document emphasizes the shift in IT's role from a project-delivery function to a provider of reusable assets. It states, "To make these assets consumable, they must be 'productized' — packaged and documented for a specific audience, discoverable through a portal or exchange, and managed for performance and security." (Page 4, Section: "The new IT operating model").

2. MuleSoft Catalyst Knowledge Hub, "API Program and Strategy Best Practices": This resource details the importance of treating APIs as products. It notes, "Treating APIs as products means applying product management discipline to the API lifecycle... This includes understanding the target consumer, defining the value proposition, and ensuring a great developer experience." (Section: "Treat APIs as Products").

3. MuleSoft Documentation, "API-Led Connectivity": The official documentation explains that this approach is about "methodically connecting data to applications through reusable and purposeful APIs." The concept of being "purposeful" directly relates to designing an API for a specific audience and use case. (Anypoint Platform > Anypoint Platform for APIs > API-Led Connectivity).

Scroll to Top