An on-demand transportation application has a Conversation preference data type. When customers use the application to request a ride, they can specify their conversation preference: whether they would like to talk to their driver or if they would prefer silence. Company stakeholders are interested in analyzing the conversation preference data.
How is the Conversation preference data type sourced?
For an on-demand transportation application collecting conversation preferences from customers, the nature of the data---preferences stated during the booking process---suggests it is generated dynamically rather than stored in a pre-existing database.
B . No system of record: This option acknowledges that conversation preferences are specified by customers in real-time and are specific to each ride request, rather than being pulled from a pre-established database (local or external). The data is generated by user input within the application itself and used for analysis without necessitating a traditional system of record for storage.
A local system of record (A) refers to data stored within the application's database but is more relevant for static or semi-static data rather than dynamic preferences. An external system of record (C) is used for data that the application retrieves from outside sources, which does not
Antonio
12 hours agoAudria
6 days agoScarlet
11 days agoLashawna
16 days agoKanisha
21 days agoVan
26 days agoJoanne
1 month agoBerry
1 month agoTalia
1 month agoArlen
2 months agoAudra
2 months agoDudley
2 months agoBlondell
2 months agoAliza
2 months agoYuriko
2 months agoPamella
3 months agoChanel
3 months agoGalen
3 months agoMarguerita
3 months ago