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

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

• Question 91:

  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?

  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 APIsB.
  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
  C. Modify the Mule API implementation's properties in Anypoint Exchange, then promote the Mule API implementation to the Production environment using Runtime Manager
  D. Use an API policy to change properties in the Mule API implementation deployed to the Staging environment and another API policy to deploy the Mule API implementation to the Production environment
  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 APIsB.

  ---

  Explanation

  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.

• Question 92:

  A company has created a successful enterprise data model (EDM). The company is committed to building an application network by adopting modern APIs as a core enabler of the company's IT operating model. At what API tiers (experience, process, system) should the company require reusing the EDM when designing modern API data models?

  A. At the experience and process tiers
  B. At the experience and system tiers
  C. At the process and system tiers
  D. At the experience, process, and system tiers
  C. At the process and system tiers

  ---

  Explanation

  Experience Layer APIs are modeled and designed exclusively for the end user's experience. So, the data models of experience layer vary based on the nature and type of such API consumer. For example, Mobile consumers will need lightweight data models to transfer with ease on the wire, where as web-based consumers will need detailed data models to render most of the info on web pages, so on. So, enterprise data models fit for the purpose of canonical models but not of good use for experience APIs.

  That is why, EDMs should be used extensively in process and system tiers but NOT in experience tier.

• Question 93:

  What condition requires using a CloudHub Dedicated Load Balancer?

  A. When cross-region load balancing is required between separate deployments of the same Mule application
  B. When custom DNS names are required for API implementations deployed to customer-hosted Mule runtimes
  C. When API invocations across multiple CloudHub workers must be load balanced
  D. When server-side load-balanced TLS mutual authentication is required between API implementations and API clients
  D. When server-side load-balanced TLS mutual authentication is required between API implementations and API clients

  ---

  Explanation

  Fact/ Memory Tip: Although there are many benefits of CloudHub Dedicated Load balancer, TWO important things that should come to ones mind for considering it are:

  Having URL endpoints with Custom DNS names on CloudHub deployed apps

  Configuring custom certificates for both HTTPS and Two-way (Mutual) authentication.

  Coming to the options provided for this question:

  We CANNOT use DLB to perform cross-region load balancing between separate deployments of the same Mule application.

  We can have mapping rules to have more than one DLB URL pointing to same Mule app. But vicevera (More than one Mule app having same DLB URL) is NOT POSSIBLE

  It is true that DLB helps to setup custom DNS names for Cloudhub deployed Mule apps but NOT true for apps deployed to Customer-hosted Mule Runtimes.

  It is true to that we can load balance API invocations across multiple CloudHub workers using DLB but it is NOT A MUST. We can achieve the same (load balancing) using SLB (Shared Load Balancer) too. We DO NOT necessarily require

  DLB for achieve it.

  So the only right option that fits the scenario and requires us to use DLB is when TLS mutual authentication is required between API implementations and API clients.

• Question 94:

  A circuit breaker strategy is planned in order to meet the goal of improved response time and demand on a downstream API.

  1. Circuit Open: More than 10 errors per minute for three minutes

  2. Circuit Half-Open: One error per minute

  3. Circuit Closed: Less than one error per minute for five minutes

  Out of several proposals from the engineering team, which option will meet this goal?

  A. Create a custom policy that implements the circuit breaker and includes policy template expressions for the required settings
  B. Create Anypoint Monitoring alerts for Circuit Open/Closed configurations, and then implement a retry strategy for Circuit Half-Open configuration
  C. Add the Circuit Breaker policy to the API instance, and configure the required settings
  D. Implement the strategy in a Mule application, and provide the settings in the YAML configuration
  C. Add the Circuit Breaker policy to the API instance, and configure the required settings

  ---

  Explanation

• Question 95:

  A large lending company has developed an API to unlock data from a database server and web server. The API has been deployed to Anypoint Virtual Private Cloud (VPC) on CloudHub 1.0.

  The database server and web server are in the customer's secure network and are not accessible through the public internet. The database server is in the customer's AWS VPC, whereas the web server is in the customer's on-premises

  corporate data center.

  How can access be enabled for the API to connect with the database server and the web server?

  A. Set up VPC peering with AWS VPC and a VPN tunnel to the customer's on-premises corporate data center
  B. Set up VPC peering with AWS VPC and the customer's on-premises corporate data center
  C. Setup a transit gateway to the customer's on-premises corporate data center through AWS VPC
  D. Set up VPC peering with the customer's on-premises corporate data center and a VPN tunnel to AWS VPC
  A. Set up VPC peering with AWS VPC and a VPN tunnel to the customer's on-premises corporate data center

  ---

  Explanation

• Question 96:

  What are the major benefits of MuleSoft proposed IT Operating Model?

  A. 1. Decrease the IT delivery gap 2. Meet various business demands without increasing the IT capacity 3. Focus on creation of reusable assets first. Upon finishing creation of all the possible assets then inform the LOBs in the organization to start using them
  B. 1. Decrease the IT delivery gap 2. Meet various business demands by increasing the IT capacity and forming various IT departments 3. Make consumption of assets at the rate of production
  C. 1. Decrease the IT delivery gap 2. Meet various business demands without increasing the IT capacity 3. Make consumption of assets at the rate of production
  C. 1. Decrease the IT delivery gap 2. Meet various business demands without increasing the IT capacity 3. Make consumption of assets at the rate of production

  ---

  Explanation

• Question 97:

  An organization wants MuleSoft-hosted runtime plane features (such as HTTP load balancing, zero downtime, and horizontal and vertical scaling) in its Azure environment. What runtime plane minimizes the organization's effort to achieve these features?

  A. Anypoint Runtime Fabric
  B. Anypoint Platform for Pivotal Cloud Foundry
  C. CloudHub
  D. A hybrid combination of customer-hosted and MuleSoft-hosted Mule runtimes
  A. Anypoint Runtime Fabric

  ---

  Explanation

  When a customer is already having an Azure environment, It is not at all an ideal approach to go with hybrid model having some Mule Runtimes hosted on Azure and some on MuleSoft. This is unnecessary and useless.

  CloudHub is a Mulesoft-hosted Runtime plane and is on AWS. We cannot customize to point CloudHub to customer's Azure environment.

  Anypoint Platform for Pivotal Cloud Foundry is specifically for infrastructure provided by Pivotal Cloud Foundry

  Anypoint Runtime Fabric is right answer as it is a container service that automates the deployment and orchestration of Mule applications and API gateways. Runtime Fabric runs within a customer-managed infrastructure on AWS, Azure,

  virtual machines (VMs), and bare-metal servers.

  -Some of the capabilities of Anypoint Runtime Fabric include:

  -Isolation between applications by running a separate Mule runtime per application. -Ability to run multiple versions of Mule runtime on the same set of resources.

  -Scaling applications across multiple replicas.

  -Automated application fail-over.

  -Application management with Anypoint Runtime Manager.

• Question 98:

  What API policy would LEAST likely be applied to a Process API?

  A. Custom circuit breaker
  B. Client ID enforcement
  C. Rate limiting
  D. JSON threat protection
  D. JSON threat protection

  ---

  Explanation

  Fact: Technically, there are no restrictions on what policy can be applied in what layer. Any policy can be applied on any layer API. However, context should also be considered properly before blindly applying the policies on APIs.

  That is why, this question asked for a policy that would LEAST likely be applied to a Process API.

  From the given options:

  All policies except "JSON threat protection" can be applied without hesitation to the APIs in Process tier.

  JSON threat protection policy ideally fits for experience APIs to prevent suspicious JSON payload coming from external API clients. This covers more of a security aspect by trying to avoid possibly malicious and harmful JSON payloads from

  external clients calling experience APIs.

  As external API clients are NEVER allowed to call Process APIs directly and also these kind of malicious and harmful JSON payloads are always stopped at experience API layer only using this policy, it is LEAST LIKELY that this same policy

  is again applied on Process Layer API.

• Question 99:

  A Platinum customer uses the U.S. control plane and deploys applications to CloudHub in Singapore with a default log configuration.

  The compliance officer asks where the logs and monitoring data reside?

  A. Logs are held in:Singapore and monitoring data is held in the United States
  B. Logs and monitoring data are held in the United States
  C. Logs are held in the United States and monitoring data is held in Singapore
  D. Logs and monitoring data are held in Singapore
  B. Logs and monitoring data are held in the United States

  ---

  Explanation

• Question 100:

  What is true about API implementations when dealing with legal regulations that require all data processing to be performed within a certain jurisdiction (such as in the USA or the EU)?

  A. They must avoid using the Object Store as it depends on services deployed ONLY to the US East region
  B. They must use a Jurisdiction-local external messaging system such as Active MQ rather than Anypoint MQ
  C. They must te deployed to Anypoint Platform runtime planes that are managed by Anypoint Platform control planes, with both planes in the same Jurisdiction
  D. They must ensure ALL data is encrypted both in transit and at rest
  C. They must te deployed to Anypoint Platform runtime planes that are managed by Anypoint Platform control planes, with both planes in the same Jurisdiction

  ---

  Explanation

  As per legal regulations, all data processing to be performed within a certain jurisdiction. Meaning, the data in USA should reside within USA and should not go out. Same way, the data in EU should reside within EU and should not go out.

  So, just encrypting the data in transit and at rest does not help to be compliant with the rules. We need to make sure that data does not go out too.

  The data that we are talking here is not just about the messages that are published to Anypoint MQ. It includes the apps running, transaction states, application logs, events, metric info and any other metadata. So, just replacing Anypoint MQ

  with a locally hosted ActiveMQ does NOT help.

  The data that we are talking here is not just about the key/value pairs that are stored in Object Store. It includes the messages published, apps running, transaction states, application logs, events, metric info and any other metadata. So, just

  avoiding using Object Store does NOT help.

  The only option left and also the right option in the given choices is to deploy application on runtime and control planes that are both within the jurisdiction.