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

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...