Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce Exam Integration Architect Topic 5 Question 34 Discussion

Actual exam question for Salesforce's Integration Architect exam
Question #: 34
Topic #: 5
[All Integration Architect Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: B

by Marg at Apr 21, 2024, 02:43 AM

Limited Time Offer

25%

Off

Get Premium Integration Architect Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Beckie
10 months ago
Exactly. An API gateway seems to cover both security and return format requirements comprehensively.
upvoted 0 times
...
Krissy
10 months ago
But D doesn't address the need for different data formats for systems of engagement. It’s more about identity management.
upvoted 0 times
...
Kanisha
11 months ago
Hmm, that makes sense. What about D? An Identity Provider with SAML could handle security.
upvoted 0 times
...
Beckie
11 months ago
API gateways can manage all security protocols and format conversions centrally. It simplifies architecture.
upvoted 0 times
...
Celeste
11 months ago
Option B with the API gateway could work, but that feels like an extra layer of complexity. C keeps it more streamlined.
upvoted 0 times
Nettie
10 months ago
Yeah, it does seem like a simpler solution compared to option B.
upvoted 0 times
...
Paola
10 months ago
I think option C is the way to go.
upvoted 0 times
...
Melina
10 months ago
Yeah, an extra layer with the API gateway might be too complex.
upvoted 0 times
...
Silva
10 months ago
I think option C is the way to go, keeping it streamlined.
upvoted 0 times
...
Wendell
11 months ago
I agree, option C with enforcing separate security protocols and return formats at the second tier seems like a more streamlined approach.
upvoted 0 times
...
Julianna
11 months ago
Option B with the API gateway could work, but that feels like an extra layer of complexity.
upvoted 0 times
...
...
Cyndy
11 months ago
Why B though? Isn't it better to enforce security and return formats directly?
upvoted 0 times
...
Jonelle
11 months ago
Haha, I bet the developers are already dreading the 'different security protocols' requirement. Implementing that at the gateway seems like a nightmare!
upvoted 0 times
Lawrence
11 months ago
A) Enforce separate security protocols and return formats at the first tier of the API-led architecture.
upvoted 0 times
...
Rodolfo
11 months ago
B) Implement an API gateway that all systems of engagement must interface with first.
upvoted 0 times
...
...
Cyril
12 months ago
I agree with Alise. Keeping the security and formatting logic centralized in the middle tier is a good design pattern.
upvoted 0 times
...
Alise
12 months ago
Option C makes the most sense. Enforcing the security protocols and return formats at the second tier ensures consistency and flexibility across the API tiers.
upvoted 0 times
Leonida
10 months ago
It seems like option C is the best choice for UC's integration architecture.
upvoted 0 times
...
Tamra
10 months ago
Definitely. It would streamline the process for returning data to different systems of engagement.
upvoted 0 times
...
Louann
11 months ago
Enforcing it at the second tier also allows for easier management and scalability.
upvoted 0 times
...
Alex
11 months ago
I agree. It's important to have consistency in security protocols and data formats.
upvoted 0 times
...
Tori
11 months ago
That's a good point. It would definitely help in maintaining a standardized approach.
upvoted 0 times
...
Melinda
11 months ago
Option C makes the most sense. Enforcing the security protocols and return formats at the second tier ensures consistency and flexibility across the API tiers.
upvoted 0 times
...
...
Beckie
1 years ago
I think option B, implementing an API gateway, is the best choice.
upvoted 0 times
...
Tawny
1 years ago
That could work. It would centralize the handling of data formats and security protocols.
upvoted 0 times
...
Val
1 years ago
Or we could implement an API gateway that all systems of engagement must interface with first.
upvoted 0 times
...
Elly
1 years ago
Maybe we could enforce separate return formats at the second tier of the API architecture.
upvoted 0 times
...
Tawny
1 years ago
What about returning data in different formats?
upvoted 0 times
...
Val
1 years ago
That sounds like a good idea. It would ensure that each system of engagement has the appropriate security measures in place.
upvoted 0 times
...
Elly
1 years ago
I think we should enforce separate security protocols at the first tier.
upvoted 0 times
...

Save Cancel