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

Salesforce Exam MuleSoft-Platform-Architect-I Topic 1 Question 12 Discussion

Actual exam question for Salesforce's Salesforce Certified MuleSoft Platform Architect I exam
Question #: 12
Topic #: 1
[All Salesforce Certified MuleSoft Platform Architect I Questions]

A company requires Mule applications deployed to CloudHub to be isolated between non-production and production environments. This is so Mule applications deployed to non-production environments can only access backend systems running in their customer-hosted non-production environment, and so Mule applications deployed to production environments can only access backend systems running in their customer-hosted production environment. How does MuleSoft recommend modifying Mule applications, configuring environments, or changing infrastructure to support this type of per-environment isolation between Mule applications and backend systems?

Show Suggested Answer Hide Answer
Suggested Answer: D

Correct Answer :Create separate Anypoint VPCs for non-production and production environments, then configure connections to the backend systems in the corresponding customer-hosted environments.

*****************************************

>>Creating different Business Groups does NOT make any difference w.r.t accessing the non-prod and prod customer-hosted environments. Still they will be accessing from both Business Groups unless process network restrictions are put in place.

>>We need to modify or couple the Mule Application Implementations with the environment. In fact, we should never implements application coupled with environments by binding them in the properties. Only basic things like endpoint URL etc should be bundled in properties but not environment level access restrictions.

>>IP addresses on CloudHub are dynamic until unless a special static addresses are assigned. So it is not possible to setup firewall rules in customer-hosted infrastrcture. More over, even if static IP addresses are assigned, there could be 100s of applications running on cloudhub and setting up rules for all of them would be a hectic task, non-maintainable and definitely got a good practice.

>>Thebest practice recommendedby Mulesoft (In fact any cloud provider), is to have your Anypoint VPCs seperated for Prod and Non-Prod and perform the VPC peering or VPN tunneling for these Anypoint VPCs to respective Prod and Non-Prod customer-hosted environment networks.


Bottom of Form

Top of Form

Contribute your Thoughts:

Ashley
7 days ago
I'm not sure, but creating separate Anypoint VPCs for each environment also sounds like a good solution.
upvoted 0 times
...
Matt
11 days ago
I agree with Dana, configuring firewall rules seems like the most secure option.
upvoted 0 times
...
Dana
13 days ago
I think option B makes sense, it's important to control access based on IP addresses.
upvoted 0 times
...
Roxane
16 days ago
That's a good point, Julie. Both options B and D could be valid solutions depending on the specific requirements.
upvoted 0 times
...
Julie
18 days ago
I'm not sure, I think creating separate Anypoint VPCs as in option D could also work well for isolation.
upvoted 0 times
...
Jacklyn
20 days ago
Ah, the joys of infrastructure management. I bet the Mule developers are having fun with this one!
upvoted 0 times
Cherrie
12 days ago
A) Modify properties of Mule applications deployed to the production Anypoint Platform environments to prevent access from non-production Mule applications
upvoted 0 times
...
...
Kandis
24 days ago
I agree with Roxane, option B seems like the most secure way to ensure isolation between environments.
upvoted 0 times
...
Kristal
26 days ago
Option C is interesting, but I'm not sure if that provides the level of isolation required. Separate VPCs is the way to go.
upvoted 0 times
...
Timothy
27 days ago
Haha, I'm just wondering how many firewalls these companies have to configure. Option B sounds like a nightmare!
upvoted 0 times
...
Roxane
29 days ago
I think option B makes sense, it's important to control access based on IP addresses.
upvoted 0 times
...
Buddy
1 months ago
I agree with Catrice. Creating separate VPCs is the recommended approach to isolate environments.
upvoted 0 times
Cornell
3 days ago
B) Configure firewall rules in the infrastructure inside each customer-hosted environment so that only IP addresses from the corresponding Anypoint Platform environments are allowed to communicate with corresponding backend systems
upvoted 0 times
...
Peggy
4 days ago
I agree, creating separate VPCs is the recommended approach to isolate environments.
upvoted 0 times
...
Emmett
5 days ago
D) Create separate Anypoint VPCs for non-production and production environments, then configure connections to the backend systems in the corresponding customer-hosted environments
upvoted 0 times
...
Ramonita
20 days ago
B) Configure firewall rules in the infrastructure inside each customer-hosted environment so that only IP addresses from the corresponding Anypoint Platform environments are allowed to communicate with corresponding backend systems
upvoted 0 times
...
...
Catrice
1 months ago
Option D makes the most sense. Separate VPCs and connections to backend systems in the corresponding environments is the way to go.
upvoted 0 times
Noel
7 days ago
It's important to have that level of isolation between non-production and production environments.
upvoted 0 times
...
Lauran
11 days ago
That sounds like a solid plan.
upvoted 0 times
...
Wilburn
19 days ago
Separate VPCs and connections to backend systems in the corresponding environments is the way to go.
upvoted 0 times
...
Johanna
21 days ago
Option D makes the most sense.
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