You're reading from Becoming a Salesforce Certified Technical Architect

Product type Book

Published in Feb 2021

Publisher Packt

ISBN-13 9781800568754

Pages 628 pages

Edition 1st Edition

Languages

Concepts

Software Architecture

Author (1):

Tameem Bahri

Table of Contents (21) Chapters

Preface

1. Section 1: Your Journey to Becoming a CTA

2. Chapter 1: Starting Your Journey as a CTA

3. Chapter 2: Core Architectural Concepts – Data

4. Chapter 3: Core Architectural Concepts – Integration and Cryptography

5. Chapter 4: Core Architectural Concepts – Identity and Access Management

6. Section 2: Knowledge Domains Deep Dive

7. Chapter 5: Developing a Scalable System Architecture

8. Chapter 6: Formulating a Secure Architecture in Salesforce

9. Chapter 7: Designing a Scalable Salesforce Data Architecture

10. Chapter 8: Creating a Lean Solution Architecture

11. Chapter 9: Forging an Integrated Solution

12. Chapter 10: Development Life Cycle and Deployment Planning

13. Chapter 11: Communicating and Socializing Your Solution

14. Section 3: Putting It All Together

15. Chapter 12: Practice the Review Board – First Mock

16. Chapter 13: Present and Defend – First Mock

17. Chapter 14: Practice the Review Board – Second Mock

18. Chapter 15: Present and Defend – Second Mock

19. Other Books You May Enjoy

Appendix: Tips and Tricks, and the Way Forward

Summary

In this chapter, we dived into the details of the Salesforce solution architecture domain. We learned what is expected from a CTA to cover and at what level of detail. We discovered the process of selecting the right combination of configurable and programmable features to deliver a requirement, and we discussed some guiding principles in selecting third-party solutions to deliver value in a short time.

We then tackled a mini hypothetical scenario that focuses on solution architecture, and we solved it together and created some catching presentation pitches. We practiced the process of selecting the right feature to deliver functionality, and we learned that it is not enough to simply mention the name of the used feature, but you have to clearly and crisply explain how it is going to be used, end to end, with no gaps and no ambiguity. If it isn't clear for you, then it won't be clear to your client, and then you can't expect your team to be able to deliver...