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

Summary

In this chapter, we dived into the details of the Salesforce development life cycle and deployment domain. We learned what is expected from a CTA to cover and at what level of detail. We discussed some key principles, such as DevOps, CI/CD, multi-layered development environments, and SCM. Then, we understood their importance and their impact on the development and release cycle.

As you might have already noticed, the scope of this domain is limited. The key challenge with such types of domains is in their depth of knowledge, understanding why some best practices are there, and how to implement them.

Then, we tackled a mini hypothetical scenario that focused on development life cycle and deployment, and we solutioned it together and created some catchy presentation pitches. We developed a development and release diagram that could be easily reused for other scenarios (with minor changes), and we learned how to present this to an audience to capture their attention and...