Make Solutions Trusted

Learning Objectives

After completing this unit, you’ll be able to:

Explain the importance of building a trusted solution.
Follow Salesforce Well-Architected best practices for building a trusted solution.

Protect the Business

As a Salesforce architect, it’s crucial to understand how to build a trusted solution that protects your business and stakeholders by behaving in ways that are secure, compliant and reliable. To achieve this, you need to plan carefully and collaborate with stakeholders across your business. Consider factors like organizational security, session security, ethical standards, availability, performance, and scalability.

This unit provides a solid grasp on building trusted solutions and their role in a well-architected Salesforce environment.

Build Trust

Ruth pointing to the Salesforce Well-Architected Framework Trusted capability with three behaviors: Secure, Compliant and Reliable.

Trust between the users and the solution is essential for the success of any business.

“An image showing the Secure behavior”

A Trusted Solution Is Secure

It controls access and protects sensitive data, ensuring that only authorized users have access to it. This is crucial in today's world, where data breaches and cyberattacks are becoming increasingly common.

To build a secure solution, prioritize three dimensions: organizational security, session security, and data security. By creating a secure solution, you are not only protecting your business and stakeholders, but also building trust with your customers.

“An image showing the Compliant behavior”

A Trusted Solution Is Compliant

It follows legal and ethical guidelines. This is important to maintain the integrity of the business and ensure that it operates within the boundaries of the law.

To build a compliant solution, prioritize three dimensions: legal adherence, ethical standards, and accessibility. By following these guidelines, you’re protecting your business from potential legal repercussions and ensuring you’re serving all users equitably. And you're also showing your commitment to ethical business practices, which can enhance your reputation.

“An image showing the Reliable behavior”

A Trusted Solution Is Reliable

It operates efficiently and dependably, allowing users to get their work done without any disruptions. Reliable architectures are available when and where users expect.

To build a reliable solution, prioritize three dimensions: availability, performance, and scalability. When you do, your business can trust that your solution will perform consistently, and scale with the business.

You might be wondering if you’re thinking about the dimensions highlighted above in the right way. Never fear, Salesforce Well-Architected has you covered. Each behavior-specific Well-Architected white paper is bursting with opinionated guidance on what you should consider when designing trusted solutions. In the next section we cover the patterns you can follow to ensure you’re considering all the right things!

Follow Well-Architected Best Practices to Build Trust

The following is a list of patterns you can follow to build a trusted solution. This isn’t an exhaustive list, but something to help get you started. Always refer to the full list of trusted patterns and anti-patterns as you roadmap and design your solution.

Secure Patterns

This table shows you a few examples of what good looks like when designing a solution that controls access and protects data. It also shows you the location where you can look for the presence (or absence) of the pattern, and how this pattern maps to the dimensions and considerations in the Well-Architected white papers where you can learn more.

Patterns: What Does a Good Pattern Look Like?	Location: Where to Look?	Resources: Learn More About Dimensions \| Considerations
API Access Control prevents users from authenticating via an unauthorized connected app.	In your org	Organizational Security \| Authentication
Every user and system with access to Salesforce maps to one or more personas in a security matrix.	In your documentation	Organizational Security \| Authorization
Standards are defined for the activities that require elevated session-level security.	In your org	Session Security \| Session Management
Salesforce mobile connected app configuration requires PIN/passcode unlock after inactivity.	In your org	Session Security \| Device Access
Regular reviews of audit history and reports take place.	In your company	Session Security \| Threat Detection and Response
All code accessing data (SOQL/SOSL) or performing data operations (DML/Database Class methods) uses with sharing keywords.	In your Apex	Data Security \| Sharing and Visibility
Use cases for data encryption in transit and (if needed) at rest are clear and discoverable.	In your design standards	Data Security \| Use of Encryption

Compliant Patterns

This table shows you a few examples of what good looks like when designing a solution that follows legal and ethical guidelines. It also shows you the location where you can look for the presence (or absence) of the pattern, and how this pattern maps to the dimensions, linked first, and considerations, linked second, in the Well-Architected white papers where you can learn more.

Patterns: What Does a Good Pattern Look Like?	Location: Where to Look?	Resources: Learn More About Dimensions \| Considerations
You have an up-to-date data dictionary containing field level names, descriptions, and classifications.	In your documentation	Legal Adherence \| Data Privacy
You have an org strategy that outlines where data will be stored and maintained to comply with all applicable data residency requirements.	In your documentation	Legal Adherence \| Localization
Test steps include using multiple types of input devices to enter data.	In your test plans	Accessibility \| Data Entry
The types of visual cues approved to convey meaning or state are clearly listed, and color is not a primary cue.	In your design standards	Accessibility \| Navigation
Standards include clear guidance for areas impacted by company policies.	In your design standards	Ethical Standards \| Company Policies
Standards for when and how to use disclaimers for generative AI are clearly defined.	In your design standards	Ethical Standards \| Artificial Intelligence

Reliable Patterns

This table shows you a few examples of what good looks like when designing a solution that operates efficiently and dependably. It also shows you the location where you can look for the presence (or absence) of the pattern, and how this pattern maps to the dimensions, linked first, and considerations, linked second, in the Well-Architected white papers where you can learn more.

Patterns: What Does a Good Pattern Look Like?	Location: Where to Look?	Resources: Learn More About Dimensions \| Considerations
Risk mitigation and response plans are prioritized, focusing on highest priority risks first.	In your documentation	Availability \| Risk Management
Mitigation controls are put in place immediately, mature over time, and incorporate automation as early as possible.	In your org	Availability \| Failure Mitigation
DML or database methods always operate against collections in Apex.	In your org	Performance \| Throughput
Filters do not contain formula fields.	In your org	Performance \| Latency
Tables have been denormalized for scale.	In your data model	Scalability \| Data Modeling
No users are assigned to more than 10,000 records of the same object type.	In your data	Scalability \| Data Volume

In the next unit, you learn about what it means to design an easy solution.

需要帮助？

了解更多