Discuss Blockchain CBDE Exam Topic 5 Question 88

Integrating the community into your testing:

Ais great, because they often find bugs which weren't considered before.

Bis not good, because you might give out secrets.

Suggested Answer: A

Get Premium CBDE Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

23 comments · newest first

Bonita 11 months ago

Wait, are we really trusting random users with our code?

Vincent 11 months ago

I don't think it's worth the risk of leaking info.

Aleshia 11 months ago

I've seen communities find bugs that devs missed!

Aron 12 months ago

But what about security risks?

Elsa 12 months ago

Totally agree, community feedback is invaluable!

Cassi 12 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.

Tiera 1 year 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.

Ellsworth 1 year 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.

Nenita 1 year ago

I remember discussing how community feedback can uncover issues we might overlook, so I think option A makes sense.

Cathrine 1 year 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.

Freeman 1 year 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.

Maira 1 year 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.

Yuonne 1 year 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.

Alease 1 year 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.

Chandra 1 year ago

I think the right answer might be A, because it allows prefixes from /1 up to /16. I hope that's correct.

Torie 1 year 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.

Melissa 1 year 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.

Trina 2 years ago

I agree with option A. Community testing identifies unique issues we haven’t considered.

Chaya 2 years ago

Yeah, but we could also just use NDAs to protect sensitive info. Still think A is better.

Willard 2 years ago

Good point, but community feedback can be invaluable. Helps improve the product.

Rebecka 2 years ago

Hmm, but what about option B? It’s risky. We might expose secrets.

Francis 2 years ago

I think it’s great! They often find bugs we might miss. Option A.

Graciela 2 years ago

What do you think about integrating the community into testing?

Blockchain CBDE Exam - Topic 5 Question 88 Discussion