Salesforce Exam Integration Architect Topic 1 Question 45 Discussion

Actual exam question for Salesforce's Integration Architect exam

Question #: 45
Topic #: 1

A company's security assessment noted vulnerabilities on the un managed packages in their Salesforce orgs, notably secrets that are easily accessible and in plain text, such as usernames, passwords, and OAuth tokens used in callouts from Salesforce.

Which two persistence mechanisms should an integration architect require to be used to ensure that secrets are protected from deliberate or inadvertent exposure?

Choose 2 answers

AEncrypted Custom Fields

BNamed Credentials

CProtected Custom Metadata Types

DProtected Custom Settings

Show Suggested Answer

Suggested Answer: B, D, E

by Milly at Sep 12, 2024, 09:14 AM

Limited Time Offer

25%

Off

Get Premium Integration Architect Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Kristofer

1 months ago

I'm going with Named Credentials and Protected Custom Settings. Keeps those secrets nice and hidden, you know?

upvoted 0 times

Adelina

6 days ago

User2: Agreed, those options will help keep our secrets safe.

upvoted 0 times

...

Robt

19 days ago

User1: Named Credentials and Protected Custom Settings are definitely the way to go.

upvoted 0 times

...

Edgar

1 months ago

Ha! I can just see the security team frantically trying to figure out which Protected Custom Settings to use. Gotta love these exam questions.

upvoted 0 times

...

Melissa

1 months ago

Protected Custom Metadata Types? Sounds like a fancy way to say 'security through obscurity'. I'll pass on that one.

upvoted 0 times

Benedict

11 days ago

User1: Yeah, I agree. It's better to use multiple mechanisms to ensure security.

upvoted 0 times

...

Cordelia

12 days ago

User2: Encrypted Custom Fields are also important for securing sensitive information.

upvoted 0 times

...

Felix

20 days ago

User1: I think Named Credentials is a good option for protecting secrets.

upvoted 0 times

...

Terrilyn

1 months ago

Named Credentials are a great choice for protecting sensitive information. Definitely one of the two I'd pick.

upvoted 0 times

Nickolas

7 days ago

A: Yeah, using both Named Credentials and Encrypted Custom Fields would provide strong protection for our secrets.

upvoted 0 times

...

Laquita

25 days ago

B: Encrypted Custom Fields would also be a good choice to protect secrets.

upvoted 0 times

...

Renea

1 months ago

A: I agree, Named Credentials are a secure way to store sensitive information.

upvoted 0 times

...

Kallie

2 months ago

Encrypted Custom Fields? That's like putting a Band-Aid on a bullet wound. Clearly, we need something more robust to secure those secrets.

upvoted 0 times

Roselle

15 days ago

C: Protected Custom Metadata Types can also be used to protect secrets from exposure.

upvoted 0 times

...

Gearldine

19 days ago

A: Yes, Named Credentials provide a more secure way to store and use secrets for callouts.

upvoted 0 times

...

William

2 months ago

B: Named Credentials would be a better option to protect secrets in Salesforce orgs.

upvoted 0 times

...

Argelia

2 months ago

A: I agree, Encrypted Custom Fields are not enough to secure sensitive information.

upvoted 0 times

...

Hester

2 months ago

I believe Encrypted Custom Fields should also be used to protect sensitive data.

upvoted 0 times

...

Raina

2 months ago

I agree with Lawana, Named Credentials are a secure way to store secrets.

upvoted 0 times

...

Lawana

2 months ago

I think Named Credentials should be used for sure.

upvoted 0 times

...