CCNA Power Automate Capabilities Questions

An automated cloud flow can trigger on new SharePoint item, include a condition to check amount, use an approval action, and conditionally update the item. Desktop flows are for desktop automation. Business process flows guide users.

Instant flows need manual trigger.

Option A is correct because the action posts a message to the 'General' channel of the 'Marketing' team, including dynamic content from the trigger. Option B is wrong because it is not a chat. Option C is wrong because it does not send an email.

Option D is wrong because it does not create a channel.

Option C is correct because the file content must be retrieved from SharePoint before sending. The 'Get file content' action is required to pass the binary data to the email action. Option A is wrong because the trigger is fine.

Option B is wrong because permission to read the list does not guarantee access to the file. Option D is wrong because the email action itself is capable of attachments.

Option B is correct because gateway timeout indicates the SQL query took too long. Option A is wrong because connection issues cause different errors. Option C is wrong because permission errors are 401/403.

Option D is wrong because throttling returns 429.

Option D is correct because the scenario requires conditional logic: evaluate the amount and branch accordingly. A Condition action is ideal for the primary split (above/below thresholds), and nested conditions handle the sub-branches. Option A is wrong because Apply to each is for iterating arrays.

Option B is wrong because Switch works for discrete values, not ranges. Option C is wrong because Parallel branches run actions concurrently but don't implement branching logic.

Option A is correct because the flow has no approval action; it just sends an email. Option B is wrong because the email action is valid. Option C is wrong because the trigger is valid.

Option D is wrong because authentication is specified.

If the payload format is correct, the issue might be that the request URL changed or the flow was deactivated. The HTTP trigger URL is unique per flow; if the flow is turned off, it returns a 404. However, 400 errors indicate client error; the flow might be turned off or the URL changed.

But since the payload is correct, the most likely is that the trigger URL was regenerated or changed. Other options like schema mismatch or authentication would cause different errors.

Option A is correct because approval flows are designed for manual approval steps. Option B is for background automation. Option C is for process adherence.

Option D is for UI automation.

Option C is correct because a button flow (instant flow) is triggered by a manual button press. Option A responds to events, not manual triggers. Option B runs on a schedule.

Option D is for business process flows, not button triggers.

Option D is correct because 'When a user is added' triggers on new user creation. Option A is wrong because it's for Microsoft Entra ID group changes. Option B is wrong because it's for user deletion.

Option C is wrong because it's for user attribute changes.

An instant cloud flow can be triggered from a button or app. Automated flows trigger on events. Scheduled flows run on schedule.

Desktop flows are for desktop automation.

Option B is correct because the 'When a file is created' trigger is designed to start a flow when a new file appears in a SharePoint library. Option A is wrong because 'When a file is modified' triggers on updates, not creation. Option C is wrong because 'When a file is deleted' triggers on removal.

Option D is wrong because 'When a file is created or modified' includes modification events.

Option B is correct because the 'Get manager' action returns the manager's email address, but if the manager's mailbox is not enabled (e.g., a distribution group or shared mailbox), the approval email will not be delivered. Option A is wrong because the flow succeeds so the manager is found. Option C is wrong because approvals are sent via email.

Option D is wrong because the flow uses the correct connector.

Option A is correct because configuring duplicate detection rules in Dataverse and using the 'Create a new record' action with duplicate detection enabled will prevent duplicates. Option B is wrong because using 'Update a record' requires an existing record. Option C is wrong because 'Delete a record' is not relevant.

Option D is wrong because the 'Compose' action does not create records.

Option B is correct because the 'Parse JSON' action uses a schema generated from a sample payload. If the schema does not include optional fields, the action will fail when those fields are present. Option A is wrong because the webhook is sending data.

Option C is wrong because the flow action is to parse, not to create. Option D is wrong because the error is 'Invalid JSON' not a missing property.

The 'When a new response is submitted' trigger for Microsoft Forms is the correct trigger. Option B is for when a response is modified. Option C is for viewing responses.

Option D is for editing responses.

Option C is correct because the trigger schema defines 'email' as required, but the Send_an_email action uses an expression that may resolve to null if the trigger body does not contain the email. Option A is wrong because the schema is valid. Option B is wrong because the action is correctly configured.

Option D is wrong because the subject is not the issue.

A and D are correct. Run history provides details of each flow execution, including inputs, outputs, and errors. Analytics in the Power Platform admin center provide insights into flow usage and performance.

Option B is incorrect because email notifications are not a built-in monitoring feature; they can be configured but are not a capability. Option C is incorrect because the 'When a flow is completed' trigger is used to start another flow, not to monitor. Option E is incorrect because the 'Configure run after' setting controls flow behavior on failure, not monitoring.

Options A and D are correct. Automated triggers (event-based) and scheduled triggers (time-based) are the main categories. Option B is wrong because 'Manual' is a trigger type but the stem asks for types of triggers; manual is a subtype.

Option C is wrong because 'Recurrence' is a specific scheduled trigger, not a type. Option E is wrong because 'Instant' is a kind of manual trigger.

Option D is correct because using a service principal with appropriate permissions ensures consistent access. Option A is wrong because run-only users would inherit limited permissions. Option B is wrong because the owner's permissions may not match the flow's needs.

Option C is wrong because turning off enhanced mode would limit capabilities.

A scheduled cloud flow can run on a recurring schedule (e.g., first day of month) and includes actions to query SharePoint and send email. Automated flows trigger on events, not schedules. Desktop flows are for desktop automation.

Business process flows guide users through stages.

Option D is correct because data loss prevention (DLP) policies allow admins to control which connectors can share data and enforce encryption requirements. Option A is incorrect because the 'Run only for the flow owner' feature controls authentication, not encryption. Option B is incorrect because solution-aware flows are for lifecycle management, not compliance.

Option C is incorrect because conditions are for branching logic.

Option B is correct because 'When a user is added to Azure AD' (now Microsoft Entra ID) triggers on new user creation. Option A is wrong because it triggers on email, not user creation. Option C is wrong because it triggers on file creation.

Option D is wrong because it triggers on record creation in Dataverse.

The 'Condition' action allows branching based on expressions. Option A is for iteration. Option B is for switching based on multiple values.

Option C is for data transformation. Option D is not a flow action.

Option D is correct because the HTTP trigger returns a 500 error when the flow response action is not configured correctly, such as missing a 'Respond to a PowerApp or flow' action. Option A is wrong because the trigger fires. Option B is wrong because the flow runs, so the request is received.

Option C is wrong because authentication errors typically return 401.

Option A is correct because the 'Recurrence' trigger runs on a schedule. Option B is wrong because it triggers on new email, not time. Option C is wrong because it triggers on new tweets, not time.

Option D is wrong because manual triggers require user interaction.

A, C, and E are correct. Using child flows promotes reusability. Using solution-aware flows enables application lifecycle management (ALM).

Using descriptive names improves readability. Option B is incorrect because you should avoid hardcoding values; use variables or configuration. Option D is incorrect because complex expressions should be broken into simpler steps or use child flows.

The correct answer is C because the 'Start and wait for an approval' action handles the approval flow and includes built-in reminder functionality. Option A is incorrect because Approvals connector is a collection of actions, not a specific feature for waiting with reminders. Option B is incorrect because 'Send an email' would not enforce approval logic.

Option D is incorrect because 'Condition' is for branching, not for reminders.

Option B is correct because HTTP requests to SharePoint require explicit site address and authentication; if the site address is incorrect, the request fails silently. Option A is wrong because HTTP requests can update items. Option C is wrong because the trigger context provides the user credentials, but the site address must be correct.

Option D is wrong because HTTP requests are available in Power Automate.

Automated flows start with a trigger like a new email or SharePoint item. Instant flows start manually with a button. Scheduled flows are also a type, but 'event-based' and 'manual' are the two categories; 'scheduled' is a separate type.

Webhook triggers exist but are a subtype of automated.

The trigger includes attachments, but if an email with 'Invoice' in the subject arrives without an attachment, the expression to access the first attachment fails because the attachments array is empty. The error 'InvalidTemplate' occurs when an expression cannot be evaluated. Option A is incorrect because the trigger is configured to include attachments.

Option C is incorrect because the folder path is valid. Option D is incorrect because the file name is taken from the attachment, not the subject.

The condition checks the status of the 'Send_approval_email' action, but the action only sends the email; it does not wait for the recipient to respond. The status 'Succeeded' simply means the email was sent, not that it was approved. To implement an approval, you should use the 'Start and wait for an approval' action.

Option B is incorrect because the condition syntax is correct. Option C is incorrect because the status is correctly referenced. Option D is incorrect because the email address is provided.

Option B is correct because the operationId is 'SendEmail' and the host connection is 'shared_office365', which corresponds to the Office 365 Outlook Send an email action. Option A is wrong because 'Post a message' would use a different operationId. Option C is wrong because 'Create event' would have different parameters.

Option D is wrong because 'Send an HTTP request' would use 'Http' connection type.

The correct answer is B because the most common cause of authentication failures in flows is expired or revoked credentials for the connected services. Option A is incorrect because licensing changes typically affect flow execution limits, not authentication. Option C is incorrect because API call limits cause throttling errors, not authentication errors.

Option D is incorrect because schema changes cause value mismatch errors, not authentication errors.

A scheduled cloud flow runs on a recurring schedule and can include actions to query SharePoint and send email. Automated flows trigger on events, not time. Desktop flows are for desktop automation.

Business process flows guide users.

Option D is correct because implementing retry logic with exponential backoff is a standard pattern for handling rate limiting. Option A is wrong because decreasing the timeout does not address the rate limit. Option B is wrong because ignoring the error could lead to data loss.

Option C is wrong because switching to a different connector might not be possible and does not solve the throttling issue.

Option A is correct because the most common misconfiguration is using the wrong webhook URL for the channel. Option B is incorrect because the trigger is working if the flow runs. Option C is incorrect because posting to Teams does not require special permissions beyond the connection.

Option D is incorrect because flow execution might not show detailed errors unless you open the run history.

Options A and C are correct because Configure Run After and Scope allow error handling. Option B is wrong because it's for actions. Option D is wrong because Conditions are for logic.

Option E is wrong because it's not for error handling.

Option D is correct because the 'When a new email arrives' trigger with 'Send push notification' action meets the requirement. Option A uses a schedule, not event-driven. Option B uses SharePoint trigger.

Option C uses approval, not notification.

Option D is correct because the flow's trigger filter may be set to only fire for specific severity levels, and critical alerts might be filtered out if the filter is misconfigured. Option A is wrong because the flow runs, so the trigger fires. Option B is wrong because the ServiceNow connection could be fine.

Option C is wrong because the alert creation is not the issue.

Option B is correct because a 403 error typically indicates insufficient permissions. Option A is wrong because throttling causes 429 errors. Option C is wrong because license issues cause 402 errors.

Option D is wrong because connector issues cause 400 or 500 errors.

A and D are correct. Standard connectors are available to all, and Premium connectors require additional licensing. B is incorrect because 'Enterprise' is not a connector tier.

C is incorrect because 'Custom' is a type of connector but not a licensing tier. E is incorrect because 'On-premises' describes data gateway, not a connector type.

Option B is correct because concurrency control allows parallel processing. Option A reduces scope but not necessarily performance. Option C is not a built-in feature.

Option D is for approval, not performance.

Option C is correct because the approval action requires the 'Approvals' connector to be properly configured. Option A is wrong because the flow owner's mailbox is not relevant to approval delivery. Option B is wrong because run history shows execution, not email delivery.

Option D is wrong because the recipient's mailbox is not directly configurable in the action.

Option A is correct because the action uses the 'SendEmailV2' operation with parameters for To, Subject, and Body. Option B is wrong because there is no attachment. Option C is wrong because it sends to one recipient.

Option D is wrong because no conditions are shown.

Options A, B, and D are correct. Automated (e.g., when an email arrives), Instant (e.g., button trigger), and Scheduled (e.g., recurrence) are the three main trigger types. Option C is wrong because 'Manual' is not a separate type; it's covered under Instant.

Option E is wrong because 'Business process flow' is a different feature in Power Automate, not a trigger type.

Option C is correct because implementing retry logic with exponential backoff is the standard approach to handle rate limiting. Option A is wrong because increasing concurrency would worsen the issue. Option B is wrong because it does not handle the rate limit.

Option D is wrong because 'Configure Run After' can handle failures but does not implement backoff.

Option B is correct because the trigger only processes emails from the last 7 days by default; older emails are ignored. Option A is wrong because the filter is on subject, not sender. Option C is wrong because the trigger works in shared mailboxes if configured.

Option D is wrong because the filter checks subject, not body.

Option C is correct because the error indicates the service principal or connection used by the flow lacks sufficient permissions. Option A is wrong because throttling would give a 429 error, not this specific message. Option B is wrong because the flow runs successfully initially.

Option D is wrong because user already existing would give a conflict error.

Option D is correct because the subjectFilter requires 'Invoice' in the subject. Option A is wrong because includeAttachments is false. Option B is wrong because onlyWithAttachments is false.

Option C is wrong because importance is 'Any'.

Option B is correct because the approval connector often requires a license with the appropriate rights. Option A is not the most likely since the manager is correctly listed. Option C is not a typical cause for delivery failure.

Option D is unrelated to delivery.

The SharePoint trigger 'When an item is created' must be set to trigger only on new items, not on changes. A common misconfiguration is setting the trigger to 'When an item is created or modified', which can cause missed triggers if the item is created and then quickly modified. Option A is incorrect because SharePoint triggers do not require a premium license for basic actions.

Option C is incorrect because permissions to the list do not affect the trigger's ability to fire. Option D is incorrect because the delay is unrelated to the trigger configuration.

Option C is correct because a parallel branch with a delay and a condition on the approval timeout can implement the requirement. Option A would change the entire timeout to 3 days, but the requirement is to auto-approve after 3 days, not reject. Option B does not allow customization of timeout behavior.

Option D would not trigger automatically after timeout.

Option A is correct because AI Builder's Form Processing model is designed for invoice extraction. Option B is wrong because it's for object detection. Option C is wrong because it's for text classification.

Option D is wrong because it's for entity extraction from plain text.

Option C is correct because the condition checks if amount > 5000; 6000 is greater, so the 'Send_approval' action runs. Option A is wrong because the flow does not check employeeId. Option B is wrong because the else branch won't run.

Option D is wrong because the trigger schema does not define managerEmail.

Option B is correct because the condition expression uses 'greater(triggerBody()?['score'], 0.8)' but if the 'score' property is a string (e.g., '0.9'), the comparison will fail because string comparison is different from numeric. The expression expects a number. Option A is wrong because the trigger is manual, not SharePoint.

Option C is wrong because the condition is correct syntactically. Option D is wrong because the condition uses 'greater' which is 'greater than'.

Options A and D are correct. Power Automate can send emails and create SharePoint items. Option B is wrong because building custom AI models is done with AI Builder.

Option C is wrong because designing Power BI reports is done in Power BI Desktop. Option E is wrong because managing user licenses is done in Microsoft 365 admin center.

Option C is correct because the 'When a new file is created' trigger for SharePoint is not available in solution-aware flows (it is a non-solution trigger). Option A is wrong because the OneDrive action is supported. Option B is wrong because the flow can be created outside a solution.

Option D is wrong because the warning indicates a limitation, not a full failure.

Option C is correct because checking run history shows the flow's status and any errors. Option A is wrong because recreating the flow is premature. Option B is wrong because the flow runs, so notifications are not disabled globally.

Option D is wrong because checking the schedule is not the first step when runs occur.