Security-and-Privacy-Accredited-Professional Practice Exam Questions with Answers Salesforce Security & Privacy Accredited Professional Exam Certification

Align your org's security setting with Salesforce-recommended security standards

Identify and fix vulnerabilities in your security settings

Organize user access logs

Access event log files to track user activity and feature adoption and troubleshoot issues

Verify that multiple Salesforce applications have the same level of security

User interface logins

API logins

Delegated authentication logins

Automated test account logins

Federated SSO logins

In near real-time

Hourly and once every 24 hours

Every 5 minutes

Every 30 minutes

Some types of penetration testing are permitted, but not in production

No, this is not permitted under any circumstances

Penetration testing is allowed, but the Salesforce Agreement needs to be signed before testing can comment

Penetration testing can be carried out at anytime by anyone

Once every month per objectOnce every 24 hours per object

Once every hour per object

Once every week per object

Via Field Level Security settings, a Salesforce user has view access to a field that is encrypted via

Platform Encryption.

1.5 TB

5TB

1TB

3TB

SOAP API

Metadata API

REST API

Portability API

Data Residency

Fallover

IP restrictions

Scalability

Password expiration

Password complexity

Password length

Password with special characters

Disallowed passwords

Permissions

Event Monitoring

Authentication

Configuration

Enable MFA for all users who log in through a Salesforce product's user interface

Enable MFA for all admins who log in through a Salesforce product's user interface

Enable MFA for your single sign-on identity provider and ensure all Salesforce users log in via SSO

Enable delegated authentication for all products built on the Salesforce Platform

Setup/Manage Tenants

Setup/Security Center

Manage Security Tab

Connected Tenants Tab

The field label followed by a message indicating that the field value is encrypted

The field label followed by the unencrypted field value

The field label followed by eight asterisks

The field label followed by 256 characters of cipher text

Data encryption is used for masking data in a production environment

Data encryption is an add on feature to the Data Mask product

Data Mask prevents malicious attackers from accessing or interacting with sensitive data at rest in the data center.

Data masking prevents developers or other users from viewing sensitive data in the user interface or exporting it as plain text

Remote Site Settings

Settings

Setup

Home

Classic Encryption encrypts standard fields

Platform Encryption encrypts custom fields only. Classic Encryption encrypts standard fields

Platform Encryption is built on Classic Encryption

Classic Encryption masks characters whereas Platform Encryption does not

Heroku

Custom Connectors

S3 Connector

AWS Private Connect

Freeze User, End Session, require 2FA

Obfuscate, Encrypt, de-identify

Launch Workflow, Require Approval, Send SMS Text

Block, Multi-Factor Authentication, and Notifications

View the Configuration Metrics detail page.

View the detail page of the 'View All Data' metric, and check the Context column on the change for the user.

See the Permissions dashboard.

View the detail page of the 'Modify All Data' metric, and check the Context column on the change for the user.

Lead

Authorization Form Consent

Case

Contact

Opportunity

Entering codes from text messages is error-prone

Mobile devices can be lost or broken

Email account credentials can be compromised

SIM cards can be hacked

Archive data after 12 months, store it for 5 years

Archive data after 6 months, store it for 18 months

Archive data after 18 months, store it for 10 years

Archive data after 24 months, store it for 7 years

Curiosity

Surprise

Fear

Rewards

AES-256

AES-192

3DES

RSA-4096

Anonymize Case Comments

Update Contacts

Query All Entries

Delete All Emails

Purchase additional storage capacity to unlock additional field history tracking.

Purchase the Field Audit Trail add-on feature.

Purchase additional field history tracking capacity in blocks of 20 fields.

Enable and save field history tracking settings on the 21st field to automatically add additional field history tracking capacity to the org.