what 3 design examples will negatively impact the scale and performance of the revenue cloudimplementation?

[References: 1, , https://trailhead.salesforce.com/content/learn/modules/scalability-with-salesforce/understand-scalability-at-salesforce, , Design examples that can negatively impact the scale and performance of the Revenue Cloud implementation include using multiple automation types on a single object, making external API calls within the pricing sequence, and extensively using custom fields on quote lines. Multiple automations on a single object can lead to complex logic processing and increased execution times, impacting overall system performance. External API calls within pricing sequences can introduce latency and potential points of failure, affecting the responsiveness and reliability of pricing calculations. Additionally, an excessive number of custom fields on quotelines can increase the data load and processing time during quote generation and manipulation, further degrading system performance. These design considerations are critical for maintaining optimal performance and scalability in Revenue Cloud implementations., , ]