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

Salesforce Exam MuleSoft Platform Architect I Topic 4 Question 13 Discussion

Actual exam question for Salesforce's MuleSoft Platform Architect I exam
Question #: 13
Topic #: 4
[All MuleSoft Platform Architect I Questions]

A client has several applications running on the Salesforce service cloud. The business requirement for integration is to get daily data changes from Account and Case

Objects. Data needs to be moved to the client's private cloud AWS DynamoDB instance as a single JSON and the business foresees only wanting five attributes from the

Account object, which has 219 attributes (some custom) and eight attributes from the Case Object.

What design should be used to support the API/ Application data model?

Show Suggested Answer Hide Answer
Suggested Answer: D

Correct Answer : A Non-Mule application

*****************************************

>> All type of Mule applications (Mule 3/ Mule 4/ with APIkit/ with Custom Java Code etc) running on Mule Runtimes support the Embedded Policy Enforcement on them.

>> The only option that cannot have or does not support embedded policy enforcement and must have API Proxy is for Non-Mule Applications.

So, Non-Mule application is the right answer.


Contribute your Thoughts:

Lyla
17 days ago
Option A, B, and C? More like A, B, and See ya later! Option D is the way to go, unless the client wants to play a game of 'guess how many attributes I have'.
upvoted 0 times
...
Blondell
21 days ago
That's a good point, Afton. It's important to consider the long-term implications of the design choice for the API/Application data model.
upvoted 0 times
...
Novella
21 days ago
Jester
upvoted 0 times
...
Afton
26 days ago
I disagree, I believe option C is the way to go. Starting with an Enterprise Data Model will ensure a more organized and scalable approach in the long run.
upvoted 0 times
...
Blondell
27 days ago
I think option A is the best choice because it combines the attributes in SAPI and filters them to provide the JSON output with only the required attributes.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77