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

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

• Question 111:

  When should idempotency be taken into account?

  A. When making requests to update currently locked entities
  B. When storing the results of s previous request for use in response to subsequent requests
  C. When sending concurrent update requests for the same entity
  D. When preventing duplicate processing from multiple sent requests
  D. When preventing duplicate processing from multiple sent requests

  ---

  Explanation

• Question 112:

  An organization has several APIs that accept JSON data over HTTP POST. The APIs are all publicly available and are associated with several mobile applications and web applications.

  The organization does NOT want to use any authentication or compliance policies for these APIs, but at the same time, is worried that some bad actor could send payloads that could somehow compromise the applications or servers running

  the API implementations.

  What out-of-the-box Anypoint Platform policy can address exposure to this threat?

  A. Shut out bad actors by using HTTPS mutual authentication for all API invocations
  B. Apply an IP blacklist policy to all APIs; the blacklist will Include all bad actors
  C. Apply a Header injection and removal policy that detects the malicious data before it is used
  D. Apply a JSON threat protection policy to all APIs to detect potential threat vectors
  D. Apply a JSON threat protection policy to all APIs to detect potential threat vectors

  ---

  Explanation

  Usually, if the APIs are designed and developed for specific consumers (known consumers/customers) then we would IP Whitelist the same to ensure that traffic only comes from them. However, as this scenario states that the APIs are publicly available and being used by so many mobile and web applications, it is NOT possible to identify and blacklist all possible bad actors. So, JSON threat protection policy is the best chance to prevent any bad JSON payloads from such bad actors.

• Question 113:

  An IT Security Compliance Auditor is assessing which nonfunctional requirements (NFRs) are already being implemented to meet security measures.

  1. The Web API has Rate-Limiting SLA

  2. Basic Authentication - LDAP

  3. JSON Threat Protection

  4. TP Allowlist policies applied Which two NFRs-are enforced?

  A. The API invocations are coming from a known subnet range
  B. Username/password supported to validate login credentials
  C. Sensitive data is masked to prevent compromising critical information
  D. The API is protected against XML invocation attacks
  E. Performance expectations are to be allowed up to 1,000 requests per second
  A. The API invocations are coming from a known subnet range
  B. Username/password supported to validate login credentials

  ---

  Explanation

• Question 114:

  What should be ensured before sharing an API through a public Anypoint Exchange portal?

  A. The visibility level of the API instances of that API that need to be publicly accessible should be set to public visibility
  B. The users needing access to the API should be added to the appropriate role in Anypoint Platform
  C. The API should be functional with at least an initial implementation deployed and accessible for users to interact with
  D. The API should be secured using one of the supported authentication/authorization mechanisms to ensure that data is not compromised
  A. The visibility level of the API instances of that API that need to be publicly accessible should be set to public visibility

  ---

  Explanation

• Question 115:

  A company deploys Mule applications with default configurations through Runtime Manager to customer-hosted Mule runtimes. Each Mule application is an API implementation that exposes RESTful interfaces to API clients. The Mule

  runtimes are managed by the MuleSoft-hosted control plane. The payload is never used by any Logger components.

  When an API client sends an HTTP request to a customer-hosted Mule application, which metadata or data (payload) is pushed to the MuleSoft-hosted control plane?

  A. Only the data
  B. No data
  C. The data and metadata
  D. Only the metadata
  D. Only the metadata

  ---

  Explanation

• Question 116:

  An organization is deploying their new implementation of the OrderStatus System API to multiple workers in CloudHub. This API fronts the organization's on-premises Order Management System, which is accessed by the API implementation over an IPsec tunnel.

  What type of error typically does NOT result in a service outage of the OrderStatus System API?

  A. A CloudHub worker fails with an out-of-memory exception
  B. API Manager has an extended outage during the initial deployment of the API implementation
  C. The AWS region goes offline with a major network failure to the relevant AWS data centers
  D. The Order Management System is Inaccessible due to a network outage in the organization's on-premises data center
  A. A CloudHub worker fails with an out-of-memory exception

  ---

  Explanation

  An AWS Region itself going down will definitely result in an outage as it does not matter how many workers are assigned to the Mule App as all of those in that region will go down. This is a complete downtime and outage.

  Extended outage of API manager during initial deployment of API implementation will of course cause issues in proper application startup itself as the API Autodiscovery might fail or API policy templates and polices may not be downloaded to

  embed at the time of applicaiton startup etc... there are many reasons that could cause issues.

  A network outage onpremises would of course cause the Order Management System not accessible and it does not matter how many workers are assigned to the app they all will fail and cause outage for sure.

  The only option that does NOT result in a service outage is if a cloudhub worker fails with an out-of-memory exception. Even if a worker fails and goes down, there are still other workers to handle the requests and keep the API UP and

  Running. So, this is the right answer.

• Question 117:

  Refer to the exhibit.

  

  What is a valid API in the sense of API-led connectivity and application networks?

  

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

  ---

  Explanation

• Question 118:

  What is true about the technology architecture of Anypoint VPCs?

  A. The private IP address range of an Anypoint VPC is automatically chosen by CloudHub
  B. Traffic between Mule applications deployed to an Anypoint VPC and on-premises systems can stay within a private network
  C. Each CloudHub environment requires a separate Anypoint VPC
  D. VPC peering can be used to link the underlying AWS VPC to an on-premises (non AWS) private network
  B. Traffic between Mule applications deployed to an Anypoint VPC and on-premises systems can stay within a private network

  ---

  Explanation

  The private IP address range of an Anypoint VPC is NOT automatically chosen by CloudHub. It is chosen by us at the time of creating VPC using thr CIDR blocks.

  CIDR Block: The size of the Anypoint VPC in Classless Inter-Domain Routing (CIDR) notation.

  For example, if you set it to 10.111.0.0/24, the Anypoint VPC is granted 256 IP addresses from 10.111.0.0 to 10.111.0.255.

  Ideally, the CIDR Blocks you choose for the Anypoint VPC come from a private IP space, and should not overlap with any other Anypoint VPC's CIDR Blocks, or any CIDR Blocks in use in your corporate network. that each CloudHub

  environment requires a separate Anypoint VPC. Once an Anypoint VPC is created, we can choose a same VPC by multiple environments. However, it is generally a best and recommended practice to always have seperate Anypoint VPCs for

  Non-Prod and Prod environments.

  We use Anypoint VPN to link the underlying AWS VPC to an on-premises (non AWS) private network.

  NOT VPC Peering.

• Question 119:

  What is the main change to the IT operating model that MuleSoft recommends to organizations to improve innovation and clock speed?

  A. Drive consumption as much as production of assets; this enables developers to discover and reuse assets from other projects and encourages standardization
  B. Expose assets using a Master Data Management (MDM) system; this standardizes projects and enables developers to quickly discover and reuse assets from other projects
  C. Implement SOA for reusable APIs to focus on production over consumption; this standardizes on XML and WSDL formats to speed up decision making
  D. Create a lean and agile organization that makes many small decisions everyday; this speeds up decision
  E. making and enables each line of business to take ownership of its projects
  A. Drive consumption as much as production of assets; this enables developers to discover and reuse assets from other projects and encourages standardization

  ---

  Explanation

  The main motto of the new IT Operating Model that MuleSoft recommends and made popular is to change the way that they are delivered from a production model to a production + consumption model, which is done through an API strategy

  called API-led connectivity.

  The assets built should also be discoverable and self-serveable for reusablity across LOBs and organization.

  MuleSoft's IT operating model does not talk about SDLC model (Agile/ Lean etc) or MDM at all. So, options suggesting these are not valid.

  References:

  https://blogs.mulesoft.com/biz/connectivity/what-is-a-center-for-enablement-c4e/

  https://www.mulesoft.com/resources/api/secret-to-managing-it-projects

• Question 120:

  What is true about automating interactions with Anypoint Platform using tools such as Anypoint Platform REST APIs, Anypoint CU, or the Mule Maven plugin?

  A. Access to Anypoint Platform APIs and Anypoint CU can be controlled separately through the roles and permissions in Anypoint Platform, so that specific users can get access to Anypoint CLI white others get access to the platform APIs
  B. Anypoint Platform APIs can ONLY automate interactions with CloudHub, while the Mule Maven plugin is required for deployment to customer-hosted Mule runtimes
  C. By default, the Anypoint CLI and Mule Maven plugin are NOT included in the Mule runtime, so are NOT available to be used by deployed Mule applications
  D. API policies can be applied to the Anypoint Platform APIs so that ONLY certain LOBs have access to specific functions
  C. By default, the Anypoint CLI and Mule Maven plugin are NOT included in the Mule runtime, so are NOT available to be used by deployed Mule applications

  ---

  Explanation

  We CANNOT apply API policies to the Anypoint Platform APIs like we can do on our custom written API instances. So, option suggesting this is FALSE.

  Anypoint Platform APIs can be used for automating interactions with both CloudHub and customer-hosted Mule runtimes. Not JUST the CloudHub. So, option opposing this is FALSE.

  Mule Maven plugin is NOT mandatory for deployment to customer-hosted Mule runtimes. It just helps your CI/CD to have smoother automation. But not a compulsory requirement to deploy. So, option opposing this is FALSE.

  We DO NOT have any such special roles and permissions on the platform to separately control access for some users to have Anypoint CLI and others to have Anypoint Platform APIs. With proper general roles/permissions (API Owner,

  Cloudhub Admin etc..), one can use any of the options (Anypoint CLI or Platform APIs). So, option suggesting this is FALSE.

  Only TRUE statement given in the choices is that - Anypoint CLI and Mule Maven plugin are NOT included in the Mule runtime, so are NOT available to be used by deployed Mule applications.

  Maven is part of Studio or you can use other Maven installation for development.

  CLI is convenience only. It is one of many ways how to install app to the runtime.

  These are definitely NOT part of anything except your process of deployment or automation.