Best Fit Solutions15% of the exam
Cross-component performance: caching, runtime settings and limits
Which performance lever to recommend across Omniscripts, Flexcards, Integration Procedures and Data Mappers: Enhanced Runtime Performance, metadata versus data caching (and when to turn the Scale Cache off), cache keys, Design Assistant recommended limits, Loop Block output and nesting, and LWR sites.
Recommend strategies for performance optimization strategies across all components (Omniscript load time, IP execution, Data Mapper queries) to ensure scalable and efficient solutions.
~8 min read · 9 practice questions ·
What the exam expects
- Recommend Enhanced Runtime Performance for faster run times and plan the user-mode access it brings.
- Tell metadata (definition) caching from data caching, show the benefit of each, and know why a changing input defeats the data cache.
- Recommend turning the Scale Cache off when components handle sensitive or user-specific data.
- Check a design against the Design Assistant recommended limits for Flexcards and Omniscripts.
- Keep loops lean (trimmed output, no nesting), use queueable remoting for CPU-heavy steps, and recommend LWR for slow Aura sites.
Key terms: Enhanced Runtime Performance (in-platform calls, user mode); metadata cache (component definitions); data cache (responses in Org or Session Cache); Scale Cache (the Standard Runtime cache implementation); Design Assistant (limit warnings in the designers).
Key facts
Enhanced Runtime Performance
- Detail
- In-platform capabilities instead of Apex calls; components run in user mode
Standard users with Enhanced Runtime Performance
- Detail
- Need a permission set granting Omni Interaction Access Configurations
Org Cache maximum time to live
- Detail
- 48 hours; non-sensitive, not user-specific data only
Session Cache maximum time to live
- Detail
- 8 hours; user-specific data
Data cache hit
- Detail
- Only when the same request input is provided again
Scale Cache
- Detail
- Can't be cleared; turned off with TurnOffScaleCache = true
Flexcard child Omniscripts and versions
- Detail
- 3 child Omniscripts, 10 versions
Nested Loop Blocks (managed package page)
- Detail
- Not supported; call a child procedure instead
Sources for this section (6)
- Omnistudio Settingshelp.salesforce.com (opens in a new tab)
- Enhanced Runtime Performance permission sethelp.salesforce.com (opens in a new tab)
- Improve Performance by Using Cachinghelp.salesforce.com (opens in a new tab)
- Supported Featureshelp.salesforce.com (opens in a new tab)
- Recommended Limitshelp.salesforce.com (opens in a new tab)
- Process Arrays Using Loop Blockshelp.salesforce.com (opens in a new tab)
- Why can't a consultant tune the Metadata Cache the way Org Cache and Session Cache are tuned?
- When should a Standard Runtime design use Session Cache instead of Org Cache?
- What does Design Assistant do when a component approaches, reaches or exceeds a recommended limit?
- How does the recommended Data Mapper count differ between a Flexcard and an Omniscript?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Omnistudio Consultant pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 31 lessons of the Omnistudio Consultant guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (9 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams