Module: Big Object Basics -Salesforce answers

In this article we will see the solutions of Module: Big Object Basics -Salesforce Answers

#1.Get Started with Big Objects

Q1)Up to how many records can a big object hold?

I)100s
II)1000s
III)100,000s
IV)1,000,000s
V)1,000,000,000 (or more)


V)1,000,000,000 (or more)

Q2)What is a good use case for a custom big object?

I)Short-term storage of transaction data
II)Keeping track of transactions between big objects, standard objects, and custom objects
III)Keeping track of opportunities
IV)Maintaining a historical archive for analysis or compliance purposes
V)Working with big data on the go with the Salesforce app


IV)Maintaining a historical archive for analysis or compliance purposes

3What is the best way to query big objects if you’re working with an extremely large set of data?

I)SOQL
II)SOSL
III)Async SOQL
IV)Apex
V)You can’t query big objects.


III)Async SOQL

#2.Define Custom Big Objects

Hands-on Challenge
Earn+500 points

YOUR CHALLENGE
Create and Deploy a Custom Big Object
Create a custom big object that stores data from a car sharing service. Use the provided data to create then deploy a custom big object and its index in your Trailhead Playground.
#Define the custom big object.
#Label: Rider History
#Plural Label: Rider Histories
#Object Name: Rider_History

#Define the custom fields.
#Start Location Latitude
#Data Type: Number
#Field Label: Start Location Latitude
#Length: 7
#Decimal Places: 4
#Field Name: Start_Location_Latitude
#Required: No
#Start Location Longitude
#Data Type: Number
#Field Label: Start Location Longitude
#Length: 7
#Decimal Places: 4
#Field Name: Start_Location_Longitude
#Required: No
#Start Time
#Data Type: Date/Time
#Field Label: Start Time
#Field Name: Start_Time
#Required: Yes
#End Time
#Data Type: Date/Time
#Field Label: End Time
#Field Name: End_Time
#Required: No
#Service Type
#Data Type: Text
#Field Label: Service Type
#Length: 16
#Field Name: Service_Type
#Required: No
#Rider Account
#Data Type: Text
#Field Label: Rider Account
#Length: 16
#Field Name: Rider_Account
#Required: Yes
#Rider Rating
#Data Type: Number
#Field Label: Rider Rating
#Length: 2
#Decimal Places: 1
#Field Name: Rider_Rating
#Required: No

#Define the index:
#Label: Rider History Index
#Name: Rider_History_Index
#Index fields:
#Index Position 1: Rider_Account__c, Descending
#Index Position 2: Start_Time__c, Descending

#Deploy the Rider History big object.
My Trailhead Playground 1
Last used on 11/26/2021
Complete the Challenge to Earn 500Points

#3.Query Big Objects

Q1)Which scenario would Async SOQL be best used for?

I)You want to run a query, but plan to step out of the office for a few minutes.
II)You want to access the results immediately to use in Apex.
III)You need to run query against the fields in a big object’s index.
IV)You need to run a query against millions of records.


IV)You need to run a query against millions of records.

Q2)Which big object fields can you query for using standard SOQL?

I)You can query only the fields defined in the big object’s index, in the order they’re defined.
II)You can query any field.
III)You can query only Text and LongTextArea fields.
IV)You can query any field as long as it’s in the same order they’re defined in the big object’s object file.


I)You can query only the fields defined in the big object’s index, in the order they’re defined.

Q3)When should you use standard SOQL over Async SOQL?

I)You’re worried about the query timing out.
II)You need the results immediately.
III)You want to run a query outside of a big object’s index.
IV)You want to run an aggregate query.


II)You need the results immediately.

Spread the love

Leave a Reply

%d bloggers like this: