A citizen services app requests limited delegated access to a user's calendar-like scheduling resource using standard authorization flows without collecting the user's cloud password. Which protocol best fits this delegated authorization scenario?
Select an answer to reveal the explanation.
Short Explanation
The app should never pocket the citizen's password—it should ask for a limited hall pass to the calendar and nothing more. OAuth 2.0 is that consent-and-token dance: scoped access without handing over the master key. Telnet, anonymous FTP, and SNMP strings are not how modern delegated auth works.
Full Explanation
OAuth 2.0 provides delegated authorization: a client receives scoped access tokens after user consent without collecting or storing the resource owner's password. That model fits citizen apps that need limited access to calendar-like or profile resources. Cleartext Telnet, anonymous FTP, and SNMP community strings are inappropriate substitutes and do not implement scoped consent. Cloud+ IAM objectives distinguish OAuth-style authorization from authentication-only mechanisms.