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)
1
Section 1: Your Journey to Becoming a CTA
6
Section 2: Knowledge Domains Deep Dive
14
Section 3: Putting It All Together

Understanding what you should be able to do as a Salesforce data architect

According to Salesforce's online documentation, the CTA candidate should meet a specific set of objectives, all of which can be found at the following link: https://trailhead.salesforce.com/en/help?article=Salesforce-Certified-Technical-Architect-Exam-Guide&search=release+exam+schedule.

Let's have a closer look at each of these objectives.

Describing platform considerations, their impact, and optimization methods while working with LDV objects

First, you need to be able to identify an LDV. I use a simple mathematical method to identify LDVs, where an object has to meet at least one of the following conditions:

  • Has more than 5 million records
  • Has a growth rate that would lead to creating 5 million new records per year

In addition, some other indicators can point to an LDV use case, such as the following:

  • Having an org with thousands of active users who can access...