INTEGRATION-ARCHITECTURE-DESIGNER practice question 18 of 25

Universal Containers (UC) currently owns a middleware tool and they have developed an API-led integration architecture with three API tiers. The…

Full set: 106 questions

Domain Design an Integration Solution

Universal Containers (UC) currently owns a middleware tool and they have developed an API-led integration architecture with three API tiers. The first tier interfaces directly with the systems of engagement, the second tier implements business logic and aggregates data, while the third tier interfaces directly with systems of record. Some of the systems of engagement will be a mobile application, a web application, and Salesforce. UC has a business requirement to return data to the systems of engagement in different formats while also enforcing different security protocols. What should an Integration Architect recommend to meet these requirements?

Answer options
A:

A. Enforce separate security protocols and return formats at the first tier of the API-led architecture.

B:

B. Implement an API gateway that all systems of engagement must interface with first.

Correct answer
C:

C. Enforce separate security protocols and return formats at the second tier of the API-led architecture.

D:

D. Leverage an Identity Provider solution that communicates with the API tiers via SAML

Correct Answer:
B. B. Implement an API gateway that all systems of engagement must interface with first.
Explanation

An API Gateway is the standard architectural component designed to be the single entry point for all client requests. It is specifically built to handle cross-cutting concerns such as enforcing diverse security protocols (e.g., OAuth for mobile, API Keys for web), performing protocol and data format transformations, and managing traffic. By implementing an API Gateway, Universal Containers can centralize policy enforcement and decouple these client-facing requirements from the backend API implementation. This allows the three API tiers to focus on their core responsibilities—experience, process, and system logic—while the gateway manages the complexity of interfacing with different systems of engagement.

Why Incorrect

A. Enforcing these policies at the first tier (Experience API) is possible but less efficient and scalable than using a dedicated gateway, which is designed for these edge-of-network tasks.
C. The second tier (Process API) is designed for reusable business logic, not for client-specific security or data formatting, which would violate the principles of API-led architecture.
D. An Identity Provider is a component for authentication and identity management; it does not address the requirement to transform data into different formats for various clients.

References

1. Salesforce Architects, "Architect's Guide to Integration Patterns and Practices": In the section discussing integration patterns, the API Gateway pattern is described as a single entry point for all clients that can handle cross-cutting concerns like authentication, authorization, and protocol translation. This aligns with the need to enforce different security protocols and formats.

2. MuleSoft Documentation, "API-led Connectivity": As the originator of the three-tier API-led architecture, MuleSoft (a Salesforce company) documentation consistently positions an API Gateway as the component responsible for securing, managing, and governing APIs. It acts as the proxy for backend services, applying security policies and mediating traffic from diverse consumers. See the "What is API-led Connectivity?" whitepaper.

3. N. Newman, "Building Microservices: Designing Fine-Grained Systems", 2nd Edition, O'Reilly Media: While not a Salesforce-specific source, this is a foundational text in modern architecture. Chapter 4, "The API Gateway," details the role of a gateway in handling authentication, authorization, and protocol/format translation for various clients, confirming this as a standard best practice.

Scroll to Top