An airline loyalty desk changes a passenger's tier in its Dynamics 365 sales app and must see that tier on the open service case. Which test should the architect require?
Select an answer to reveal the explanation.
Short Explanation
A relay counts only if the baton arrives in the next runner's hand. You need a test that changes the tier in the sales app and then reads that tier on the open service case. A clean save on the sales form can still leave the desk looking at yesterday.
Full Explanation
An end-to-end test is the right gate when one business fact is written in one Dynamics 365 app and read in another. The sales app is where the tier changes, and the service case is where the loyalty desk reads it, so the test has to perform that change and then open the case and confirm the same tier. A sales-form test that saves the tier and stops before the case can pass while the desk still shows the previous tier. A service-only test that types a tier onto the case proves the form accepts text, not that it displays the value the sales app just saved. A nightly compare of exported files does not open the case the desk uses, and it can pass on a copy that is already stale. Exam caveat: sharing a customer record is what makes the handoff possible, and it does not replace running the scenario. Two apps on one platform still need a test that crosses them. Operational check: in a non-production company, change one passenger's tier in the sales app, open that passenger's service case, and confirm the case shows the new tier before the desk relies on it.