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

Designing the project environment and release strategy

Give yourself time to quickly skim through the scenario, understand the big picture, and develop some initial thoughts about the solution. This is a must-do step for every scenario. In this scenario in particular, you will find some requirements that are related to each other and can be clubbed together.

Understanding the current situation

We understand that PMF is using two different clouds. The scenario didn't specify that both these products are actually in the same environment, but considering the difficulties mentioned in release management, it is fair to assume so. Note that such a challenge would likely not happen with a multi-org setup.

PMF used VSC and Change Sets to deploy metadata between environments. What does that information tell us?

It probably indicates that no source control management is included, which means that changes cannot be tracked and tied back to a requirement. Moreover, that could...