Which way should be used to safely the API keys?
Suggested Answer: B
Get Premium 200-901 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
API keys should be stored securely to prevent unauthorized access. The best practice is to store them encrypted in a configuration file that is separate from the code. This approach ensures that sensitive information is not hardcoded in the source code, which could be exposed through version control or other means. Keeping API keys in encrypted configuration files also allows for better management and updating of keys without changing the application code.
26 comments · newest first
MI
Miles
6 months ago
D is a big no. Plain text is just asking for trouble.
CH
Chaya
6 months ago
C is risky. If someone sees the code, they get the keys.
SA
Samira
6 months ago
A is good too, but what if the environment gets compromised?
DY
Dyan
6 months ago
I think B is the best option. Keeps it secure.
SY
Sylvia
6 months ago
I disagree with A, it’s not as secure as B.
LE
Lenna
6 months ago
Wait, people still use D? That's wild!
TO
Torie
7 months ago
C? Really? That sounds risky.
PA
Paulina
7 months ago
A is good too, but B is safer.
ME
Mee
7 months ago
B is definitely the best option!
AN
Anna
7 months ago
I'm with the crowd on this one. Option B is the way to go. Gotta keep those API keys locked down tight!
JE
Jesusa
7 months ago
Option C might work, but it's still not as secure as keeping the keys in an encrypted config file. Better safe than sorry!
LA
Lashon
8 months ago
Haha, Option D? Putting API keys in plain text? That's like leaving your house keys under the doormat.
LU
Lucy
8 months ago
I agree, Option B is the safest choice. Keeping sensitive data out of the code is a best practice.
AI
Aide
8 months ago
Option B is the way to go. Encrypting the API keys in a separate config file is the most secure approach.
MA
Maurine
8 months ago
I vaguely recall a practice question where we had to choose between environment variables and encrypted files, but I can't remember which was preferred.
TA
Tayna
9 months ago
I feel like encrypting in a separate config file is safer than putting it in the code itself, so B might be the right choice.
EL
Elmer
9 months ago
I think using environment variables is a good practice, but I’m not sure if it’s the best option compared to encryption.
SH
Shad
9 months ago
I remember we discussed that storing API keys in plain text is a huge security risk, so D is definitely out.
LE
Leandro
9 months ago
Option B seems like the safest bet to me. Keeping the API keys separate from the code and encrypting them is a standard security practice. I feel pretty confident that this is the right way to go.
MI
Mindy
9 months ago
I'm a bit confused by this question. Storing API keys securely is an important issue, but I'm not sure which of these options is the best. I'll need to do some research on best practices for API key management.
CA
Cathrine
10 months ago
D is definitely not the right answer. Storing API keys in plain text is a huge security risk. I'm leaning towards B or C, but I'll need to review the details of each approach.
KR
Kristin
10 months ago
Hmm, I'm not sure about this one. I'd need to think more about the tradeoffs between the different options. Encrypting in the code could work, but a separate config file might be better.
CO
Colton
10 months ago
I think option B is the best approach here. Encrypting the API keys in a separate configuration file seems like the most secure way to handle sensitive information.
CA
Candida
4 months ago
Option A could work too, but B feels more secure.
DA
Daniel
4 months ago
Yeah, keeping it separate from the code is smart.
LA
Lajuana
5 months ago
I agree, option B is definitely the safest choice.