Book Image

Becoming a Salesforce Certified Technical Architect

By : Tameem Bahri
5 (1)
Book Image

Becoming a Salesforce Certified Technical Architect

5 (1)
By: Tameem Bahri

Overview of this book

Salesforce Certified Technical Architect (CTA) is the ultimate certification to validate your knowledge and skills when it comes to designing and building high-performance technical solutions on the Salesforce platform. The CTA certificate is granted after successfully passing the CTA review board exam, which tests your platform expertise and soft skills for communicating your solutions and vision. You’ll start with the core concepts that every architect should master, including data lifecycle, integration, and security, and build your aptitude for creating high-level technical solutions. Using real-world examples, you’ll explore essential topics such as selecting systems or components for your solutions, designing scalable and secure Salesforce architecture, and planning the development lifecycle and deployments. Finally, you'll work on two full mock scenarios that simulate the review board exam, helping you learn how to identify requirements, create a draft solution, and combine all the elements together to create an engaging story to present in front of the board or to a client in real life. By the end of this Salesforce book, you’ll have gained the knowledge and skills required to pass the review board exam and implement architectural best practices and strategies in your day-to-day work.
Table of Contents (21 chapters)
Section 1: Your Journey to Becoming a CTA
Section 2: Knowledge Domains Deep Dive
Section 3: Putting It All Together


In this chapter, we dived into the details of the Salesforce integration architecture domain. We learned what is expected from a CTA to cover and at what level of detail. We discovered the key Salesforce integration patterns, and we understood their importance and impact on the clarity of the designed solution.

We then tackled a mini hypothetical scenario that focused on integration architecture, and we solutioned it together and created some catching presentation pitches. We learned the structured way of designing an integration interface, and we came up against some interesting design decisions. We came across multiple examples where we used our diagrams to structure an end-to-end solution presented in an easy-to-follow way. We learned the negative impact of rushing to conclusions about the integration interfaces and how to avoid that.

We also covered other topics in the mini-scenario, including migrating users to new identity stores and dealing with partner users,...