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