PL-100 · Question #337
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might…
The correct answer is B. No. Answering "No" implies the proposed solution fails to address the column length issue in a managed solution context, likely due to violating solution management best practices or organizational constraints like direct modification in production.
Question
Options
- AYes
- BNo
How the community answered
(43 responses)- A16% (7)
- B84% (36)
Why each option
Answering "No" implies the proposed solution fails to address the column length issue in a managed solution context, likely due to violating solution management best practices or organizational constraints like direct modification in production.
Answering "Yes" would indicate that the proposed solution effectively resolves the column length issue and allows users to enter full values, which would contradict the correct answer being "No".
The "No" answer suggests the proposed solution, which is not provided, either attempts to directly modify components of a managed solution in the production environment (which is generally prevented or unsupported for managed solutions), or involves creating new unmanaged components in production, both of which are inappropriate and would not achieve the goal reliably or without violating the stated organizational policy.
Concept tested: Dataverse managed solution update restrictions
Source: https://learn.microsoft.com/en-us/power-apps/developer/data-platform/managed-solutions#update-a-managed-solution
Topics
Community Discussion
No community discussion yet for this question.