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
5 months agoFletcher
5 months agoCharlene
5 months agoGracia
5 months agoMozelle
5 months agoHoa
6 months agoChristene
6 months agoElli
6 months agoMona
6 months agoKarl
6 months agoCorinne
6 months agoSkye
10 months agoSylvia
11 months agoRose
10 months agoTrina
10 months agoIrene
10 months agoZack
11 months agoNan
9 months agoTomas
10 months agoMitzie
10 months agoFausto
11 months agoCorazon
10 months agoEdward
11 months agoJovita
11 months agoDierdre
12 months agoPamella
12 months ago