Q: 7
A review of an organization’s IT portfolio revealed several applications that are not in use.
The BEST way to prevent this situation from recurring would be to implement.
Options
Discussion
D . Asset life cycle management isn't just about what gets bought, it's about reviewing, maintaining, and retiring applications too. That covers unused apps hanging around. Pretty sure that's what the question targets.
I don’t think it’s D. I picked B since business case development should stop people from buying stuff they don’t really need in the first place. Seems like if you have that up front, you avoid shelfware entirely. Maybe I’m missing how ongoing life cycle steps would catch it later, but B seems closer to root cause for me. Agree?
D imo, only asset life cycle management handles retiring unused applications so that's the best fit here.
D , asset life cycle management is what actually covers the whole process from acquisition to retirement, so it helps avoid accumulating unused applications. Just managing acquisition (like C) doesn't catch stuff falling out of use later. Pretty sure D’s the standard governance control here. Open to other takes if I missed something practical.
B , business case procedures should catch if apps aren't needed in the first place. D is tempting though.
D tbh, that's what covers ongoing review and retiring unused assets. Nothing else here really deals with the whole application lifespan.
D imo. Had something like this in a mock exam and asset life cycle management was the expected pick for unused apps.
C vs D here-if it's about ongoing review and retiring unused apps, D (Asset life cycle management) is probably the way to go since it covers the whole process. C only handles what gets acquired, not after. Pretty sure D is best but I see why folks get stuck.
I think D, not C. Asset life cycle management covers retirement, not just acquisition. C is a common trap here.
Sick of how ISACA always makes these sound trickier than they are. D imo.
Be respectful. No spam.
