Salesforce Exam CRT-450 Topic 7 Question 48 Discussion

Actual exam question for Salesforce's CRT-450 exam

Question #: 48
Topic #: 7

A developer has identified a method in an Apex class that performs resource intensive actions in memory by iterating over the result set of a SOQL statement on the account. The method also performs a DML statement to save the changes to the database.

Which two techniques should the developer implement as a best practice to ensure transaction control and avoid exceeding governor limits'*

Choose 2 answers

AUse the @ReadOnly annotation to bypass the number of rows returned by a SOQL.

BUse partial DML statements to ensure only valid data is committed.

CUse the System.limit class to monitor the current CPU governor limit consumption.

DUse the Database.Savepoint method to enforce database integrity.

Show Suggested Answer

Suggested Answer: B

by Gladys at Apr 09, 2024, 06:24 AM

Limited Time Offer

25%

Off

Get Premium CRT-450 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Marion

24 days ago

Haha, the read-only annotation? Really? That's like trying to solve a sudoku puzzle with a crayon. Nah, I'm going with B and D all the way. Partial DMLs and savepoints are the dynamic duo when it comes to governor limit shenanigans. Although, I have to admit, the mental image of a developer frantically monitoring the CPU limit with the System.limit class is pretty entertaining.

upvoted 0 times

...

Tien

26 days ago

Definitely B and D, folks. Partial DMLs and savepoints are the way to go. I mean, who wants to be the poor sap that hits the CPU limit and gets their code shut down? Not me, that's for sure. Although, I do have to say, the read-only annotation idea is kind of hilarious. It's like trying to outrun a speeding bullet with a toothpick!

upvoted 0 times

Daniel

5 days ago

Yeah, it's important to ensure only valid data is committed and enforce database integrity.

upvoted 0 times

...

Nadine

11 days ago

I agree, using partial DML statements and savepoints is definitely the way to go to avoid hitting governor limits.

upvoted 0 times

...

Haydee

1 months ago

Ah, the age-old battle against governor limits. I vote for B and D - partial DMLs and savepoints are the real MVPs here. Anything that helps me avoid the wrath of the Salesforce overlords is a winner in my book. Just don't try to pull a fast one with that read-only annotation, that's like trying to sneak past the bouncer with a fake ID.

upvoted 0 times

Leota

9 days ago

A) Use the @ReadOnly annotation to bypass the number of rows returned by a SOQL.

upvoted 0 times

...

Albert

14 days ago

D) Use the Database.Savepoint method to enforce database integrity.

upvoted 0 times

...

Caitlin

22 days ago

B) Use partial DML statements to ensure only valid data is committed.

upvoted 0 times

...

Tina

2 months ago

I'm not falling for that read-only trap! Bypassing the SOQL limit? No way, that's a surefire way to get your code shut down. Gotta use those partial DMLs and savepoints to stay on the safe side. Oh, and maybe throw in some comedy relief while you're at it - governor limits are so dry, we need a few good laughs to get through this!

upvoted 0 times

Jaime

26 days ago

A: Haha, we could all use a good laugh when dealing with those dry governor limits!

upvoted 0 times

...

Oliva

1 months ago

B: Definitely! Partial DMLs and savepoints are the way to go for sure.

upvoted 0 times

...

Rebecka

1 months ago

A: Yeah, I agree. Using @ReadOnly is risky business. Gotta be careful with those governor limits.

upvoted 0 times

...

Burma

2 months ago

Hmm, I think B and D are the way to go. Partial DML statements and database savepoints are the best practices here to ensure data integrity and avoid governor limit issues. Who needs read-only annotations when you have these powerful tools at your disposal?

upvoted 0 times