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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Blockchain CBDE Exam - Topic 5 Question 88 Discussion

Integrating the community into your testing:
A) is great, because they often find bugs which weren't considered before.
B) is not good, because you might give out secrets.

Blockchain CBDE Exam - Topic 5 Question 88 Discussion

Actual exam question for Blockchain's CBDE exam
Question #: 88
Topic #: 5
[All CBDE Questions]

Integrating the community into your testing:

Show Suggested Answer Hide Answer
Suggested Answer: A

by Eden at May 10, 2024, 02:29 AM

Limited Time Offer

25%

Off

Get Premium CBDE Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Bonita
9 months ago
Wait, are we really trusting random users with our code?
upvoted 0 times
...
Vincent
10 months ago
I don't think it's worth the risk of leaking info.
upvoted 0 times
...
Aleshia
10 months ago
I've seen communities find bugs that devs missed!
upvoted 0 times
...
Aron
10 months ago
But what about security risks?
upvoted 0 times
...
Elsa
10 months ago
Totally agree, community feedback is invaluable!
upvoted 0 times
...
Cassi
10 months ago
I see both sides, but I recall a case study where community testing led to major security leaks, which makes me hesitant about A.
upvoted 0 times
...
Tiera
11 months ago
I practiced a question similar to this, and I think integrating the community is beneficial, especially for finding unexpected bugs. So, A seems right.
upvoted 0 times
...
Ellsworth
11 months ago
I'm not entirely sure about involving the community; I feel like there could be risks with sharing sensitive information, which makes me lean towards B.
upvoted 0 times
...
Nenita
11 months ago
I remember discussing how community feedback can uncover issues we might overlook, so I think option A makes sense.
upvoted 0 times
...
Cathrine
11 months ago
I got this one! Involving the community is super valuable for finding bugs. You just need to be selective about what you share to avoid leaking sensitive info. Piece of cake.
upvoted 0 times
...
Freeman
11 months ago
Integrating the community into testing is a great idea! They often catch things the dev team misses. As long as you're careful about what information you share, the benefits outweigh the risks.
upvoted 0 times
...
Maira
11 months ago
Hmm, I'm a bit unsure about this one. I know involving the community can find more bugs, but I'm worried about the security implications. I'll have to think this through.
upvoted 0 times
...
Yuonne
11 months ago
This seems like a straightforward question about the benefits and risks of involving the community in software testing. I'll need to weigh the pros and cons carefully.
upvoted 0 times
...
Alease
11 months ago
Hmm, I'm a bit confused on the best approach here. I'm not sure if packaging each library separately or combining the functions would really help reduce the size as much as the Lambda layer option. I'll have to think this through carefully.
upvoted 0 times
...
Chandra
11 months ago
I think the right answer might be A, because it allows prefixes from /1 up to /16. I hope that's correct.
upvoted 0 times
...
Torie
11 months ago
I'm a bit confused by this question. I'm not entirely sure what "quality assurance" means in the context of a project board. I'll have to review my notes to see if I can figure this out.
upvoted 0 times
...
Melissa
11 months ago
I think option C sounds like something we practiced. It talks about automated scaling listeners, which could help with routing requests, but I'm a bit confused about how it interacts with the on-premise setup.
upvoted 0 times
...
Trina
2 years ago
I agree with option A. Community testing identifies unique issues we haven’t considered.
upvoted 0 times
...
Chaya
2 years ago
Yeah, but we could also just use NDAs to protect sensitive info. Still think A is better.
upvoted 0 times
...
Willard
2 years ago
Good point, but community feedback can be invaluable. Helps improve the product.
upvoted 0 times
...
Rebecka
2 years ago
Hmm, but what about option B? It’s risky. We might expose secrets.
upvoted 0 times
...
Francis
2 years ago
I think it’s great! They often find bugs we might miss. Option A.
upvoted 0 times
...
Graciela
2 years ago
What do you think about integrating the community into testing?
upvoted 0 times
...

Save Cancel