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

Integration in the enterprise – understanding the landscape

The digital enterprise landscape is continuously becoming more sophisticated. Gone are the days when the enterprise used to have less than 10 systems covering most of its business processes. Today's enterprises have hundreds, if not thousands, of different applications that are either bought, built in house, or a combination of both. This is in addition to a set of legacy systems that are still surviving the axe. Nowadays, it is very common to find that an enterprise has dozens of websites, multiple instances of ERP systems, and many other departmental applications, in addition to several data warehouses or lakes.

One of the reasons why enterprises end in such situations is because of the complexity associated with building business applications. Building a single application that runs all business processes is nearly impossible. Maintaining it and adapting to day-to-day business challenges and requested changes...