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 4 Question 3 Discussion

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

A company uses a hybrid Anypoint Platform deployment model that combines the EU control plane with customer-hosted Mule runtimes. After successfully testing a Mule API implementation in the Staging environment, the Mule API implementation is set with environment-specific properties and must be promoted to the Production environment. What is a way that MuleSoft recommends to configure the Mule API implementation and automate its promotion to the Production environment?

Show Suggested Answer Hide Answer
Suggested Answer: A

Correct Answer : Bundle properties files for each environment into the Mule API implementation's deployable archive, then promote the Mule API implementation to the Production environment using Anypoint CLI or the Anypoint Platform REST APIs

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

>> Anypoint Exchange is for asset discovery and documentation. It has got no provision to modify the properties of Mule API implementations at all.

>> API Manager is for managing API instances, their contracts, policies and SLAs. It has also got no provision to modify the properties of API implementations.

>> API policies are to address Non-functional requirements of APIs and has again got no provision to modify the properties of API implementations.

So, the right way and recommended way to do this as part of development practice is to bundle properties files for each environment into the Mule API implementation and just point and refer to respective file per environment.


Contribute your Thoughts:

Izetta
3 months ago
Using policies to change properties seems a bit convoluted. I'd rather have a single, reliable deployment process.
upvoted 0 times
...
Cherelle
3 months ago
Haha, modifying properties in the API Manager? That's like trying to change the oil in your car while it's driving down the highway!
upvoted 0 times
Davida
2 months ago
Haha, modifying properties in the API Manager? That's like trying to change the oil in your car while it's driving down the highway!
upvoted 0 times
...
Willard
2 months ago
B) Modify the Mule API implementation's properties in the API Manager Properties tab, then promote the Mule API implementation to the Production environment using API Manager
upvoted 0 times
...
Hannah
3 months ago
A) Bundle properties files for each environment into the Mule API implementation's deployable archive, then promote the Mule API implementation to the Production environment using Anypoint CLI or the Anypoint Platform REST APIs
upvoted 0 times
...
...
Tamekia
3 months ago
I like the idea of using Anypoint CLI or Platform APIs to automate the promotion process. That will make it more reliable and repeatable.
upvoted 0 times
Princess
2 months ago
B) Modify the Mule API implementation's properties in the API Manager Properties tab, then promote the Mule API implementation to the Production environment using API Manager
upvoted 0 times
...
Whitney
2 months ago
B) Modify the Mule API implementation's properties in the API Manager Properties tab, then promote the Mule API implementation to the Production environment using API Manager
upvoted 0 times
...
Shannan
2 months ago
A) Bundle properties files for each environment into the Mule API implementation's deployable archive, then promote the Mule API implementation to the Production environment using Anypoint CLI or the Anypoint Platform REST APIs
upvoted 0 times
...
Tiera
2 months ago
B) Modify the Mule API implementation's properties in the API Manager Properties tab, then promote the Mule API implementation to the Production environment using API Manager
upvoted 0 times
...
Elsa
2 months ago
A) Bundle properties files for each environment into the Mule API implementation's deployable archive, then promote the Mule API implementation to the Production environment using Anypoint CLI or the Anypoint Platform REST APIs
upvoted 0 times
...
Staci
3 months ago
A) Bundle properties files for each environment into the Mule API implementation's deployable archive, then promote the Mule API implementation to the Production environment using Anypoint CLI or the Anypoint Platform REST APIs
upvoted 0 times
...
...
Emogene
3 months ago
Option A seems the most straightforward way to handle environment-specific properties. Bundling them into the deployable archive makes sense for promoting the API to production.
upvoted 0 times
Corrina
2 months ago
A: Absolutely, it saves time and ensures consistency in the deployment process
upvoted 0 times
...
Barbra
2 months ago
B: I agree, automation is key when promoting applications to different environments
upvoted 0 times
...
Annice
3 months ago
B) Modify the Mule API implementation's properties in the API Manager Properties tab, then promote the Mule API implementation to the Production environment using API Manager
upvoted 0 times
...
Eveline
3 months ago
A: Definitely, it helps streamline the promotion process and reduces the risk of errors
upvoted 0 times
...
Weldon
3 months ago
B: That sounds like a good approach to ensure the properties are correctly configured for each environment
upvoted 0 times
...
Helaine
3 months ago
A) Bundle properties files for each environment into the Mule API implementation's deployable archive, then promote the Mule API implementation to the Production environment using Anypoint CLI or the Anypoint Platform REST APIs
upvoted 0 times
...
Yolando
3 months ago
A: Bundle properties files for each environment into the Mule API implementation's deployable archive, then promote the Mule API implementation to the Production environment using Anypoint CLI or the Anypoint Platform REST APIs
upvoted 0 times
...
...

Save Cancel