PDI · Question #75
Which aspect of Apex programming is limited due to multitenancy?
The correct answer is D. The number of records returned from database queries. Salesforce's multitenant architecture imposes governor limits to ensure fair resource sharing among all tenants, which directly restricts the number of records that can be returned by database queries in Apex.
Question
Which aspect of Apex programming is limited due to multitenancy?
Options
- AThe number of active Apex classes
- BThe number of methods in an Apex Class
- CThe number of records processed in a loop
- DThe number of records returned from database queries
How the community answered
(27 responses)- B4% (1)
- C4% (1)
- D93% (25)
Why each option
Salesforce's multitenant architecture imposes governor limits to ensure fair resource sharing among all tenants, which directly restricts the number of records that can be returned by database queries in Apex.
While there are limits on the total number of Apex classes in an org, it's a metadata limit, not a direct limitation of multitenancy on programming execution.
There isn't a specific governor limit on the number of methods within a single Apex class; class size limits are typically based on compiled code size.
While processing large numbers of records in a loop can hit CPU time or DML limits, the core number of records processed itself is not a direct governor limit, but rather the operations performed on them are.
Due to Salesforce's multitenant architecture, governor limits are in place to prevent any single tenant from monopolizing shared resources. One significant governor limit is the total number of records that can be retrieved by SOQL queries (e.g., 50,000 records) within a single Apex transaction.
Concept tested: Apex governor limits (SOQL query limits)
Source: https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_gov_limits.htm
Topics
Community Discussion
No community discussion yet for this question.