Which two types of data skew negatively affect performance in Salesforce?

The correct choice of account data skew and ownership skew directly relates to specific issues that can impact performance in Salesforce.

Account data skew occurs when a single account has an unusually high number of related child records. When many records are linked to one account, operations that require Salesforce to access or display that account can slow down due to contention for the account's resources. This can manifest as performance bottlenecks when many users are trying to access or manipulate these records simultaneously.

Ownership skew, on the other hand, occurs when one user or one group of users owns a disproportionate number of records. Similar to account data skew, this can lead to performance issues, especially during data operations like queries or updates. The heuristic driving this issue is that Salesforce's sharing and locking model can lead to contention when many records are owned by a single user. When this model is put under load—such as when multiple processes or users try to access or modify these records—it can lead to slower response times.

Both of these types of skew can impede the efficient processing of transactions within Salesforce, leading to degraded performance.

The other options do not accurately capture the specific types of skew that directly affect performance as they may relate to general concepts or different issues surrounding data management. For example,