Salesforce MuleSoft-Integration-Architect-I Exam With Confidence Using Practice Dumps

To securely handle sensitive properties in a Mule application deployed through a CI/CD pipeline, the properties should be encrypted and stored as global configuration properties. This ensures that sensitive data is not visible in cleartext in Runtime Manager or any other configuration files. The steps are:

Encrypt Sensitive Properties: Use a tool or process to encrypt sensitive property values.

Global Configuration Properties: Store these encrypted values as global configuration properties within the Mule application.

Configuration in Runtime Manager: Ensure that these properties are referenced correctly so that administrators with proper permissions can manage them in Runtime Manager without exposing the sensitive values.

This approach aligns with security best practices and complies with the requirement to hide sensitive properties while allowing administrative control.

References

MuleSoft Documentation on Secure Property Placeholder

Best Practices for Handling Sensitive Data in MuleSoft

API Manager is a component of the Anypoint Platform's control plane. The control plane in Anypoint Platform is responsible for managing, securing, and monitoring APIs and integrations. API Manager specifically provides tools for API governance, including policy enforcement, analytics, security, and lifecycle management. It allows organizations to manage APIs centrally, ensuring they adhere to compliance and security standards while providing insights into API usage and performance.

Explanation

Mule applications are deployed in CloudHub workers and each worker is assigned with a dedicated IP • For zero downtime deployment, each worker in CloudHub needs additional IP addresses • A few IPs in a VPC are reserved for infrastructure (generally 2 IPs) • The IP addresses are usually in a private range with a subnet block specifier, such as 10.0.0.1/24 • The smallest CIDR network subnet block you can assign for your VPC is /24 (256 IP addresses) (60*3 env * 2 worker per application ) + 50% of (total) for zero downtime = 540 In this case correct answer is 10.0.0.0/22 as this provided 1024 IP's .

Other IP's are insufficient.