Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam CRT-450 Topic 3 Question 63 Discussion

Actual exam question for Salesforce's CRT-450 exam
Question #: 63
Topic #: 3
[All CRT-450 Questions]

A developer at AW Computing is tasked to create the supporting test class for a programmatic customization that leverages records stored within the custom object,

Pricing Structure c. AW Computing has a complex pricing structure for each item on the store, spanning more than 500 records.

hich two approaches can the developer use to ensure Pricing _Structure__c records are available when the test class is executed?

Choose 2 answers

Show Suggested Answer Hide Answer
Suggested Answer: A, C

Contribute your Thoughts:

Meghann
2 months ago
I think we should also consider using the @isTest(seeAllData=true) annotation to access the existing data in the org.
upvoted 0 times
...
Candida
2 months ago
I'm just imagining the developer trying to manually create 500 Pricing Structure records. Nope, nope, nope! A and C are the way to go.
upvoted 0 times
Edmond
1 months ago
Definitely, it's important to streamline the process for testing.
upvoted 0 times
...
Lynelle
1 months ago
Using data setup methods and test data import are much more efficient.
upvoted 0 times
...
Rene
2 months ago
Agreed, manually creating 500 records would be a nightmare.
upvoted 0 times
...
Brandon
2 months ago
A and C are definitely the way to go.
upvoted 0 times
...
...
Shaun
2 months ago
I agree with Loreta. Using Test.loadData{} method is a good approach for this scenario.
upvoted 0 times
...
Loreta
2 months ago
I think we should use the Test.loadData{} method to ensure Pricing_Structure__c records are available.
upvoted 0 times
...
Lanie
2 months ago
Haha, 'without shering'? I'm guessing that's supposed to be 'without sharing'. Gotta love those typos! A and C all the way.
upvoted 0 times
...
Pamela
3 months ago
Hmm, I'm not sure about B. Isn't using seeAllData=true generally frowned upon? Anyway, A and C for me.
upvoted 0 times
Jeanice
2 months ago
Yeah, using SeeAllData=true should be avoided if possible. A and C seem like the best choices here.
upvoted 0 times
...
Pearlene
2 months ago
I agree, and C is also a valid option by using the @isTest(SeeAllData=true) annotation.
upvoted 0 times
...
Chana
2 months ago
I think A is a good choice, we can create test data within the test class itself.
upvoted 0 times
...
...
Willie
3 months ago
Whoa, 500 records? That's a lot of data to load! I'd go with A and C too. Seems like the most efficient way to handle this.
upvoted 0 times
...
Kris
3 months ago
I think the correct answers are A and C. Using a Test Data Factory class allows you to create test data programmatically, while the Test.loadData() method lets you load data from a CSV file.
upvoted 0 times
Erin
1 months ago
It allows you to load data from a CSV file for testing.
upvoted 0 times
...
Pok
1 months ago
I think using the Test.loadData() method is also important.
upvoted 0 times
...
Coral
1 months ago
Yes, it helps in creating test data programmatically.
upvoted 0 times
...
Osvaldo
2 months ago
I agree, using a Test Data Factory class is a good approach.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77