Solution Architecture

Key Takeaways

Solution Architecture requires choosing the right blend of declarative and programmatic capabilities while evaluating build-vs-buy trade-offs. Know when to use Flow vs Apex, how to evaluate AppExchange packages with a TCO framework, and how modern platform features like Agentforce, OmniStudio, and Dynamic Forms change architectural decisions.

This domain covers selecting the right combination of declarative and programmatic functionality and evaluating external applications.

Objectives

• Appropriate combination of declarative and programmatic functionality
• Benefits, considerations, and trade-offs of incorporating external applications

Study Content

Core Topics

• Declarative vs Programmatic Solutions — Flow Builder vs Apex, automation strategy, order of execution, governor limits, and when to use each
• Build vs Buy & AppExchange Strategy — AppExchange evaluation framework, managed package considerations, TCO analysis, vendor scorecard, exit strategies
• AppExchange & ISV Landscape — Key ISV solutions by category (document gen, backup, data quality, DevOps, payments, CTI, iPaaS), vendor comparison tables, CTA scenario patterns
• Modern Platform Features — OmniStudio, Einstein AI, Agentforce, Dynamic Forms, External Services, LWC vs Aura vs Visualforce
• Agentforce Architecture — Atlas Reasoning Engine, Agent Builder, topics and actions, Trust Layer, Data Cloud grounding, deployment patterns, CTA scenario guidance

Product, Pricing & Commerce Architecture

• CPQ Architecture — Data model, pricing waterfall, rules engine, Advanced Approvals, CPQ vs Revenue Cloud, performance at scale, CTA scenario patterns
• Commerce Architecture — B2C vs B2B vs B2B2C, headless/composable commerce, Order Management, integration patterns, CTA commerce scenarios

Decision Guides & Analysis

• Decision Guides — Mermaid decision flowcharts for Flow vs Apex, build vs buy, LWC vs Aura, OmniStudio vs Flow, Screen Flow vs LWC
• Trade-Offs — Declarative vs programmatic, native vs AppExchange, configuration vs customization analysis
• Best Practices — Solution architecture patterns, anti-patterns, and design principles

Practice

• Domain Grilling: D4 Solution Architecture Q&A

Related Topics

Solution design requires balancing capabilities across multiple domains simultaneously:

• Security — Compliance and regulatory requirements shape which design patterns are permissible
• Integration — Available integration capabilities and middleware constrain solution choices
• Development Lifecycle — Delivery methodology, team skills, and release cadence influence build-vs-buy decisions

Frequently Asked Questions

What does the CTA exam test in Solution Architecture?

The CTA exam tests your ability to select the right combination of declarative and programmatic functionality, evaluate build-vs-buy decisions with TCO analysis, assess AppExchange packages against custom development, and leverage modern platform features like Agentforce, OmniStudio, and Dynamic Forms. You must justify why your chosen approach is better than alternatives.

How is Solution Architecture scored in the CTA review board?

Judges evaluate whether you follow a declarative-first approach with justified exceptions, whether your build-vs-buy analysis considers total cost of ownership (not just license cost), whether you demonstrate awareness of modern platform capabilities, and whether you can articulate the trade-offs of your chosen solution components compared to alternatives.

What are the most common mistakes in Solution Architecture during the CTA exam?

Candidates commonly fail by jumping to Apex when Flow Builder would suffice, not conducting a proper build-vs-buy analysis for AppExchange packages, ignoring exit strategy risks with third-party managed packages, overlooking OmniStudio or Agentforce as options for guided processes, and not addressing the order of execution implications when combining declarative and programmatic automation.

How should I approach build-vs-buy decisions at the review board?

Use a structured evaluation framework: assess the requirement fit, evaluate vendor stability and roadmap, calculate TCO over 3-5 years (license + implementation + maintenance + training), consider exit strategy and data portability, evaluate managed package governor limit impact, and assess the team’s ability to maintain custom code vs configure a package. Present at least two options with clear trade-offs.

When should I recommend Agentforce in a CTA scenario?

Recommend Agentforce when the scenario describes repetitive customer or employee interactions that follow predictable patterns, mentions reducing case volume or agent workload, or requires intelligent automation grounded in the organization’s data. Address the Atlas Reasoning Engine, Trust Layer for hallucination prevention, Data Cloud grounding requirements, and the build-out effort for topics and actions.