CCNA Demonstrate the capabilities of Power Automate Questions

The correct answers are A and D. Configure Run After settings allow you to specify actions that run on failure, timeout, or skip, enabling error handling. Scope actions group actions and allow you to configure error handling at the scope level, including running subsequent actions on failure.

Option B (Apply to each) is for iterating over lists, not error handling. Option C (Compose) is for creating data, not error handling. Option E (Condition) is for branching logic, not error handling.

A cloud flow (automated) is the correct choice because it triggers on an event (new email) and can integrate with SharePoint. Desktop flows are for legacy desktop automation. Business process flows guide users through steps.

An approval flow is for approvals.

The trigger is configured for file creation in the 'Incoming' folder with a condition that checks the file extension is .xlsx, so it only fires when an Excel file is created. Option A is wrong because the trigger filters for .xlsx files, not .csv files. Option B is wrong because the trigger does not fire for any file; it only fires for .xlsx files.

Option C is wrong because the trigger is for file creation, not modification.

A solution-aware flow can be packaged and deployed to a dedicated environment with DLP policies, and a managed identity (now service principal) provides secure authentication. Option A is incorrect because instant flows are manually triggered, not triggered by data changes. Option B is incorrect because the 'When a row is modified' trigger does not use service principal; it uses the owner's credentials.

Option C is incorrect because automated flows can be triggered by Dataverse changes, but the 'Run only for the flow owner' setting does not use managed identity.

The approval step fails because the 'Start and wait for an approval' action requires the 'Attachments' parameter to be populated with the file content. Without it, no attachment is sent, even if the file is referenced elsewhere. Option A is incorrect because the issue is not about licensing; standard connectors support attachments.

Option B is incorrect because there is no 10 MB limit for standard approvals; the file size limit is higher and not the cause here. Option C is incorrect because SharePoint connectors can access PDF files.

'When a new email arrives' trigger initiates the flow for each incoming email, and the 'Create file' action can save attachments to a OneDrive folder. Option B is incorrect because 'Send an email' action would send an email, not create a file. Option C is incorrect because 'When an item is created' trigger is for SharePoint or similar, not for email.

Option D is incorrect because 'When a file is created' trigger and 'Start an approval' action do not relate to copying email attachments.

SharePoint does not allow certain characters in file names, including the colon (:). When a file name contains a colon, the flow fails because SharePoint cannot create or copy the file with that character. Option C is incorrect because the connector is not the issue; the problem is the invalid character.

Option B is not typical for this specific error, and Option D is unrelated.

'Start and wait for an approval' pauses the flow until a decision is made, and a 'Condition' action can check the outcome (e.g., 'Approve' or 'Reject') to notify the salesperson or stop processing. Option A is wrong because 'Scope' is used to group actions and does not provide approval functionality. Option B is wrong because 'Start an approval' does not wait, so the flow continues immediately without waiting for a response.

Option D is wrong because 'Terminate' ends the flow but cannot check the approval outcome and handle the rejected scenario appropriately.

Options B, D, and E are correct. A trigger starts the flow, actions perform tasks, and conditions control the flow logic. Option A (Environment) is the container for resources, not a component of a single flow definition.

Option C (Connector) is a connection to a service, not a component of the flow itself.

Options A and C are correct. Instant triggers (A) are started manually by a user, while Automated triggers (C) respond to events such as an email arriving or a file being created. Option B (Event) is not a valid trigger type; Power Automate uses 'Scheduled' or 'Automated' for event-based flows.

Option D (Manual) is not a distinct trigger type—it is a subtype of Instant. Option E (Calendar) is not a trigger type; scheduling is done via 'Scheduled' triggers.

The SharePoint trigger in Power Automate uses a polling interval; when the flow is enabled, it may not immediately capture items created before the first poll completes. This is a common cause of missing recent items. Option A is incorrect because utcNow() is evaluated dynamically at each poll, not static.

Option C is incorrect because there is no evidence the $filter expression is invalid. Option D is incorrect because the site ID is typically correct if the flow connects successfully.

The correct answers are B and E. Dataverse provides triggers such as 'When a row is added, modified, or deleted' (option B) and 'When a row is added' (option E). These triggers initiate flows based on changes to rows in a Dataverse table.

Options A and C are incorrect because they are triggers for Outlook and SharePoint respectively, not Dataverse. Option D is a manual trigger, not a Dataverse trigger.

The 'Compose' action can be used to sanitize file names by replacing special characters. Option A is wrong because 'Apply to each' iterates over items but does not modify names. Option B is wrong because 'Condition' checks conditions but does not transform data.

Option D is wrong because 'Scope' groups actions but does not handle errors.

The correct trigger is 'When a user is created' from the Microsoft Entra ID connector (formerly Azure AD). This trigger initiates a flow when a new user object is created in Microsoft Entra ID, which is ideal for sending a welcome email. Option A is incorrect because it triggers on incoming emails, not on user creation.

Option B is for record creation in Dataverse, not for Microsoft Entra ID users. Option C is for file creation in SharePoint, not relevant to user provisioning.

Configuring the email action's 'Run after' settings to retry on failure and then escalate to a secondary manager is the best practice. This handles the transient error (full mailbox) by retrying, and if it still fails, it escalates to a secondary manager, ensuring the notification is delivered. Option A is wrong because terminating on error does not handle the full mailbox scenario.

Option B is wrong because it only alerts an admin but does not resolve the need to notify the manager. Option D is impractical as Power Automate cannot easily check mailbox size before sending.

The 'When an item is created' trigger is bound to the original site URL and list ID. Moving the list to a different site does not automatically update the trigger's connection, so the flow continues to listen for changes on the old location and fails to trigger for the new one. Option B is incorrect because the trigger can work across sites if updated; the issue is the stale reference.

Option C is incorrect because the flow is not automatically disabled during the move. Option D is incorrect because re-authentication is not related to the change in location.

The correct first check because the most common reason files don't appear after a successful flow run is that the SharePoint connection lacks write permissions to the target library. Option A is incorrect because special characters are not the primary issue here. Option B is not relevant as the flow already runs successfully.

Option C is not the first step; checking run history can be done after verifying permissions.

Service principal certificates have expiration dates. When the certificate expires, authentication fails with a '401 Unauthorized' error. Option A is incorrect because a wrong connection string would produce a different error (e.g., 'Cannot connect to SQL Server').

Option B is irrelevant as the environment does not affect authentication. Option C is incorrect because rate limits cause '429 Too Many Requests', not 401.

The 'Run only user' setting in a flow's trigger captures the context of the user who triggered the flow, enabling audit trails. Option A is wrong because the 'When an item is created' trigger does not log the initiator by default. Option B is wrong because 'Configure Run After' settings are for error handling, not for capturing user identity.

Option C is wrong because the 'Start and wait for an approval' action does not include the trigger context beyond its own inputs.

Options A, D, and E are correct. For a Power Automate flow to use the 'When an email arrives' trigger for a shared mailbox, the flow must use an Office 365 Outlook connector (A), the connection must be configured with the shared mailbox address (D), and the shared mailbox must be enabled for the connector (E). Option B is incorrect because desktop flows are not required; cloud flows can use this trigger.

Option C is incorrect because the trigger fires for any email, not just those with attachments.

Options B and E are correct. A 'Condition' action filters by sender, and 'Create a task' action creates the task in Microsoft To Do. Option A is wrong because 'Compose' is used for data manipulation, not for filtering or task creation.

Option C is wrong because 'Send an email' is not needed. Option D is wrong because 'Apply to each' is used for arrays, not for filtering by sender.

The 'Recurrence' trigger allows you to schedule flows to run at specific intervals, such as every Monday at 9 AM. Option A is incorrect because a Power Apps button trigger requires a manual action from a user in a Power App, not automation. Option B is incorrect because 'When a row is added, modified or deleted' triggers on data changes in a data source, not on a schedule.

Option C is incorrect because 'When a new email arrives' triggers on incoming emails, not a time-based schedule.

An automated trigger in Power Automate starts a flow automatically when a specific event occurs, such as a new tweet matching a keyword. Option A is incorrect because a recurrence trigger runs on a schedule, not in response to an event. Option B is incorrect because a manual trigger requires user action to start the flow.

Option D is incorrect because a scheduled trigger is another name for a recurrence trigger, which runs at specified times.

Sharing the flow with specific users (HR managers) and assigning them Owner permissions is the standard method to restrict access in Power Automate. Option A is wrong because separate environments don't restrict access by role; they isolate resources but permissions must still be set. Option B is wrong because DLP policies control data connectivity, not flow ownership or access.

Option D is wrong because disabling sharing affects all flows but doesn't grant specific access to HR managers.

The most likely reason is that the $filter parameter is not supported by the trigger type. In Power Automate, the 'When a new email arrives' trigger for Office 365 Outlook uses server-side filtering via OData $filter. However, the 'hasAttachments' property is not a valid filtering property for the Mail API, so the filter is ignored.

Instead, use an action to check for attachments after the trigger fires.

Scheduled flows are designed to run on a recurring schedule, such as daily or weekly, without requiring a trigger event. Option B requires a daily report to be generated at a fixed time (8 AM), which is a classic scheduled flow use case. Option C requires archiving records every Sunday, another recurring schedule.

Both scenarios rely on time-based triggers, not event-driven triggers.

The 'Forbidden' error indicates that the flow cannot access the Google Sheets spreadsheet due to authentication failure. The most likely cause is that the Google Sheets connection is not authenticated or the token has expired. Option B correctly identifies this issue.

Option A is less likely because Microsoft Entra ID tokens are used for Microsoft services, not Google Sheets. Option C is irrelevant because the trigger is from Google Sheets, not SharePoint. Option D would cause a different error at the Dynamics 365 action step, not at the trigger.

The Teams connector requires proper authentication and permissions; if the connection is broken or insufficient, messages will fail to post. Option A is incorrect because the 'Post a message' action configuration is not the first thing to check; the trigger and connection status are more fundamental. Option C is incorrect because the flow triggering on new lead creation is a separate issue from the Teams connector itself.

Option D is incorrect because Teams notification settings are per-user and not the primary cause of the flow not sending messages.

The on-premises data gateway is required to connect to a local network drive from a cloud flow. Power Automate cloud flows run in the cloud and cannot directly access on-premises file systems without a gateway. Option B is wrong because cloud flows with a SharePoint connector can only connect to SharePoint Online, not to a local drive.

Option C is wrong because UI flows are for automating user interface interactions, not file transfers. Option D is wrong because business process flows provide guided step-by-step processes and are not for file automation.

Using parallel branches allows each independent action (send welcome email, create user accounts, assign licenses) to run concurrently. If one branch fails, the others continue unaffected, ensuring high reliability. Option A is incorrect because sequential actions in a single branch stop the entire flow if any action fails.

Option B is incorrect because a scope timeout only limits execution time, not isolate failures. Option C is incorrect because a condition evaluates a decision but does not provide parallel execution or failure isolation.

Power Automate has a file size limit (default 100 MB) for actions like 'Get file content'. Large video files often exceed this limit, causing failures. Option A is incorrect because the SharePoint connector can read video files; file type is not the issue.

Option B is incorrect because parallel branches are unrelated to file size limits. Option D is incorrect because Azure Blob Storage supports large files, including videos.

A trigger starts the flow when an event occurs, such as a new file being added. Option A is a condition, which is a logic step, not a trigger. Option C is a connector, which is a service connection, not a trigger.

Option D is an action, which is a step that performs an operation, not a trigger.

The flow's schedule is correctly configured, but the flow may have been manually turned off in the Power Automate portal, preventing it from executing. Option A is incorrect because the recurrence setting appears valid. Option C is incorrect because an invalid SharePoint URL would cause the flow to fail when triggered, not prevent it from being scheduled.

Option D is incorrect because flows do not have a 'Stopped' state; they are either turned on or off.

If the email body uses a dynamic content token that is not mapped correctly, the flow will output the token name as placeholder text. Option A is wrong because the trigger is working (flow runs). Option B is wrong because the email is sent successfully.

Option D is wrong because there is no mention of permissions.

The 'Send an email' action in Power Automate requires a connection to an email server; if the connection uses a shared mailbox or a service account, and that mailbox's credentials expire or the mailbox is deactivated, the flow will appear to succeed but the email will not be delivered. Option B is incorrect because if the email goes to spam, the flow would still show success. Option C is incorrect because the trigger is working.

Option D is incorrect because the donor table is populated, so the flow runs.

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.

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

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

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.

The flow lacks an approval action; it only sends an email notification. To implement an approval process, a 'Start and wait for an approval' action must be included. Option A is wrong because the 'When an HTTP request is received' trigger can be used for manual or external triggers.

Option B is wrong because email actions in Power Automate authenticate via the connection, not explicit authentication parameters. Option D is wrong because the 'Send an email' action supports required parameters like To, Subject, and Body, which are not deprecated.

A cloud flow with an approval action (commonly called an approval flow) is designed to incorporate human approval steps in an automated process. Option A (Automated cloud flow) is triggered automatically without any manual intervention, so it does not fit the requirement for human interaction. Option B (Business process flow) provides a guided experience for users to follow a standard process but does not handle approvals.

Option C (Desktop flow) automates tasks on the desktop (RPA) and is not intended for approval workflows.

An instant flow (also known as a button flow) is triggered manually by a user, such as by clicking a button in a mobile app. Option B (business process flow) is a guided process, not a manual trigger. Option C (scheduled flow) runs on a predefined schedule.

Option D (automated flow) is triggered automatically by events like email arrival or file creation, not by user interaction.