PL-200 · Question #88
Case Study 1 - Alpine SKi House Background Alpine SKi House is a boutique mountain resort that offers year-round spa and outdoor activities such as snow sports, hiking, mountain biking, and more…
The correct answer is C. Embed the invitation code in the email link URL. The correct approach is to embed the invitation code directly in the email link URL as a query string parameter. When the customer clicks the link, the portal reads the code from the URL automatically, eliminating manual entry entirely. Option A (defaulting the code after…
Question
Options
- ADefault the invitation code from the email upon logging into the portal
- BAuto-populate the invitation code field on the sign in screen from the email link
- CEmbed the invitation code in the email link URL
- DSend the customer their username and temporary password in the email link
How the community answered
(17 responses)- B12% (2)
- C82% (14)
- D6% (1)
Explanation
The correct approach is to embed the invitation code directly in the email link URL as a query string parameter. When the customer clicks the link, the portal reads the code from the URL automatically, eliminating manual entry entirely. Option A (defaulting the code after login) is too late in the flow - the code is needed before or at login. Option B (auto-populating a field on the sign-in screen) could work but requires the code to already be in the URL to read from; embedding it in the URL (C) is the mechanism that enables this. Option D (sending username and temporary password) addresses authentication credentials, not the invitation code workflow. Embedding the code in the URL is the standard, seamless pattern for portal invitation redemption in Power Pages/Dynamics portals.
Topics
Community Discussion
No community discussion yet for this question.