Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam Data Architect Topic 1 Question 47 Discussion

Actual exam question for Salesforce's Data Architect exam
Question #: 47
Topic #: 1
[All Data Architect Questions]

Northern Trail Outfitters is streaming IoT data from connected devices to a cloud database. Every 24 hours. 100,000 records are generated.

NIO employees will need to see these lol records within Salesforce and generate weekly reports on it. Developers may also need to write programmatic logic to aggregate the records and incorporate them into workflows.

Which data pattern will allow a data architect to satisfy these requirements, while also keeping limits in mind?

Show Suggested Answer Hide Answer
Suggested Answer: D

Persistence is the data pattern that will allow a data architect to satisfy the requirements, while also keeping limits in mind. Persistence means storing data from external sources in Salesforce objects, either standard or custom. This allows you to access the data within Salesforce and use it for reporting, analytics, workflows, and other features. Persistence also helps you avoid hitting API limits or performance issues when accessing large volumes of data from external systems. You can use various tools such as Data Loader, Bulk API, or Platform Events to persist IoT data from connected devices to a cloud database in Salesforce.


Contribute your Thoughts:

Derick
2 months ago
Haha, 'lol records'? Whoever wrote this question has a great sense of humor. I'm going with D. Persistence - you can't go wrong with good old-fashioned data storage.
upvoted 0 times
...
Keva
2 months ago
Hmm, I'm torn between B and D. Unidirectional integration might be more efficient, but persistence could give the developers more flexibility. Tough call!
upvoted 0 times
Berry
29 days ago
Let's weigh the pros and cons before making a decision.
upvoted 0 times
...
Van
1 months ago
But D could give us more flexibility in the long run.
upvoted 0 times
...
Audrie
1 months ago
I think B might be the way to go for efficiency.
upvoted 0 times
...
...
Stephen
2 months ago
D. Persistence for sure. Gotta keep those lol records safe and sound in the cloud! Weekly reports are gonna be a breeze.
upvoted 0 times
...
Theola
2 months ago
B. Unidirectional integration would work here, since the IoT data is only being streamed to the cloud and not coming back the other way. Plus, it's a simpler approach than bidirectional integration.
upvoted 0 times
Genevieve
1 months ago
C) Virtualization
upvoted 0 times
...
Eve
1 months ago
B. Unidirectional integration would work here, since the IoT data is only being streamed to the cloud and not coming back the other way. Plus, it's a simpler approach than bidirectional integration.
upvoted 0 times
...
Paris
1 months ago
B) Unidirectional integration
upvoted 0 times
...
Delpha
2 months ago
A) Bidirectional integration
upvoted 0 times
...
...
Cornell
2 months ago
I see your point, but I still think D) Persistence is the way to go to keep limits in mind.
upvoted 0 times
...
Brandee
2 months ago
I disagree, I believe C) Virtualization would be more efficient for this scenario.
upvoted 0 times
...
Alayna
3 months ago
I think the answer is D. Persistence. Storing the data in a cloud database and then accessing it through Salesforce and programmatic workflows seems like the best way to handle the high volume of records.
upvoted 0 times
Paulene
2 months ago
D) Persistence
upvoted 0 times
...
Malinda
2 months ago
C) Virtualization
upvoted 0 times
...
Margart
2 months ago
B) Unidirectional integration
upvoted 0 times
...
Candida
2 months ago
A) Bidirectional integration
upvoted 0 times
...
...
Edda
3 months ago
I think the best option is A) Bidirectional integration.
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