Answer-first summary for fast verification
Answer: Keep the API credentials in AWS Secrets Manager and use the credentials to make the API call by fetching the API credentials at runtime by using the AWS SDK
Keep the API credentials in AWS Secrets Manager and use the credentials to make the API call by fetching the API credentials at runtime by using the AWS SDK Secrets Manager enables you to replace hardcoded credentials in your code, including passwords, with an API call to Secrets Manager to retrieve the secret programmatically. This helps ensure the secret can't be compromised by someone examining your code, because the secret no longer exists in the code. Also, you can configure Secrets Manager to automatically rotate the secret for you according to a specified schedule. This enables you to replace long-term secrets with short-term ones, significantly reducing the risk of compromise.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
Question 18 Correct A company plans to transmit data to a third party using an HTTP API endpoint that is controlled by the third party. The company possesses the required API key to access the endpoint. It is crucial that integrating the API key into the company's application code does not degrade the application’s performance.
What is the most secure method to achieve this?
A
Keep the API credentials in AWS Secrets Manager and use the credentials to make the API call by fetching the API credentials at runtime by using the AWS SDK
B
Keep the API credentials in an encrypted table in MySQL RDS and use the credentials to make the API call by fetching the API credentials from RDS at runtime by using the AWS SDK
C
Keep the API credentials in an encrypted file in S3 and use the credentials to make the API call by fetching the API credentials from S3 at runtime by using the AWS SDK
D
Keep the API credentials in a local code variable and use the local code variable at runtime to make the API call