Microsoft Certified Power Platform Functional Consultant Associate · Free Practice Question Medium
Question 16
Different Power Automate PowerShell cmdlets help provide administrators with visibility into how app makers are using Power Automate.
What does the Get-AdminPowerAppConnector cmdlet do?
-
A
Administrators can retrieve all custom connectors that have been deployed in the tenant.
-
B
Administrators can retrieve all environments that have been created within the tenant. The returned information will also include the name of the person who created the environment, when it was created, and its location.
-
C
Administrators can retrieve all connection permissions for Power Apps and Power Automate. The returned data includes whether the connection belongs to an owner or if the connection has been shared with another user.
-
D
Lists all flows that exist within the tenant. The returned information includes when the flow was created, who created it, and the environment that it was created in.
-
E
Administrators can retrieve all environments that have been created within the tenant. The returned information will also include the name of the person who created the environment when it was created, and you can provide a parameter of -Default that will result in only the default environment being returned.
Reveal correct answer
Correct answer: A
Explanation
Different Power Automate PowerShell cmdlets help provide administrators with visibility into how app makers are using Power Automate.
The different cmdlets that you can use are listed below.
Read connection permissions
In the read connection permissions (Get-AdminPowerAppConnectionRoleAssignment) cmdlet, administrators can retrieve all connection permissions for Power Apps and Power Automate. The returned data includes whether the connection belongs to an owner or if the connection has been shared with another user.
Read and delete custom connectors
In the read and delete custom connectors (Get-AdminPowerAppConnector) cmdlet, administrators can retrieve all custom connectors that have been deployed in the tenant.
Read environments
In the read environments (Get-FlowEnvironment) cmdlet, administrators can retrieve all environments that have been created within the tenant. The returned information will also include the name of the person who created the environment, when it was created, and its location.
Read default environment
The read default environment (Get-FlowEnvironment -Default) cmdlet is one that has already been discussed, but the difference, in this case, is that you can provide a parameter of -Default that will result in only the default environment being returned.
List all flows in tenant
The list of all flows in the tenant (Get-AdminFlow) cmdlet will list all flows that exist within the tenant. The returned information includes when the flow was created, who created it, and the environment that it was created in.
If you want to export this information in CSV format, you can use the following command, which will write this information to a file.
Get-AdminFlow | Export-Csv -Path '.\FlowExport.csv'
Because the output of PowerShell cmdlet is a CSV file, you can load the results into a business intelligence tool, like Power BI or Microsoft Excel, where you can further analyze the results.
A. The Get-AdminPowerAppConnector cmdlet allows administrators to retrieve all custom connectors that have been deployed in the tenant. This information is valuable for monitoring and managing custom connectors used by app makers in Power Automate.
B. This choice is incorrect as it describes the functionality of retrieving all environments created within the tenant, not custom connectors. The Get-AdminPowerAppConnector cmdlet specifically focuses on custom connectors, not environments.
C. This choice is incorrect as it describes the functionality of retrieving connection permissions for Power Apps and Power Automate, not custom connectors. The Get-AdminPowerAppConnector cmdlet is specifically used for managing custom connectors in Power Automate, not connection permissions.
D. This choice is incorrect as it describes the functionality of listing all flows within the tenant, not custom connectors. The Get-AdminPowerAppConnector cmdlet is specifically used for managing custom connectors in Power Automate, not flows.
E. This choice is incorrect as it describes the functionality of retrieving all environments created within the tenant, not custom connectors. The Get-AdminPowerAppConnector cmdlet is specifically used for managing custom connectors in Power Automate, not environments.
Discussion
Think the marked answer is wrong, or have a better explanation? Share it below — comments appear after review.
