PL-600 flashcards
PL-600 · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Fit-gap analysis
- A structured comparison of business requirements against out-of-the-box platform capabilities that classifies each requirement as standard configuration, custom extension, or a gap requiring a workaround or scope change.
- Functional requirement
- A statement describing a specific behavior, task, or output the solution must deliver, such as approving an invoice or generating a report.
- Nonfunctional requirement
- A quality attribute the solution must satisfy, such as performance, availability, scalability, security, usability, or regulatory compliance, rather than a specific behavior.
- Solution blueprint
- A design document that describes the proposed apps, automation, data model, integrations, security model, ALM approach, environments, and licensing for a Power Platform solution.
- RACI matrix
- A responsibility assignment chart that identifies who is Responsible, Accountable, Consulted, and Informed for each task, decision, or workstream in a project.
- Minimum viable product
- The smallest scope that delivers meaningful business value and can be released to validate assumptions before investing in lower-priority requirements.
- Requirement traceability matrix
- A table that links each requirement to its design component, test case, and status so teams can verify complete coverage and detect scope gaps.
- Power Platform Well-Architected
- A framework with five pillars: Reliability, Security, Operational Excellence, Performance Efficiency, and Experience Optimization, used to review solution quality and trade-offs.
- Business case
- A justification document comparing expected benefits, costs, risks, and timeline of a proposed solution to support a go or no-go investment decision.
- Data migration assessment
- An analysis of source data quality, volume, mapping, and cleansing needs that determines effort and approach for moving data into Dataverse.
- Success criteria
- Measurable outcomes agreed with stakeholders that define what a successful solution must achieve and serve as the baseline for acceptance testing.
- Business unit
- A Dataverse security boundary that controls record ownership; users can generally access records owned by their business unit unless sharing or hierarchy settings extend access.
- Security role
- A set of privileges and access levels assigned to users or teams that determines which tables and operations they can use and at what scope.
- Column security
- A field-level control that restricts read, update, or create access to specific Dataverse columns for selected users or teams, independent of table-level privileges.
- Hierarchy security
- A model that grants managers visibility into records owned by their subordinates through manager or position hierarchies, supplementing business unit and role security.
- Managed solution
- A packaged solution installed in an environment that is locked from direct editing and supports clean upgrade, patch, and uninstall lifecycle operations.
- Environment strategy
- A plan defining which Power Platform environments exist, their purpose, region, security, and promotion path from development through test to production.
- Delegation
- The ability of Power Apps to translate filtering and sorting operations into queries executed by the data source, returning complete results from large tables.
- Connection reference
- A solution component that points to a connector and lets makers bind apps or flows to a connection at deployment time instead of hard-coding credentials.
- Environment variable
- A solution component that stores configuration values such as URLs, IDs, or feature flags so the same solution can behave differently per environment.
- Virtual table
- A Dataverse table whose data remains in an external system and is surfaced through a provider, allowing apps to read or write external records without copying data.
- Dual-write
- A near-real-time integration that synchronizes Dataverse records with finance and operations apps so data stays consistent across both systems.
- DLP policy
- A tenant or environment policy that classifies connectors into Business, Non-business, or Blocked groups and prevents incompatible connectors from being combined in one app or flow.
- Managed environment
- An environment setting that adds governance features such as sharing limits, solution checker enforcement, deployment pipelines, and weekly admin digests.
- Solution checker
- A static analysis tool that reviews solution components against performance, security, and maintainability rules and reports issues by severity before deployment.
- Deployment pipeline
- An automated process that promotes a solution through predefined environments, running validation and import steps with minimal manual intervention.
- Power Platform CLI
- A command-line interface used to authenticate, export and import solutions, manage environments, and script ALM tasks in build automation.
- Deployment settings file
- A JSON file that supplies connection references and environment variable values during solution import so automated deployments do not prompt for configuration.
- Dataverse auditing
- A feature that records create, update, and delete actions on audited tables and columns, supporting compliance and troubleshooting investigations.
- Application Insights
- An Azure monitoring service that can receive telemetry from Power Apps and Power Automate to track usage, errors, and performance.
- Point-in-time restore
- A Dataverse capability that restores an environment to a prior moment within the retention window, used to recover from data corruption or failed deployments.
- User acceptance testing
- A validation phase where business users execute real scenarios against the solution to confirm it meets agreed requirements before go-live.