New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce ANC-301 Exam - Topic 12 Question 60 Discussion

Actual exam question for Salesforce's ANC-301 exam
Question #: 60
Topic #: 12
[All ANC-301 Questions]

A CRM Analytics consultant at Cloud Kicks is trying to upload data using an External Data API and the CSV file with the data was uploaded successfully. Upon analyzing the data using a lens, they find

they are unable to perform any mathematical operations as all the data and fields are treated as dimensions.

What is causing the problem?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

0/2000 characters
Stevie
2 months ago
Agreed, dimensions can't do math without proper setup!
upvoted 0 times
...
Loreta
2 months ago
I think it's the double quotes around the values.
upvoted 0 times
...
Mireya
3 months ago
Definitely need those transformations before the API call!
upvoted 0 times
...
Wynell
3 months ago
Wait, are we sure it's not just a formatting error?
upvoted 0 times
...
Gerardo
3 months ago
Sounds like a missing JSON file issue.
upvoted 0 times
...
Lisbeth
3 months ago
I feel like I've seen this before, but I can't recall if the JSON file is mandatory or if it's just a best practice.
upvoted 0 times
...
Noel
4 months ago
I practiced a similar question where transformations at the source were crucial. Maybe that's what we need to look at here?
upvoted 0 times
...
Layla
4 months ago
I'm not entirely sure, but I think if the values in the CSV are in double quotes, it could cause them to be treated as strings instead of numbers.
upvoted 0 times
...
Chandra
4 months ago
I remember something about needing a JSON metadata file for the data to be recognized correctly. That might be the issue here.
upvoted 0 times
...
Glendora
4 months ago
The key here is to make sure the data is properly transformed before uploading it. The External Data API expects a certain format, so we'll need to handle that at the source.
upvoted 0 times
...
Roosevelt
4 months ago
Okay, let me see. If the field values were enclosed in double quotes, that could be causing the issue. I'll make sure to check that in the CSV file.
upvoted 0 times
...
Shannon
5 months ago
Ah, I think I know what the problem is. The JSON metadata file wasn't uploaded, so the system doesn't know how to interpret the data properly.
upvoted 0 times
...
Lenora
5 months ago
Hmm, this seems tricky. I'm not sure what the issue could be, but I'll try to think it through step-by-step.
upvoted 0 times
...
Toi
5 months ago
But could it also be because the field values were in double quotes in the CSV file?
upvoted 0 times
...
Virgie
5 months ago
I agree with Tony, without the metadata file, the system won't recognize the data types.
upvoted 0 times
...
Derick
6 months ago
Wait, the data was in double quotes? That's like wrapping a present in another present. No wonder the system is confused!
upvoted 0 times
...
Viola
7 months ago
Hmm, this sounds like a classic case of not having the proper metadata file. I bet the JSON file is the culprit here. How else are they supposed to know which fields are dimensions and which are measures?
upvoted 0 times
Louvenia
5 months ago
C) Proper transformations need to be performed at the external source prior to External Data API callout.
upvoted 0 times
...
Gerardo
5 months ago
B) The field value added in the CSV file was contained within double quotes.
upvoted 0 times
...
Rocco
5 months ago
A) JSON metadata file was not uploaded along with the CSV data file.
upvoted 0 times
...
Lillian
5 months ago
B) The field value added in the CSV file was contained within double quotes.
upvoted 0 times
...
Lashanda
5 months ago
A) JSON metadata file was not uploaded along with the CSV data file.
upvoted 0 times
...
...
Tony
7 months ago
I think the problem is with the JSON metadata file not being uploaded.
upvoted 0 times
...

Save Cancel