Microsoft Certified Power Platform Functional Consultant Associate · Free Practice Question Medium
Question 52
Scenario: Roxxon Energy Corporation (NYSE: ROX) is an American multinational oil and gas corporation headquartered at the One Roxxon Plaza in Manhattan, New York City. It is one of the largest fuel conglomerates around the world. The Corporation generated billions of dollars in profits each year by refining and manufacturing products related to oil through its many holdings. The founder of the company, J.T. Jones, has hired you as a Microsoft Power Automate SME to assist with their IT projects.
At the moment, the team is working on correcting a failure based on limits. The current setup has the following:
• 250 flows
• 30 custom connectors
• 20 connections per application programming interface (API) and 100 connections total
Which of the following have exceeded their permitted limits? (Select all that apply)
-
A
Only 1 item has exceeded its threshold
-
B
Connections per API
-
C
Custom connectors
-
D
Flows
-
E
None have exceeded their threshold
-
F
Total connections
Reveal correct answers
Correct answers: A, C
Explanation
Identify the error
Before you can fix a flow, you must identify why it failed. You will get an email with a list of failures each week.
1. Select the Settings button (the gear symbol) at the top of the web portal and select Activity (or select the Activity tab in the mobile app), and then select your flow in the list that appears.
2. Details about the flow appear, and at least one step has a red exclamation point (!) symbol. Open that step, and review the error message.
Authentication failures
In many cases, flows fail because of an authentication error. If this type of error occurs, the error message includes the word "Unauthorized," or an error code of 401 or 403 appears. You can usually fix authentication errors by updating the connection.
1. You can view the connections by opening up the flow details by selecting the flow from My Flows.
2. Scroll to the connection that you saw the "Unauthorized" error message for.
3. Next to the connection, select the Verify password link in the message that states that the connection hasn't been authenticated.
4. Verify your credentials by following the instructions that appear. Then return to your flow-run failure, and select Resubmit.
The flow should now run as expected.
Action configuration issues
Flows sometimes fail if a setting in one of the flow's actions doesn't work as expected. In this case, the error message includes the phrase "Bad request" or "Not found," or an error code 400 or 404 appears.
The error message should indicate how to fix the failure.
Select the Edit button, and then fix the issues inside the flow definition.
Save the updated flow, and then select Resubmit to try to run the flow again with the updated configuration.
Temporary issues
If error code 500 or 502 appears, the failure is temporary or transient.
Select Resubmit to try to run the flow again.
Issues with your pricing plan
Sometimes your flows might behave unexpectedly because you aren't using the correct plan.
To view your plan, in Power Automate, select Learn. It will redirect you to another page. Here select Learn, and then select Pricing.
Learn more about pricing and how to switch plans.
Issues with data usage
You might have run out of data that you can use.
If you're on a free plan or a trial plan, select the Settings button (the gear symbol) to show your current usage against your plan.
If you're on a paid plan, runs are pooled across all users in your organization. We're working on features that will show information about available quotas and usage across an organization.
Important: If you exceed your data limit, Power Automate throttles your flow runs.
You might be running flows too often
Your plan determines how often your flows run. For example, your flows might run every 15 minutes if you're on the free plan. If a flow is triggered less than 15 minutes after its last run, it's queued until 15 minutes have passed.
Whenever a flow is triggered, whether by an automatic trigger or because you manually start it, the action counts as a run. Checks for new data don't count as runs.
Learn more about usage limits.
You might be using an incorrect account
If you sign in by using a Microsoft account (for example, an account that ends with @outlook.com or @gmail.com), you can use only the free plan. To take advantage of the features of the paid plan, sign in by using your organizational account or school email address.
To upgrade, use an organizational account or a school account, or create a Microsoft Office 365 trial account.
Some flows run more often than expected
Some flows might run more often than you expect. For example, you create a flow that sends you a push notification whenever your manager sends you an email. That flow must run every time you get an email from anyone because the flow must check whether the email came from your manager. This action counts as a run.
Other issues that are based on limits, and caveats
You might have issues that are based on other limits:
Each account can have up to:
250 flows.
15 custom connectors.
20 connections per application programming interface (API) and 100 connections total.
You can install a gateway only in the default environment.
Some external connectors, like Twitter, implement connection throttling to control the quality of service. Your flows might fail when throttling is in effect. If your flows are failing, review the details of the run that failed in the flow's run history.
A.
Custom connectors has exceeded their permitted limit of 25, which indicates that the team has surpassed the maximum number of custom connectors allowed in the current setup.
B. Connections per API have not exceeded their permitted limit of 20, as the current setup allows for 20 connections per API. This means that the team can still establish connections within the specified limit without any issues.
C.
Custom connectors has exceeded their permitted limit of 25, which indicates that the team has surpassed the maximum number of custom connectors allowed in the current setup.
D. Flows have not exceeded their permitted limit of 250, as the current setup has 250 flows. This means that the team can continue to create new flows within the specified limit without encountering any restrictions.
E.
Custom connectors has exceeded their permitted limit of 25, which indicates that the team has surpassed the maximum number of custom connectors allowed in the current setup.
F.
The current setup allows for a total of 100 connections, which has been reached. This means that the total number of connections across all APIs has reached the limit, and further connections cannot be established until the limit is increased.
Discussion
Think the marked answer is wrong, or have a better explanation? Share it below — comments appear after review.
