Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam Heroku-Architect Topic 8 Question 31 Discussion

Actual exam question for Salesforce's Salesforce Certified Heroku Architect exam
Question #: 31
Topic #: 8
[All Salesforce Certified Heroku Architect Questions]

Which technology do Salesforce REST APIs use for authentication?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Marvel
3 months ago
I feel more confident now after discussing it. B) OAuth seems to be the correct answer.
upvoted 0 times
...
Veronica
3 months ago
Got it, thanks for the explanation. I think I'll go with B) OAuth as well.
upvoted 0 times
...
Lonny
3 months ago
OAuth allows for tokens to be issued instead of sharing actual usernames and passwords, making it more secure.
upvoted 0 times
...
Edgar
3 months ago
I'm not sure about this one. Can someone explain why OAuth is used for authentication?
upvoted 0 times
...
In
3 months ago
Yes, I agree. OAuth is the standard way for authentication with Salesforce REST APIs.
upvoted 0 times
...
Nicholle
3 months ago
Let's be real, if you're not using OAuth for your Salesforce REST APIs, you're living in the past. It's like using a typewriter in the age of laptops.
upvoted 0 times
Miriam
2 months ago
C) SAML
upvoted 0 times
...
Terrilyn
2 months ago
B) OAuth
upvoted 0 times
...
Lea
2 months ago
A) Basic usernames and passwords
upvoted 0 times
...
...
Reena
3 months ago
I think the answer is B) OAuth because it provides a more secure way of authentication.
upvoted 0 times
...
Tashia
3 months ago
I feel more confident now after discussing it. B) OAuth seems to be the correct answer.
upvoted 0 times
...
Ellen
3 months ago
Got it, thanks for the explanation. I think I'll go with B) OAuth as well.
upvoted 0 times
...
Edward
3 months ago
Ooh, OAuth! It's like having a secret handshake for your API access. Much cooler than just typing in a password.
upvoted 0 times
...
Emmett
3 months ago
Pre-shared keys? What is this, the Dark Ages? OAuth is the future, and the future is now!
upvoted 0 times
Tula
2 months ago
Pre-shared keys are outdated, OAuth is much more secure and modern.
upvoted 0 times
...
Yuette
3 months ago
OAuth is definitely the way to go for authentication with Salesforce REST APIs.
upvoted 0 times
...
...
Kiley
3 months ago
SAML? Really? That's so 2000s. OAuth is where it's at, my friend.
upvoted 0 times
Brandon
3 months ago
Yeah, SAML is outdated. OAuth provides a more secure authentication method.
upvoted 0 times
...
Zack
3 months ago
OAuth is definitely the way to go for Salesforce REST APIs.
upvoted 0 times
...
...
Ben
4 months ago
OAuth allows for tokens to be issued instead of sharing actual usernames and passwords, making it more secure.
upvoted 0 times
...
Vivan
4 months ago
I'm not sure about this one. Can someone explain why OAuth is used for authentication?
upvoted 0 times
...
Daniel
4 months ago
Yes, I agree. OAuth is the standard way for authentication with Salesforce REST APIs.
upvoted 0 times
...
Arletta
4 months ago
OAuth is the way to go for Salesforce REST APIs. I mean, who wants to deal with basic usernames and passwords these days?
upvoted 0 times
Romana
2 months ago
C) SAML
upvoted 0 times
...
Anglea
2 months ago
OAuth is the standard for authentication these days.
upvoted 0 times
...
Sharee
2 months ago
B) OAuth
upvoted 0 times
...
Vesta
2 months ago
I agree, OAuth is definitely the better option.
upvoted 0 times
...
Jarvis
2 months ago
A) Basic usernames and passwords
upvoted 0 times
...
Miriam
2 months ago
Definitely! OAuth is much more secure and convenient.
upvoted 0 times
...
Karan
3 months ago
B) OAuth
upvoted 0 times
...
...
Jaclyn
4 months ago
I think the answer is B) OAuth because it provides a more secure way of authentication.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77