Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft Exam AZ-400 Topic 4 Question 118 Discussion

Actual exam question for Microsoft's AZ-400 exam
Question #: 118
Topic #: 4
[All AZ-400 Questions]

You have a GitHub repository that uses GitHub Actions and stores access keys by using GitHub encrypted secrets.

You plan to update the secrets by using the GitHub REST API.

You need to wrap the secrets before adding them to a REST-based call.

Which encryption library should you are that you use?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Billy
7 days ago
Haha, BouncyCastle? Sounds like something straight out of a spy movie!
upvoted 0 times
...
Claudia
9 days ago
CryptoNet? Never heard of it. I'd stick with a more established library like libsodium.
upvoted 0 times
...
Leonardo
20 days ago
I personally prefer CryptoNet for encryption, it has worked well for me in the past.
upvoted 0 times
...
Denny
22 days ago
I'm not sure about libsodium, I think hashlib might be a better option.
upvoted 0 times
...
Junita
23 days ago
I agree with Lura, libsodium is a good choice for encryption.
upvoted 0 times
...
Lavera
24 days ago
Hmm, hashlib is for hashing, not encryption. Definitely not the right choice.
upvoted 0 times
...
Luis
28 days ago
BouncyCastle is a good option too, but it might be overkill for this simple use case.
upvoted 0 times
Charlette
12 days ago
A) CryptoNet
upvoted 0 times
...
Fletcher
14 days ago
A) CryptoNet
upvoted 0 times
...
...
Herminia
1 months ago
I think libsodium is the way to go here. It's a well-known and secure library for handling encryption tasks.
upvoted 0 times
...
Lura
1 months ago
I think we should use libsodium for encryption.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77