Discuss Salesforce Salesforce Certified MuleSoft Developer II (Mule-Dev-301) Exam Topic 1 Question 22

Refer to the exhibit.

What is the result if ''Insecure'' selected as part of the HTTP Listener configuration?

AThe HTTP Listener will trust any certificate presented by the HTTP client

BThe HTTP Lister will accept any unauthenticated request

CThe HTTP listener will only accept HTTP requests

DMutual TLS authentication will be enabled between this HTTP Listener and an HTTP client

Suggested Answer: A

To communicate asynchronously between two APIs deployed to a two-node on-prem cluster, the developer can use the VM Connector if the two APIs use the same domain. The VM Connector allows passing messages between different Mule applications within a single Mule runtime instance or across different instances using shared memory or persistent storage. If two APIs are deployed under the same domain, they can share resources such as VM queues and communicate asynchronously using VM Connector operations. Reference: https://docs.mulesoft.com/mule-runtime/4.3/vm-connector https://docs.mulesoft.com/mule-runtime/4.3/shared-resources

Get Premium Salesforce Certified MuleSoft Developer II (Mule-Dev-301) Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

34 comments · newest first

Glory 11 months ago

Wait, really? That seems too insecure!

Kristin 11 months ago

B is correct, right? No authentication needed!

Carli 12 months ago

I thought it would only accept HTTP requests?

Talia 12 months ago

Totally agree, that's a security risk!

Candra 1 year ago

A means it trusts any client cert.

Vicky 1 year ago

I don't think it would enable mutual TLS, so D seems unlikely. I might lean towards B, but I need to double-check my notes.

Beth 1 year ago

I feel like "Insecure" might just mean it accepts HTTP requests only, so C could be the answer. But I could be mixing it up with something else.

Claudia 1 year ago

I remember a practice question where "Insecure" allowed any request, which sounds like B. That could be the right choice here.

Ira 1 year ago

I think "Insecure" means the listener won't validate certificates, so maybe A is correct? But I'm not entirely sure.

Dottie 1 year ago

I'm pretty confident the answer is B. The "Insecure" setting means the HTTP Listener will accept any unauthenticated request, without verifying certificates or requiring authentication.

Moon 1 year ago

I'm a bit confused by this question. I know "Insecure" means there won't be any security measures, but I'm not sure if that means it will accept any unauthenticated request or just HTTP requests. I'll have to review the material on this.

Valentine 1 year ago

Okay, let me think this through. If "Insecure" is selected, that means the HTTP Listener won't be doing any kind of authentication or verification, so option B seems like the right answer.

Myra 1 year ago

Hmm, I'm not sure about this one. I need to double-check the details on what the "Insecure" setting actually does.

Glenn 1 year ago

I think the answer is B. The "Insecure" setting means the HTTP Listener will accept any unauthenticated request.

Jin 2 years ago

Insecure? Wow, that's about as subtle as a sledgehammer to the face. I guess the developers were feeling a little too 'creative' with their naming conventions.

Karl 1 year ago

↳ replying to Jin

User1: Definitely, it's not the most reassuring option.

Annelle 1 year ago

↳ replying to Jin

User2: I agree, they could have come up with a better name.

France 1 year ago

↳ replying to Jin

User3: I wonder why they would even have that option in the first place.

Jaime 1 year ago

↳ replying to Jin

User2: I know, right? It's like they're just asking for trouble.

Gerald 1 year ago

↳ replying to Jin

User1: Yeah, 'Insecure' does sound pretty blunt.

Na 1 year ago

↳ replying to Jin

User1: Yeah, 'Insecure' doesn't exactly inspire confidence.

Rex 2 years ago

Insecure? More like 'I'm-gonna-get-hacked-so-hard' mode. Hard pass on that one, my friend. I'll stick with the secure options, if you don't mind.

Filiberto 2 years ago

The 'Insecure' option? Sounds like a recipe for disaster. I'd rather not have my data exposed to the whole internet, thank you very much.

Erick 1 year ago

↳ replying to Filiberto

User1: Absolutely, we should never compromise on data security.

Naomi 1 year ago

↳ replying to Filiberto

User3: I think it's important to always consider the potential risks involved.

Melodie 2 years ago

↳ replying to Filiberto

User2: Definitely, it's better to prioritize security over convenience.

Adelina 2 years ago

↳ replying to Filiberto

User1: I agree, choosing 'Insecure' doesn't sound safe at all.

Alishia 2 years ago

Oh, so 'Insecure' means I can just waltz in without any authentication? Sweet, sign me up! Wait, what do you mean that's not a good thing?

Devora 1 year ago

↳ replying to Alishia

User 2: 'Insecure' option means any unauthenticated request will be accepted.

Adelle 2 years ago

↳ replying to Alishia

User 1: 'Insecure' means no authentication required.

Shawana 2 years ago

Whoa, 'Insecure' option? Guess the developers wanted to keep things exciting, huh? Definitely not the way to go if you value your data's safety.

Lanie 2 years ago

I'm not sure, but I think selecting 'Insecure' means the HTTP Listener will trust any certificate presented by the HTTP client.

Darrin 2 years ago

I agree with Elena, selecting 'Insecure' would enable mutual TLS authentication.

Elena 2 years ago

I think the result would be D) Mutual TLS authentication will be enabled between this HTTP Listener and an HTTP client.

Salesforce Certified MuleSoft Developer II (Mule-Dev-301) Exam - Topic 1 Question 22 Discussion