Lesson 12 of 23 · All lessons
Salesforce Platform Administrator II
0 of 23 complete
1Exam Overview
  1. 1.1Platform Administrator II Complete Exam Overview
2Security and Access20%
  1. 2.1Sharing architecture: records, fields, and inherited access
  2. 2.2Profiles, permission sets, delegated administration, and
  3. 2.3Person accounts and complex account-contact models
3Objects and Applications19%
  1. 3.1Object relationships, record types, and schema design
  2. 3.2Applications, Lightning App Builder, Dynamic Forms, and
  3. 3.3Record types, page layouts, and related-list experience
4Auditing and Monitoring10%
  1. 4.1Debug logs and Setup Audit Trail
  2. 4.2Sensitive data, sandbox controls, and security review
  3. 4.3Reviewing security changes and pending access updates
5Cloud Applications11%
  1. 5.1Sales lifecycle: products, price books, schedules, orders, and
  2. 5.2Forecasting and Enterprise Territory Management
  3. 5.3Knowledge, entitlements, and service channels
  4. 5.4Salesforce product suite and platform extension choices
6Data and Analytics Management13%
  1. 6.1Data quality, validation, duplicates, enrichment, and archiving
  2. 6.2Complex reports, dashboards, and analytic design
  3. 6.3External data, backup and restore, and import methods
7Environment Management and Deployment
  1. 7.1Sandboxes, packages, and metadata movement options
  2. 7.2Change set composition, validation, and deployment practice
  3. 7.3Sandbox selection, refresh, and data protection
8Process Automation20%
  1. 8.1Choosing Flow, approvals, formulas, and legacy automation
  2. 8.2Order of execution, recursion, and automation interaction
  3. 8.3Automation troubleshooting, testing, and fault handling

Section 5 · Cloud Applications · 11% of exam

5.2 Forecasting and Enterprise Territory Management

3 min read Updated Nov 17, 2026

Exam objective

Distinguish the capabilities and implications of forecasting and Territory Management. Forecasting helps sales leaders estimate expected revenue or other configured measures over a period. Forecast categories classify opportunities by confidence or stage; forecast hierarchy determines whose forecasts roll up to managers. Forecast adjustments let authorized users account for judgment that is not represented by opportunity data, while opportunity ownership, splits, and product schedules can affect forecast calculations depending on configuration. A forecast is a planning view; it does not itself change an opportunity's stage or guarantee revenue. Before enabling or changing forecasting, clarify the forecast measure, time periods, currency behavior, hierarchy, categories, and which users participate. Review opportunity stages and category mappings because poor stage discipline undermines forecast quality. Managers need access to the relevant opportunities and forecast hierarchy. Configure custom forecast types only when the business has a defined measure and understands its source. Keep adjustments explainable and governed so the forecast is auditable as a management process.

Enterprise Territory Management supports assigning accounts and opportunities to territories using a territory model and rules. Territories represent market coverage such as geography, industry, or account segment. Users can belong to roles and territories; territory-based access can provide access to accounts and related records based on configured settings. A territory model has planning and activation states, and rule changes may require recalculation or model activation. Do not assume territories replace role hierarchy or that every access setting behaves identically across objects. Forecast hierarchy and territory hierarchy are different concepts. Forecast rollups follow the forecast hierarchy configuration and user relationships; territory access follows territory assignment and territory settings. A sales manager may need a forecast rollup for a team and separate territory access for a market. Changing one hierarchy to solve the other problem can grant the wrong visibility or distort reporting. Determine whether the request is about forecast aggregation, account assignment, opportunity access, or both.

Plan territory design around assignment criteria and change frequency. A rule-based model can scale when segments are predictable; manual assignments may be useful for exceptions but create governance work. Validate edge cases such as an account matching multiple rules, a changed territory boundary, users in multiple territories, and opportunities that should inherit or differ from account assignments. Test with representative users and inspect access after activation or recalculation. Align the model with compensation and sales operations policies.

Scenario method: if a leader asks for expected revenue by team, inspect forecast type, stage categories, hierarchy, and eligible opportunities. If a rep needs accounts in a defined market, inspect territory model, assignment rules, membership, and territory-based access. If the request includes both, solve them separately and verify their interaction. Document who owns assignment rules and who approves territory changes; otherwise operational changes can unexpectedly alter access and forecast visibility.

Exam focus: forecasting supports estimates and rollups; Territory Management supports market assignment and access. Recognize that they may interact but are not interchangeable. Check active model state, rules, user membership, stage-category mappings, and access consequences. Choose a design that supports the business's assignment logic without making the role hierarchy excessively complex.

Territory changes can affect record access and sales reporting. Validate assignments and access in a test environment and follow the organization's approval process before activating a model.

Historical comparisons require stable definitions. If territory boundaries change, prior-period reports may reflect a different assignment than current forecasts. Decide whether leadership wants results by the territory at transaction time or by today's territory model, and preserve the necessary snapshot or assignment history. Forecast adjustments should have owners and review expectations. Where users hold multiple roles or territories, inspect how rollups and access behave. A useful acceptance test compares expected account visibility and forecast totals for a small set of named users before activating the model for everyone.

Practical scenario

A regional VP needs to review expected quarterly revenue by sales team, while representatives must access accounts in assigned industry segments that cross geographic regions. Configure forecasting around the sales hierarchy and opportunity categories; configure territories around the account assignment model. Test forecast rollups and account access independently. Avoid changing role hierarchy solely to model industry territories.

Extra concept

Territory modeling is also a governance design. Define rule ownership, exception handling, model versioning, and review frequency. A technically valid assignment model can still produce poor access outcomes if no one maintains the criteria as the business changes.

Key takeaways

  • Forecasts estimate and roll up sales outcomes; territories assign market coverage and access.
  • Check forecast hierarchy and stage mappings separately from territory assignments.
  • Test model activation, territory membership, access, and forecast totals.
  • Official references: https://help.salesforce.com/s/articleView?id=005298969&language=en_US&type=1 https://help.salesforce.com/s/articleView?id=sf.forecasts3_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.admin_territories.htm&type=5

Check your knowledge

Answer exam-style Cloud Applications questions with answers and explanations.

Practice Cloud Applications
Finished this lesson? Mark it complete to track your progress.

Ready for the real exam?

Take the timed Salesforce Platform Administrator II simulator: same number of questions, same time limit.

Get Complete Access