Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam B2B Solution Architect Topic 10 Question 23 Discussion

Actual exam question for Salesforce's B2B Solution Architect exam
Question #: 23
Topic #: 10
[All B2B Solution Architect Questions]

Universal Containers (UC) is implementing a SalesforceB2B multi-cloud project with large volumes of data and daily transactions from multiple third-party systems via multiple integrations. UC is looking at transactions of more than 1 million records a week and, in higher seasons, 10 million records a week. UC has made the decision to get a full copy sandbox to use to test all of its third-party integrations across its multiple clouds. UC has also invested in MuleSoft and the Anypoint Platform as the single enterprise service bus for all of the third-party data going into Salesforce.

Which type of performance testing should a Solution Architect recommend for testing data at scale on this project?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

Mammie
1 months ago
I'm pretty sure the Avengers would step in and help with the performance testing. Captain America would definitely be on the API load testing team.
upvoted 0 times
Reynalda
2 days ago
B) I think Iron Man would be great at unit testing against the full copy sandbox codebase.
upvoted 0 times
...
Madalyn
12 days ago
A) Perform API load test against the full copy sandbox before go live.
upvoted 0 times
...
...
Nilsa
2 months ago
Hold on, why are we not considering page load testing in production? That's where the real action is, and we need to make sure the user experience is smooth.
upvoted 0 times
Lashon
16 days ago
C) Hold on, why are we not considering page load testing in production? That's where the real action is, and we need to make sure the user experience is smooth.
upvoted 0 times
...
Elke
19 days ago
B) Perform unit testing against the full copy sandbox codebase before go live in production.
upvoted 0 times
...
Gilma
20 days ago
C) Hold on, why are we not considering page load testing in production? That's where the real action is, and we need to make sure the user experience is smooth.
upvoted 0 times
...
Daniel
28 days ago
B) Perform unit testing against the full copy sandbox codebase before go live in production.
upvoted 0 times
...
Maybelle
29 days ago
A) Perform API load test against the full copy sandbox before go live.
upvoted 0 times
...
Carmelina
1 months ago
A) Perform API load test against the full copy sandbox before go live.
upvoted 0 times
...
...
Octavio
2 months ago
I'm not so sure about that. Unit testing the codebase seems like a better approach to me. That way, we can catch any bugs or performance issues at the code level.
upvoted 0 times
...
Lizette
2 months ago
The Hulk would smash that full copy sandbox if it couldn't handle the load!
upvoted 0 times
Andrew
21 days ago
D) Perform API load test against the partial copy sandbox before go live.
upvoted 0 times
...
Carolynn
27 days ago
A) Definitely, we don't want the Hulk smashing our system!
upvoted 0 times
...
Kimberlie
29 days ago
B) I agree, we need to make sure it can handle the volume of data.
upvoted 0 times
...
Keena
2 months ago
A) Perform API load test against the full copy sandbox before go live.
upvoted 0 times
...
...
Gerardo
2 months ago
I'm not sure, but I think option A makes sense because we need to ensure the system can handle the high volume of transactions.
upvoted 0 times
...
Keneth
3 months ago
I agree with Alonzo. It's important to test the performance of the integrations with such large volumes of data.
upvoted 0 times
...
Alonzo
3 months ago
I think we should go with option A and perform API load test against the full copy sandbox before go live.
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