Salesforce Certified Identity and Access Management Questions with 100% Correct Answers | Verified

Salesforce Certified Identity and Access Management Types of Authentication Flow - ✔✔ - Web Server - User Agent - JWT Bearer Token - Device Authentication Flow - Asset Token Flow - SAML Bearer Assertion Flow - SAML Assertion Flow - Username and Password Web Server Flows - ✔✔ - are for apps hosted on a secure server - must be used when the server must protect the secret - uses the "Authorisation Code" grant type, which is optimised for confidential clients and may request both access and refresh tokens User Agent Flows - ✔✔ - users can authorise desktop or mobile apps to access data using an external or embedded browser - uses a scripting language, such as Javascript - uses the "Implicit" grant type, which gets only access tokens and is optimised for pub lic clients JWT Bearer Token Flows - ✔✔ - selected for server -server API integration - uses a certificate to sign the JWT request - doesn't require any specific user interaction - JWT = the format of the request Device Authentication Flows - ✔✔ - Can be used for command -line applications - Can be used for applications with limited input and display capabilities, such as appliances, TVs and IoT - Users connect these to Salesforce using a browser on desktop or smartphone (THINK Philips Hue, Sonos, app -controlled washing machines, Amazon Echo Dot) What are the benefits of combining the issuing and registration of asset tokens within an Asset Token Flow? - ✔✔ - Efficient token exchange - Enables the automatic linking of devices to Salesforce Service Cloud asset data Asset Token Flows - ✔✔ are used to request an asset token from Salesforce for connected devices What happens in an asset token flow? - ✔✔ An OAuth access token and an actor t oken are exchanged for an asset token What is the difference between a SAML Bearer & Assertion Flow and a SAML Assertion Flow? - ✔✔ While both flows make use of SAML assertions that contain signed certificates, SAML Assertion Flows are used when organisati ons ALREADY use SAML to access Salesforce and they want to use the Web Services API in the same way. SAML Bearer and Assertion Flow - ✔✔ - Enables applications to reuse an existing authorisation by supplying a signed SAML assertion - The app is authorised by assigning a digital signature to the SAML assertion SAML Assertion Flow - ✔✔ - An alternative flow for orgs who are already accessing Salesforce via SAML - used when the customer wants to access the web services API in the same way, i.e. using signed assertions Access Tokens - ✔✔ - Are a type of OAuth token, known as the Session ID - Are used to make authenticated requests FOR the user - Have a longer lifetime than authorisation codes - Must be protected from interception (via Transport Layer Securi ty: TLS) Authorisation Codes - ✔✔ - Are a type of OAuth token that authorise access for a very short amount of time - Are generated by Salesforce and passed to the client app via the browser - Are passed from the client App to the Authorisation Server in exchange for an access / refresh token Refresh Tokens - ✔✔ - Can have an indefinite lifetime - Can be stored within a client app - Can be used repeatedly to gain access, like a password