Answer-first summary for fast verification
Answer: Use secure LDAP to authenticate the legacy application and ask users to sign in through Gmail.
Modifying a legacy application to use SAML or OAuth 2.0 can be challenging, time-consuming, and expensive, which contradicts the company's goal of minimizing developer effort and cost. Synchronizing LDAP server data with Google Cloud Directory Sync doesn't address the LDAP protocol authentication directly unless the application is modified, which again increases effort and cost. Secure LDAP is the right answer because it allows the legacy application to authenticate using the same Cloud Identity credentials users have for G Suite and other SaaS apps, without requiring significant changes to the application. This approach is cost-effective and minimizes developer effort. Reference: [Google Cloud Blog](https://cloud.google.com/blog/products/identity-security/cloud-identity-now-provides-access-to-traditional-apps-with-secure-ldap).
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
Your company is planning to migrate a legacy application that uses the LDAP protocol for authentication to the cloud. The goal is to find a cost-effective solution with minimal developer effort. What is the best approach?
A
Modify the legacy application to use SAML and ask users to sign in through Gmail.
B
Modify the legacy application to use OAuth 2.0 and ask users to sign in through Gmail.
C
Use secure LDAP to authenticate the legacy application and ask users to sign in through Gmail.
D
Synchronize data within your LDAP server with Google Cloud Directory Sync.