Salesforce MULESOFT-PLATFORM-ARCHITECT-I Online Practice Questions and Exam Preparation

Salesforce MULESOFT-PLATFORM-ARCHITECT-I Online Questions & Answers

• Question 1:

  Refer to the exhibit. An organization needs to enable access to their customer data from both a mobile app and a web application, which each need access to common fields as well as certain unique fields.

  The data is available partially in a database and partially in a 3rd-party CRM system.

  What APIs should be created to best fit these design requirements?

  

  

  A. Option A
  B. Option B
  C. Option C
  D. Option D
  C. Option C

  ---

  Explanation

  As per MuleSoft's API-led connectivity:

  Experience APIs should be built as per each consumer needs and their experience.

  Process APIs should contain all the orchestration logic to achieve the business functionality.

  System APIs should be built for each backend system to unlock their data.

• Question 2:

  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?

  A. Modify properties of Mule applications deployed to the production Anypoint Platform environments to prevent access from non-production Mule applications
  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
  C. Create non-production and production environments in different Anypoint Platform business groups
  D. Create separate Anypoint VPCs for non-production and production environments, then configure connections to the backend systems in the corresponding customer-hosted environments
  D. Create separate Anypoint VPCs for non-production and production environments, then configure connections to the backend systems in the corresponding customer-hosted environments

  ---

  Explanation

  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.

  The best practice recommended by 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.

• Question 3:

  An eCommerce company is adding a new Product Details feature to their website, A customer will launch the product catalog page, a new Product Details link will appear by product where they can click to retrieve the product detail description. Product detail data is updated with product update releases, once or twice a year, Presently the database response time has been very slow due to high volume.

  What action retrieves the product details with the lowest response time, fault tolerant, and consistent data?

  A. Select the product details from a database in a Cache scope and return them within the API response
  B. Select the product details from a database and put them in Anypoint MQ; the Anypoint MO subseriber will receive the product details and return them within the API response
  C. Use an object store to store and retrieve the product details originally read from a database and return them within the API response
  D. Select the product details from a database and return them within the API response
  C. Use an object store to store and retrieve the product details originally read from a database and return them within the API response

  ---

  Explanation

• Question 4:

  An API client calls one method from an existing API implementation. The API implementation is later updated. What change to the API implementation would require the API client's invocation logic to also be updated?

  A. When the data type of the response is changed for the method called by the API client
  B. When a new method is added to the resource used by the API client
  C. When a new required field is added to the method called by the API client
  D. When a child method is added to the method called by the API client
  C. When a new required field is added to the method called by the API client

  ---

  Explanation

  Generally, the logic on API clients need to be updated when the API contract breaks.

  When a new method or a child method is added to an API , the API client does not break as it can still continue to use its existing method. So these two options are out.

  We are left for two more where "datatype of the response if changed" and "a new required field is added".

  Changing the datatype of the response does break the API contract. However, the question is insisting on the "invocation" logic and not about the response handling logic. The API client can still invoke the API successfully and receive the

  response but the response will have a different datatype for some field.

  Adding a new required field will break the API's invocation contract. When adding a new required field, the API contract breaks the RAML or API spec agreement that the API client/API consumer and API provider has between them. So this

  requires the API client invocation logic to also be updated.

• Question 5:

  What are 4 important Platform Capabilities offered by Anypoint Platform?

  A. API Versioning, API Runtime Execution and Hosting, API Invocation, API Consumer Engagement
  B. API Design and Development, API Runtime Execution and Hosting, API Versioning, API Deprecation
  C. API Design and Development, API Runtime Execution and Hosting, API Operations and Management, API Consumer Engagement
  D. API Design and Development, API Deprecation, API Versioning, API Consumer Engagement
  C. API Design and Development, API Runtime Execution and Hosting, API Operations and Management, API Consumer Engagement

  ---

  Explanation

  API Design and Development - Anypoint Studio, Anypoint Design Center, Anypoint Connectors API Runtime Execution and Hosting - Mule Runtimes, CloudHub, Runtime Services API Operations and Management - Anypoint API Manager, Anypoint Exchange API Consumer Management - API Contracts, Public Portals, Anypoint Exchange, API Notebooks

• Question 6:

  A company wants to move its Mule API implementations into production as quickly as possible. To protect access to all Mule application data and metadata, the company requires that all Mule applications be deployed to the company's customer-hosted infrastructure within the corporate firewall. What combination of runtime plane and control plane options meets these project lifecycle goals?

  A. Manually provisioned customer-hosted runtime plane and customer-hosted control plane
  B. MuleSoft-hosted runtime plane and customer-hosted control plane
  C. Manually provisioned customer-hosted runtime plane and MuleSoft-hosted control plane
  D. iPaaS provisioned customer-hosted runtime plane and MuleSoft-hosted control plane
  A. Manually provisioned customer-hosted runtime plane and customer-hosted control plane

  ---

  Explanation

  There are two key factors that are to be taken into consideration from the scenario given in the question.

  Company requires both data and metadata to be resided within the corporate firewall

  Company would like to go with customer-hosted infrastructure.

  Any deployment model that is to deal with the cloud directly or indirectly (Mulesoft-hosted or Customer's own cloud like Azure, AWS) will have to share atleast the metadata.

  Application data can be controlled inside firewall by having Mule Runtimes on customer hosted runtime plane. But if we go with Mulsoft-hosted/ Cloud-based control plane, the control plane required atleast some minimum level of metadata to

  be sent outside the corporate firewall.

  As the customer requirement is pretty clear about the data and metadata both to be within the corporate firewall, even though customer wants to move to production as quickly as possible, unfortunately due to the nature of their security

  requirements, they have no other option but to go with manually provisioned customer-hosted runtime plane and customer-hosted control plane.

• Question 7:

  An Order API must be designed that contains significant amounts of integration logic and involves the invocation of the Product API.

  The power relationship between Order API and Product API is one of "Customer/Supplier", because the Product API is used heavily throughout the organization and is developed by a dedicated development team located in the office of the

  CTO.

  What strategy should be used to deal with the API data model of the Product API within the Order API?

  A. Convince the development team of the Product API to adopt the API data model of the Order API such that the integration logic of the Order API can work with one consistent internal data model
  B. Work with the API data types of the Product API directly when implementing the integration logic of the Order API such that the Order API uses the same (unchanged) data types as the Product API
  C. Implement an anti-corruption layer in the Order API that transforms the Product API data model into internal data types of the Order API
  D. Start an organization-wide data modeling initiative that will result in an Enterprise Data Model that will then be used in both the Product API and the Order API
  C. Implement an anti-corruption layer in the Order API that transforms the Product API data model into internal data types of the Order API

  ---

  Explanation

  Key details to note from the given scenario:

  Power relationship between Order API and Product API is customer/supplier

  So, as per below rules of "Power Relationships", the caller (in this case Order API) would request for features to the called (Product API team) and the Product API team would need to accomodate those requests.

• Question 8:

  Traffic is routed through an API proxy to an API implementation. The API proxy is managed by API Manager and the API implementation is deployed to a CloudHub VPC using Runtime Manager. API policies have been applied to this API. In this deployment scenario, at what point are the API policies enforced on incoming API client requests?

  A. At the API proxy
  B. At the API implementation
  C. At both the API proxy and the API implementation
  D. At a MuleSoft-hosted load balancer
  A. At the API proxy

  ---

  Explanation

  API Policies can be enforced at two places in Mule platform.

  One - As an Embedded Policy enforcement in the same Mule Runtime where API implementation is running.

  Two - On an API Proxy sitting in front of the Mule Runtime where API implementation is running.

  As the deployment scenario in the question has API Proxy involved, the policies will be enforced at the API Proxy.

• Question 9:

  A Mule application exposes an HTTPS endpoint and is deployed to the CloudHub Shared Worker Cloud. All traffic to that Mule application must stay inside the AWS VPC. To what TCP port do API invocations to that Mule application need to be sent?

  A. 443
  B. 8081
  C. 8091
  D. 8082
  D. 8082

  ---

  Explanation

  8091 and 8092 ports are to be used when keeping your HTTP and HTTPS app private to the LOCAL VPC respectively.

  Above TWO ports are not for Shared AWS VPC/ Shared Worker Cloud.

  8081 is to be used when exposing your HTTP endpoint app to the internet through Shared LB

  8082 is to be used when exposing your HTTPS endpoint app to the internet through Shared LB

  So, API invocations should be sent to port 8082 when calling this HTTPS based app.

  References:

  https://docs.mulesoft.com/runtime-manager/cloudhub-networking-guide https://help.mulesoft.com/s/article/Configure-Cloudhub-Application-to-Send-a-HTTPS-Request-Directly-to-Another-Cloudhub-Application https://help.mulesoft.com/s/question/0D52T00004mXXULSA4/multiple-http-listerners-on-cloudhub-one-with-port-9090

• Question 10:

  An API has been updated in Anypoint Exchange by its API producer from version 3. 1.1 to 3. 2. 0 following accepted semantic versioning practices and the changes have been communicated via the API's public portal.

  The API endpoint does NOT change in the new version.

  How should the developer of an API client respond to this change?

  A. The update should be identified as a project risk and full regression testing of the functionality that uses this API should be run
  B. The API producer should be contacted to understand the change to existing functionality
  C. The API producer should be requested to run the old version in parallel with the new one
  D. The API client code ONLY needs to be changed if it needs to take advantage of new features
  D. The API client code ONLY needs to be changed if it needs to take advantage of new features

  ---

  Explanation