<< Prev Question Next Question >>
Question 31/50
A consultant is planning the ingestion of a data stream that has profile information including a mobile phone number.
To ensure that the phone number can be used for future SMS campaigns, they need to confirm the phone number field is in the proper E164 Phone Number format. However, the phone numbers in the file appear to be in varying formats.
What is the most efficient way to guarantee that the various phone number formats are standardized?
To ensure that the phone number can be used for future SMS campaigns, they need to confirm the phone number field is in the proper E164 Phone Number format. However, the phone numbers in the file appear to be in varying formats.
What is the most efficient way to guarantee that the various phone number formats are standardized?
Recent Comments (The most recent comments are at the top.)
The correct answer is:
A. Create a formula field to standardize the format.
Using a formula field during ingestion is the most efficient way to standardize phone numbers into the proper E164 format. Formula fields can transform the data as it is ingested, ensuring that all phone numbers conform to the required format without needing to modify the source system or manually edit dataCohort 20 Copy of AMER ….
Why not the other options?
B. Edit and update the data in the source system prior to sending to Data Cloud: This would be time-consuming and less efficient, especially for dynamic or large datasets.
C. Assign the PhoneNumber field type when creating the data stream: While assigning the field type is necessary, it doesn't automatically standardize phone numbers into E164 format.
D. Create a calculated insight after ingestion: Calculated insights are used for metrics and insights, not for transforming or standardizing data during ingestionCohort 20 Copy of AMER ….
It should be "A". The phone data type is modeled on the text data type. Any valid text value is accepted for ingestion into a phone data type field.
It should be "A". The phone data type is modeled on the text data type. Any valid text value is accepted for ingestion into a phone data type field.