I practiced a similar question, and I think option A could also be a contender since creating different case types might imply different functionalities for users and CSRs.
Okay, I think I've got this. The key is to look at the type parameter for the PriceChecker class. Option D seems to be the most specific and correct answer, since it uses the Plushy type that extends the Products class.
Haha, option D is a classic 'all of the above' trap. Of course the mobile app should support all major operating systems, but that doesn't require distinct channels.
I'm not sure about that. Couldn't the app just have a settings menu where users can adjust the currency and time format themselves? Seems like that could be done without separate channels.
Option C seems like the most logical choice here. Customizing the mobile app experience based on user location is a distinct requirement that would likely require separate mobile app channels.
Wilda
4 months agoFletcher
4 months agoCharlene
4 months agoGracia
4 months agoMozelle
4 months agoHoa
5 months agoChristene
5 months agoElli
5 months agoMona
5 months agoKarl
5 months agoCorinne
5 months agoSkye
9 months agoSylvia
10 months agoRose
9 months agoTrina
9 months agoIrene
9 months agoZack
10 months agoNan
8 months agoTomas
9 months agoMitzie
9 months agoFausto
10 months agoCorazon
9 months agoEdward
10 months agoJovita
10 months agoDierdre
11 months agoPamella
11 months ago