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 Certified MuleSoft Platform Architect (Mule-Arch-201) Exam - Topic 4 Question 13 Discussion

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 CaseObjects. 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 theAccount 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?
D) Create separate entities for Account with five attributes and Case with eight attributes in SAPI, which are combined by the PAPI to provide JSON output containing 13 attributes.
A) Create separate entities for Account and Case Objects by mimicking all the attributes in SAPI, which are combined by the PAPI and filtered to provide JSON output containing 13 attributes.
B) Request client's AWS project team to replicate all the attributes and create Account and Case JSON table in DynamoDB. Then create separate entities for Account and Case Objects by mimicking all the attributes in SAPI to transfer ISON data to DynamoD for respective Objects
C) Start implementing an Enterprise Data Model by defining enterprise Account and Case Objects and implement SAPI and DynamoDB tables based on the Enterprise Data Model,

Salesforce Certified MuleSoft Platform Architect (Mule-Arch-201) Exam - Topic 4 Question 13 Discussion

Actual exam question for Salesforce's Salesforce Certified MuleSoft Platform Architect (Mule-Arch-201) exam
Question #: 13
Topic #: 4
[All Salesforce Certified MuleSoft Platform Architect (Mule-Arch-201) 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.


by Eva at Aug 27, 2024, 02:06 AM

Limited Time Offer

25%

Off

Get Premium Salesforce Certified MuleSoft Platform Architect (Mule-Arch-201) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Odette
9 months ago
Definitely surprised by the number of attributes in the Account object!
upvoted 0 times
...
Elinore
10 months ago
I think C could work too, but it feels a bit overkill for this case.
upvoted 0 times
...
Lorrine
10 months ago
Wait, why would we mimic all attributes? Seems unnecessary.
upvoted 0 times
...
Luann
10 months ago
I agree, less clutter is always better!
upvoted 0 times
...
Chan
10 months ago
Option D seems the most efficient, just pulling the needed attributes.
upvoted 0 times
...
Meaghan
10 months ago
I feel like option D is the most straightforward approach, but I wonder if we might miss some important data by only selecting those 13 attributes.
upvoted 0 times
...
Wilda
11 months ago
I keep getting confused between options A and B. I think both suggest replicating all attributes, but I’m not sure if that’s necessary for this integration.
upvoted 0 times
...
Marcos
11 months ago
I'm not entirely sure, but I think we practiced a similar question where we had to decide on data modeling. I feel like option C might be too complex for this scenario.
upvoted 0 times
...
Elvis
11 months ago
I remember we discussed the importance of minimizing data transfer, so option D seems like it could be the right choice since it only pulls the needed attributes.
upvoted 0 times
...
Alex
11 months ago
I think I understand the problem, but I want to make sure I'm not missing any important details before deciding on a design. I'll review the requirements one more time to be confident in my approach.
upvoted 0 times
...
Irene
11 months ago
I'm not sure about starting with an enterprise data model right away. That could add unnecessary complexity for this specific integration use case. I'll need to weigh the pros and cons of each approach.
upvoted 0 times
...
Gerry
11 months ago
Option D looks like the most efficient solution to me. Extracting just the required attributes and combining them in the PAPI seems like the cleanest way to handle this.
upvoted 0 times
...
Alayna
11 months ago
Hmm, I'm a bit confused by the different options. I'll need to review the requirements closely and consider the tradeoffs between creating separate entities versus replicating the data model.
upvoted 0 times
...
Shonda
11 months ago
This seems like a straightforward integration problem, but I'll need to think carefully about the best approach to minimize complexity and maintain flexibility.
upvoted 0 times
...
Dominic
11 months ago
This is a good question to test our understanding of business data. I think the key is to focus on the purpose and use of the data within the application's functional area. Option A seems to capture that the best.
upvoted 0 times
...
Lyla
1 year 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
Ty
1 year ago
I agree, Option D seems like the most efficient choice for this integration.
upvoted 0 times
...
Michel
1 year ago
Option D is definitely the way to go. Less hassle with all those attributes!
upvoted 0 times
...
...
Blondell
1 year 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
1 year ago
Jester
upvoted 0 times
Georgiana
1 year ago
D
upvoted 0 times
...
Georgiana
1 year ago
C
upvoted 0 times
...
Georgiana
1 year ago
A
upvoted 0 times
...
...
Afton
1 year 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
1 year 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