You create a Power App portal. When a user signs into the portal the following error displays: User not found You confirm that the user's sign in information is correct. You need to determine the cause of the error. What should you do?
Agreed. It states you need to determine the cause of the error. If you disable the custom error message, it will display the full error message and therefore allow you to determine the cause of the error.
Agrred.
Disabling custom errors should be a temporary setting because the detailed error message might convey an increased negative experience for portal visitors. We recommend that you only disable custom errors when you are in the development phase and enable custom errors after you go live.
C. Enable diagnostic tools in Lifecycle Services.
This will allow you to gather more information about the error and determine the cause of the issue. Enabling diagnostic tools will allow you to review log files, trace information, and other diagnostic data that can assist in troubleshooting the problem. Additionally, you can also check the portal settings and ensure that the user's account is properly configured to have access to the portal.
Explanation:
Custom Error Messages: Disabling or enabling custom error messages affects how errors are displayed to the user but doesn’t help in identifying the root cause of an issue like "User not found." Custom error messages are more about user experience.
Diagnostic Tools: Enabling diagnostic logging or tools helps capture detailed logs that can provide insights into why the error is occurring. This is essential for troubleshooting authentication issues or identifying misconfigurations.
If you have any doubts, it’s important to consider the intent behind the action:
Custom error messages: Improve the user experience with friendly messages.
Diagnostic logging: Gain insights into the actual problem to fix it.
I feel A is the corect answer.
"If any server-side exception occurs on your website, a customized error page with a user-friendly error message is shown by default. To configure the error message, see Display a custom error message.
However, it's better to see the ASP.NET detailed error page, also known as Yellow Screen of Death (YSOD), for debugging purposes. The detailed error page helps you to get the full stack of server errors."
https://learn.microsoft.com/en-us/power-pages/admin/view-portal-error-log
Also the question talks about creating a Power App Portals. Isnt Lifecycle Services related to Dynamics Finance & Operations
A isn't correct. The questions is asking 'You need to determine the cause of the error.'. A is a temporary solution and cannot help identify the reason behind the error.
It does help identify the issue:
"In the Power Pages admin center, the Disable custom errors action replaces the notification with detailed error information on the website page that could provide extra information for an administrator to troubleshoot the issue."
n the Power Pages admin center, the Disable custom errors action replaces the notification with detailed error information on the website page that could provide extra information for an administrator to troubleshoot the issue.
Enabling diagnostic tools in Lifecycle Services can provide detailed logs and insights into the error that is occurring and help to determine the root cause of the issue.
A is the most likely answer considering this is a FUNDAMENTALS exam and it is specifically listed in the MS Learn content.
If this was a Dynamics fundamentals then I would consider the Lifecycle answer, however this feature is now depreciated in LCS.
https://learn.microsoft.com/en-us/training/modules/portals-maintenance-troubleshooting/1-introduction
Disabling custom error messages will elucidate more info as to why there is an error so it would. Not advised in live environments though, so C more preferred regardless.
C. Diagnostic tools in Lifecycle Services will log details why the user is not able to sign in successfully. Disabling custom error messages in a production environment is not only discouraged but can cause confusion
Disabling custom errors should NEVER be done in production. It is considered a very bad practice and should only be done in development environment.
This problem is typically analyzed using telemetry data generated from LifeCycle Services (LCS).
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/lifecycle-services/monitoring-diagnostics
Also Audit log provides data to analyze the sing-ins:
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/lifecycle-services/user-logins
Just reviewed the link https://docs.microsoft.com/en-us/learn/modules/portals-maintenance-troubleshooting/1-introduction
It is saying that Disable Custom Error Message should be used during development phase. While the question seems asking for LIVE environment. For this it seems that the given answer (C) would be appropriate. Please suggest.
C might be correct, since "after the launch of Power Apps portals on October 1, 2019, all Dynamics 365 Portals are now referred to as Power Apps portals." so literally Lifecycle service can also be used here.
This section is not available anymore. Please use the main Exam Page.PL-900 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Loredana
Highly Voted 4 years, 5 months agoAunehwet79
3 years, 6 months agoSh4z
4 years, 4 months agoShradz93
3 years, 5 months agoEdrisKazemi
Highly Voted 2 years, 3 months agorestlessrat
6 months, 4 weeks agoKraken84
1 year, 8 months agohm0167968
Most Recent 8 months, 2 weeks agoPanda01
1 year, 5 months agoMayaYao
1 year, 10 months agoManiula
1 year, 10 months agoMurtuza
1 year, 11 months agoPhil12345
1 year, 11 months agokty
2 years agoKraken84
1 year, 8 months agobeep123
1 year, 5 months agoEltooth
2 years, 5 months agoClaraM
2 years, 6 months agocodheads
2 years, 6 months agoLibertoo
2 years, 8 months agonanochuan
2 years, 8 months agoDeVries
2 years, 9 months agoD3COD3R
2 years, 9 months agoJainS
2 years, 11 months agoGaurav2096
3 years agoDoubi
3 years, 1 month agoPari2612
3 years, 2 months ago