Salesforce Certified Platform Data Architect (Plat-Arch-201) Exam - Topic 1 Question 47 Discussion

Actual exam question for Salesforce's Salesforce Certified Platform Data Architect (Plat-Arch-201) exam

Question #: 47
Topic #: 1

[All Salesforce Certified Platform Data Architect (Plat-Arch-201) 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?

ABidirectional integration

BUnidirectional integration

CVirtualization

DPersistence

Show Suggested 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.

by Tamesha at Sep 18, 2024, 03:59 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Lucy

3 months ago

Totally agree, unidirectional keeps it simple and effective!

upvoted 0 times

...

Pete

3 months ago

Wait, can Salesforce even handle that volume efficiently?

upvoted 0 times

...

Joesph

3 months ago

Persistence seems like the way to go for reporting.

upvoted 0 times

...

Suzi

4 months ago

I think unidirectional integration makes the most sense here.

upvoted 0 times

...

Gearldine

4 months ago

100,000 records daily? That's a lot!

upvoted 0 times

...

Christene

4 months ago

Virtualization sounds like it could work, but I feel like it might not handle the volume of records efficiently.

upvoted 0 times

...

Glen

4 months ago

I practiced a similar question about data persistence, but I can't recall if it applies here since we need real-time access.

upvoted 0 times

...

Olive

4 months ago

I think unidirectional integration might be the right choice since it seems simpler for just pulling data into Salesforce.

upvoted 0 times

...

Edgar

5 months ago

I remember studying data integration patterns, but I'm not entirely sure which one fits best here.

upvoted 0 times

...

Shawnee

5 months ago

Piece of cake! Unidirectional integration is the way to go here. It'll let us get the data into Salesforce without any unnecessary complexity.

upvoted 0 times

...

Kenda

5 months ago

Okay, I've got a strategy - I'll focus on the need to get the data into Salesforce and generate reports. That should help me narrow down the best approach.

upvoted 0 times

...

Jannette

5 months ago

Hmm, I'm a bit confused by the mention of "limits" in the question. I'll need to think carefully about the tradeoffs between the different options.

upvoted 0 times

...

Eulah

5 months ago

This looks like a classic data integration problem. I think the key is to consider the requirements around real-time access and reporting.

upvoted 0 times

...

Nieves

5 months ago

Okay, I've got this. Based on my understanding, Database Express allows you to view performance and status information, start up and shut down the database, and manage users and security. I'll select those three options.

upvoted 0 times

...

Derick

1 year 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

1 year 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

1 year ago

Let's weigh the pros and cons before making a decision.

upvoted 0 times

...

Van

1 year ago

But D could give us more flexibility in the long run.

upvoted 0 times

...

Audrie

1 year ago

I think B might be the way to go for efficiency.

upvoted 0 times

...

Stephen

1 year 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

1 year 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 year ago

C) Virtualization

upvoted 0 times

...

Eve

1 year 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 year ago

B) Unidirectional integration

upvoted 0 times

...

Delpha

1 year ago

A) Bidirectional integration

upvoted 0 times

...

Cornell

1 year 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

1 year ago

I disagree, I believe C) Virtualization would be more efficient for this scenario.

upvoted 0 times

...

Alayna

1 year 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