Microsoft Power Platform Solution Architect 온라인 연습
최종 업데이트 시간: 2026년02월14일
당신은 온라인 연습 문제를 통해 Microsoft PL-600 시험지식에 대해 자신이 어떻게 알고 있는지 파악한 후 시험 참가 신청 여부를 결정할 수 있다.
시험을 100% 합격하고 시험 준비 시간을 35% 절약하기를 바라며 PL-600 덤프 (최신 실제 시험 문제)를 사용 선택하여 현재 최신 47개의 시험 문제와 답을 포함하십시오.
정답:
Explanation:
A: How to View Auditing Log Details?
System administrators can see activities for the entities that are enabled for audit logging.
To view the audit logs:
✑ Go to Settings > System >Auditing.
✑ Choose Audit Summary View.
✑ Under Audit Summary View, you will see the list of audit entries

B: You can view details about solution operations from the Solutions area of Power Apps. An operation can be a solution import, export, or uninstall. The solution history displays information such as solution version, solution publisher, type of operation, operation start and end time, and operation status.
D: Trace log records are written to the PluginTraceLog Table. Writing of these records is controlled by the trace settings mentioned in Enable trace logging.
This data can be found in model-driven applications by navigating to Settings and choosing the Plug-in Trace Log tile.
Reference:
https://www.sherweb.com/blog/dynamics-365/audits-dynamics-365/
https://docs.microsoft.com/en-us/powerapps/developer/data-platform/logging-tracing

정답: 
Explanation:
Box 1: Increase multithreading and/or batch size settings
Box 2: Ensure you are loading data in a specific order.
Load the base tables in the hierarchies first.
정답:
Explanation:
A: With advanced data preparation available in Power Apps, you can create a collection of data called a dataflow, which you can then use to connect with business data from various sources, clean the data, transform it, and then load it to Microsoft Dataverse or your organization’s Azure Data Lake Gen2 storage account.
B: By combining conditions and actions, you can do any of the following with business rules:
✑ Set column values
✑ Clear column values
✑ Set column requirement levels
✑ Show or hide columns
✑ Enable or disable columns
✑ Validate data and show error messages
✑ Create business recommendations based on business intelligence.
C: Duplicate detection works by comparing generated match codes of existing records with each new record being created. These match codes are created as each new record is created. Therefore, there is potential for one or more duplicate records to be created if they are processed at the exact same moment. In addition to detecting duplicates as they are created, you should schedule duplicate detection jobs to check for other potential duplicate records.
Reference:
https://docs.microsoft.com/en-us/powerapps/maker/data-platform/data-platform-create-business-rule
https://docs.microsoft.com/en-us/powerapps/maker/data-platform/create-and-use-dataflows
https://docs.microsoft.com/en-us/powerapps/developer/data-platform/duplicaterule-entities
정답:
Explanation:
Dataverse includes a web application tool called Import Data Wizard. You use this tool to import data records from one or more comma-separated values (.csv), XML Spreadsheet 2003 (.xml), or text files.
Use transformation mapping to modify data before importing it. For example, split a full name that is contained in the source file into a first name and a last name to match the target columns for a table.
Note:
✑ To implement data import, you typically do the following:
✑ Create a comma-separated values (CSV), XML Spreadsheet 2003 (XMLSS), or text source file.
✑ Create a data map or use an existing data map.
✑ Create a comma-separated values (CSV), XML Spreadsheet 2003 (XMLSS), or text source file.
✑ Create a data map or use an existing data map.
✑ Associate an import file with a data map.
✑ Upload the content from a source file to the associated import file.
✑ Parse the import file.
✑ Transform the parsed data.
✑ Upload the transformed data into the target Dataverse server.
Reference:
https://docs.microsoft.com/en-us/powerapps/developer/data-platform/import-data
https://docs.microsoft.com/en-us/powerapps/developer/data-platform/add-transformation-mappings-import
정답:
Explanation:
With the position hierarchy security, a user at a higher position has access to the records owned by a lower position user or by the team that a user is a member of, and to the records that are directly shared to the user or the team that a user is a member of.
The hierarchy security model is an extension to the earlier security models that use business units, security roles, sharing, and teams. It can be used in conjunction with all other existing security models.
Reference:
https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/security-dev/
hierarchical-security-control-access-entities
정답:

정답: 
Explanation:
Box 1: Microsoft Power Automate, Microsoft Dataverse connector, and Microsoft 365 Outlook connector
Use Microsoft Dataverse as the data source.
While Power Automate is a robust tool with ever-expanding capabilities, it also handles simple tasks with grace. A universal business need for many organizations is the ability to automate email notifications based on certain criteria: an opportunity is won, send an email to the sales manager; a case is closed, send an email to the customer; a work order is completed, send an email to the customer.
Power Automate can easily accommodate this using the Microsoft 365 Outlook connector.
Box 2: Microsoft Power Automate, Power Bi data alerts, and Microsoft 365 connector Data alerts in the Power BI service: Set alerts to notify you when data in your dashboards changes beyond limits you set.
Box 3: Microsoft Power Automate, Power BI, Power Apps, and Microsoft Dataverse connector
Reference:
https://www.velosio.com/blog/2021/01/27/tracking-emails-the-right-way-with-power-automate/
https://docs.microsoft.com/en-us/power-bi/create-reports/service-set-data-alerts
정답:
Explanation:
B: Setting a column to Business Required means that the default behavior of a model-driven or canvas app will enforce this requirement in the app.
C: With alternate keys you can now define a column in a Dataverse table to correspond to a unique identifier (or unique combination of columns) used by the external data store. This alternate key can be used to uniquely identify a record in Dataverse in place of the primary key. You must be able to define which columns represent a unique identity for your records. Once you identify the columns that are unique to the table, you can declare them as alternate keys through the customization user interface (UI) or in the code.
Reference:
https://docs.microsoft.com/en-us/powerapps/maker/data-platform/create-edit-field-portal
https://docs.microsoft.com/en-us/powerapps/developer/data-platform/define-alternate-keys-entity

정답: 
Explanation:
Box 1: Data loss prevention policy
Data loss prevention (DLP) policies enforce rules for which connectors can be used together by classifying connectors as either Business or Non-Business. If you put a connector in the Business group, it can only be used with other connectors from that group in any given app or flow. Sometimes you might want to block the usage of certain connectors altogether by classifying them as Blocked.
Box 2: Security group
If your company has multiple Microsoft Dataverse environments, you can use security groups to control which licensed users can be a member of a particular environment.
Reference:
https://docs.microsoft.com/en-us/power-platform/admin/wp-data-loss-prevention
https://docs.microsoft.com/en-us/power-platform/admin/control-user-access

정답: 
Explanation:
Reference: Box 1: One-to-many relationship
Each educator can have 0, 1, or many qualifications
Box 2: One-to-many relationship
Each educator can be the primary educator for 0, 1 or many cources.
Box 3: Many-to-many relationship that uses a custom table.
Note: N:N (Many-to-Many): A table relationship that depends on a special Relationship table, sometimes called an Intersect table, so that many rows of one table can be related to many rows of another table.
Reference: https://docs.microsoft.com/en-us/powerapps/maker/data-platform/create-edit-entity-relationships

정답: 
Explanation:
Box 1: Contact
With Contact scope, a signed-in user in the role for which the permission record is defined will have the rights granted by that permission only for records that are related to that user's contact record via a defined relationship.
Box 2: Account
With Account Scope, a signed-in user in the role for which the permission record is defined will have the rights granted by that permission only for records that are related to that user's parent account record via a defined relationship.
This scope means that the entity list will only show the records of the selected entity that are associated to the user's parent account. For example, if an entity permission allows Read access to Lead entity with the Account scope, the user having this permission can view all the leads of only the parent account of the user.
Incorrect Answers:
Self Scope allows you to define the rights a user has to their own Contact (Identity) record. Users can use entity forms or web forms to make changes to their own Contact record linked with their profile.
Parental scope: In this most complex case, permissions are granted for an entity that is a relationship away from an entity for which an Entity Permission record has already been defined. This permission is actually a child record of the parent entity permission.
Reference: https://docs.microsoft.com/en-us/powerapps/maker/portals/configure/assign-entity-permissions

정답:
Explanation:
Need a relationship table.
N:N (Many-to-Many): A table relationship that depends on a special Relationship table, sometimes called an Intersect table, so that many rows of one table can be related to many rows of another table.
When viewing rows of either table in a N:N relationship you can see a list of any rows of the other table that are related to it.
Reference: https://docs.microsoft.com/en-us/powerapps/maker/data-platform/create-edit-entity-relationships
정답:
Explanation:
Import data that's stored somewhere else into your model-drvien app using the import feature in Power Apps.
Every table has required columns that must exist in your input file. It's recommended that you download an Excel template, add your data, and then import the file to your app. The template saves time and effort. Don't add or modify columns in the template to avoid issues during the import.
Note:
Step 1: Download an Excel template
To avoid mapping issue, it's recommended that you use an Excel template that you can download from your app. Once the template is downloaded add your data and then import the file back to your app.
Remember don't add or modify columns in the template to avoid issues during the import process.
Step 2: Import your data
Use the template that you downloaded in the previous step (modified with your data) and import the file to your app.
Reference: https://docs.microsoft.com/en-us/powerapps/user/import-data

정답: 
Explanation:
Box 1: Assign only Create rights to activities
You require the same set of Dataverse privileges and access rights to work with custom activities as those required to work with custom entities.
Task-based privileges, at the bottom of the form, give a user privileges to perform specific tasks, such as publish articles.
Box 2: Assign User-level assign rights to human resources case table. Record-level privileges define which tasks a user with access to the record can do, such as Read, Create, Delete, Write, Assign, Share, Append, and Append To.
For user and team owned records, the access level choices for most privileges are tiered Organization, Business Unit, Business Unit and Child Business Unit or only the user’s own records. That means for read privilege on contact, I could set user owned, and the user would only see their own records.
Incorrect Answers:
For security purposes, records that are organization owned, the only access level choices is either the user can do the operation or can’t.
Reference:
https://docs.microsoft.com/en-us/power-platform/admin/security-roles-privileges
https://docs.microsoft.com/en-us/power-platform/admin/wp-security-cds
정답:
Explanation:
Reference:
https://docs.microsoft.com/en-us/powerapps/maker/portals/portal-templates
https://docs.microsoft.com/en-us/dynamics365/customer-service/embed-chat-widget-portal