Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  2. Home
  3. Exams
  4. Salesforce
  5. Salesforce-Hyperautomation-Specialist

Salesforce Salesforce-Hyperautomation-Specialist Exam
Salesforce Certified Hyperautomation Specialist (Page 6 )

Updated On: 1-Feb-2026
Page 2 of 13
PDF with 60 Questions

Northern Trail Outfitters needs to update multiple systems outside of Salesforce based on record updates within Salesforce. A hyperautomation practitioner needs to configure Salesforce to call several APIs created by the MuleSoft development team from within a Salesforce flow.
What specifications must be imported into Salesforce to make external services available to a Salesforce flow that enables external invokable actions?

  1. Open API specifications
  2. External API specifications
  3. RAML API specifications
  4. Anypoint API specifications

Answer(s): A

Explanation:

To enable Salesforce to call external services within a flow, the appropriate specifications must be imported to make these external services available as invokable actions. The correct specification is Open API specifications. OpenAPI Specification (formerly known as Swagger) is a standard for defining APIs which can be easily imported into Salesforce to facilitate the integration and invocation of external services.
Import OpenAPI Specifications: Salesforce allows the import of OpenAPI specifications, which define the available endpoints and operations of an API, making them accessible as invocable actions in a Salesforce flow.
Creating External Services: By importing an OpenAPI definition into Salesforce, it creates an External Service, which you can then use within Flow to interact with the defined APIs. Flow Integration: Once imported, these services can be integrated into Salesforce Flows to automate processes that require interaction with external systems.


Reference:

Salesforce External Services and API Integrations



Northern Trail Outfitters (NTO) has outgrown its custom Extract-Transform-Load (ETL) solution and needs to migrate its ETL jobs to a new tool. One of the requirements is a single interface to view and manage the ETL jobs. Some of these ETL jobs interact with systems that are hosted on-premises. According to Salesforce's hyperautomation best practices, how should Salesforce's various hyperautomation solutions be combined to meet NTO's requirements?

  1. Migrate all integrations to MuleSoft Compose.
    Use the Salesforce UI to view all MuleSoft Composer integrations.
    Leverage MuleSoft RPA for on-premises systems.
  2. Implement a three-tier API-led strategy to migrate its ETL jobs to a new tool.
    Use Anypoint API Manager to view and manage all API integrations.
  3. Migrate integrations with simple transformations to MuleSoft Composer and complex integrations to Anypoint Platform.
    Use Anypoint Exchange to view and manage all API integrations.
  4. Use External Services in Salesforce to connect with Anypoint Platform.
    Use Orchestrator to coordinate the different ETL jobs in a single UI.
    Leverage MuleSoft RPA for on-premises systems.

Answer(s): C

Explanation:

To meet NTO's requirements of migrating ETL jobs and managing them efficiently, the following approach is recommended:
Migrate Simple Integrations to MuleSoft Composer:
MuleSoft Composer is suitable for simple transformations and straightforward data integrations that do not require complex logic or custom coding. This allows non-technical users to manage and automate these processes easily.
Migrate Complex Integrations to Anypoint Platform:
For more complex integrations that involve intricate business logic, large data volumes, or require advanced features like error handling, use Anypoint Platform. Anypoint Platform provides robust capabilities for building, deploying, and managing APIs and integrations.
Use Anypoint Exchange:
Anypoint Exchange serves as a centralized repository for all API assets, including those created using Composer and Anypoint Platform. It provides a single interface to view, manage, and share API integrations.
This approach leverages the strengths of both tools and ensures that all API integrations are efficiently managed and monitored.


Reference:

Anypoint Platform Documentation
Anypoint Exchange Documentation



Northern Trail Outfitters wants to create an automation which runs on a fixed schedule to enter sales data into NetSuite running as a process in the background. The business product owner chose MuleSoft Composer as the tool for this task.
The Salesforce admin wants to advise the product owner about how the MuleSoft Composer scheduling functionality works.
Which two options are available for use as the time mechanism within MuleSoft Composer? (Choose two.)

  1. Schedule based on a formula
  2. Every 30 minutes
  3. Every 30 days
  4. Every 5 minutes

Answer(s): B,D

Explanation:

MuleSoft Composer provides scheduling functionality that allows you to set up automated flows to run at specified intervals. The available options for scheduling within MuleSoft Composer include:
Every 30 minutes:
This option allows you to set up a flow to run every half hour, ensuring that your automation process is executed at regular intervals throughout the day.

Every 5 minutes:
This option enables the flow to run at a higher frequency, executing the automation process every 5 minutes, which is useful for scenarios that require more frequent updates or processing. These scheduling options ensure that you can automate tasks at the desired frequency without manual intervention.


Reference:

MuleSoft Composer Documentation



Which API policy can be applied to limit the number of requests an individual client can make to an API?

  1. Client ID Enforcement
  2. Spike Control
  3. Rate limiting - SLA-Based
  4. OAuth 2.0 access token enforcement

Answer(s): C

Explanation:

The Rate Limiting - SLA-Based policy in Anypoint Platform is designed to control the number of requests an individual client can make to an API. This policy is highly configurable and allows you to set specific limits based on service level agreements (SLAs).
Rate Limiting - SLA-Based:
This policy helps protect APIs from being overwhelmed by too many requests by enforcing a limit on the number of requests a client can make within a specified time frame. You can define different rate limits for different tiers of clients, ensuring fair usage and protecting backend services.


Reference:

Anypoint Platform Rate Limiting Documentation



Northern Trail Outfitters evaluates multiple standards for the exit criteria of a stage in their Flow

Orchestration. Based on their criteria, they want the flow to go down one of three paths. How should this be built in Flow Orchestration to meet this requirement?

  1. Use the evaluation flow to determine the exit criteria for the current stage. Then, use a separate evaluation flow to determine the entry criteria for each of the three paths.
  2. Have the evaluation flow return a number variable, and use a decision element to determine which path to execute.
  3. Create two evaluation flows, and execute the second evaluation flow if the first evaluation flow returns false.
  4. Evaluate the criteria for the first two paths in an evaluation flow. Then, use the default path functionality of the decision element for the third path.

Answer(s): B

Explanation:

To implement branching logic based on multiple criteria in Flow Orchestration, you can use the following approach:
Evaluation Flow Returns a Number Variable:
Create an evaluation flow that assesses the exit criteria for the current stage and returns a number variable indicating which path to take (e.g., 1, 2, or 3).
Decision Element:
Use a decision element in Flow Orchestration to evaluate the number variable returned by the evaluation flow. Based on the value of the variable, the decision element will determine which path to execute next.
This approach allows for clear and maintainable branching logic, ensuring that the flow can proceed down one of three paths based on the defined criteria.


Reference:

Salesforce Flow Orchestration Documentation



Viewing page 6 of 13
Viewing questions 26 - 30 out of 60 questions



Post your Comments and Discuss Salesforce Salesforce-Hyperautomation-Specialist exam prep with other Community members:

Join the Salesforce-Hyperautomation-Specialist Discussion