Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Becoming a Salesforce Certified Technical Architect
  • Table Of Contents Toc
  • Feedback & Rating feedback
Becoming a Salesforce Certified Technical Architect

Becoming a Salesforce Certified Technical Architect

By : Bahri
5 (21)
close
close
Becoming a Salesforce Certified Technical Architect

Becoming a Salesforce Certified Technical Architect

5 (21)
By: Bahri

Overview of this book

This book is a complete guide to learning essential architectural concepts that’ll enable you to deliver secure, high-performant Salesforce solutions and pass the Salesforce CTA review board exam with confidence. This second edition comes with updated content, additional supporting material such as cheat sheets, and detailed practical examples, and helps you learn key soft skills to craft a winning presentation. You’ll begin by reviewing vital architectural concepts needed to create a scalable end-to-end Salesforce solution. Next, you’ll find out how to identify requirements and break down a problem into smaller, more solvable parts. As you advance, you’ll gain practical experience in managing design decisions and defending them using real-world scenarios. The book also helps familiarize you with the correct methodology to structure your solution presentation and the necessary supporting artifacts. Finally, you’ll practice providing solutions for two full hypothetical scenarios and structuring your playback step by step. By the end of this Salesforce book, you’ll be able to design a highly scalable Salesforce solution and create suitable material to comfortably explain the end-to-end solution to the CTA review board and potentially your customer, and have a higher chance of passing.
Table of Contents (18 chapters)
close
close

What Kind of Artifacts You Need to Generate and Why

A Salesforce Architect is always aiming at creating a secure and scalable solution that meets all required functionalities. In addition, the architect should also ensure the solution is documented in a way that allows it to be communicated effectively to the stakeholders. This is applicable both during the review board and while tackling a real-life implementation project.

An architecture diagram is a graphical representation of a set of concepts that are part of an architecture. They are heavily used in software architecture and, when used effectively, can become a common language for documenting and communicating your solution.

Based on experience, there are usually several discrepancies in the way architectural diagrams are created. They could be inconsistent, fragmented, or lacking some details. In several cases, these discrepancies can be traced back to the misuse of an architectural description language (for example, unified...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech
bookmark search playlist font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY