Q: 2
Please read this scenario prior to answering the question
You are working as an Enterprise Architect at a large supermarket. The company runs many retail
stores, as well as an online grocery shop. Many of the stores used to remain open 24/7, but the
number has decreased in recent years. Instead, they now focus on fulfilling online orders during
the night.
The company has a mature Enterprise Architecture (EA) practice and uses the TOGAF standard
for its architecture development method. The EA practice is involved in all aspects of the
business, with oversight provided by an Architecture Board with representatives from different
parts of the business. The EA program is sponsored by the Chief Information Officer (CIO).
Each store uses a standard method to track sales and inventory. This involves sending accurate
timely sales data to a central Al-based inventory management system that can predict demand,
adjust stock levels and automate reordering. The central inventory management system is housed
at the company's central data center.
The company has bought a major rival. The Chief Executive Officer believes that a merger will
enable growth through combined offerings and cost savings. The decision has been taken to fully
integrate the two organizations, including merging retail operations and systems. This means that
duplicated systems will be replaced with one standard retail management system. Also, the
company will reduce the number of applications that are used. The CIO expects significant
savings will be achieved by implementing these changes across the newly merged company.
One improvement that the rival has successfully implemented is the use of hand-held devices
within stores, for both customers and staff. This has increased both customer and staff employee
satisfaction due to the time savings this has brought. The CIO has given the go-ahead to roll out
the devices in all stores but has stated that training on how to use the hand-held devices should
be brief because there are a lot of employees, many of whom are part-time.
The Request for Architecture Work to oversee the merger has been approved. The project has
been scoped and you have been assigned to work on it. Your role includes managing the
architecture for the retail stores.
Refer to the scenario
You have been asked to confirm the most relevant architecture principles for the transformation.
Based on the TOGAF Standard, which of the following is the best answer?
[Note: The sequence of the principles listed in each answer does not matter. You should assume
the company follows the set of principles that are provided in the TOGAF Standard, ADM
Techniques, Architecture Principles chapter. You may need to refer to section 2.6 located in ADM
Techniques within the reference text to answer this question.]
Options
Discussion
A. matches most exam reports and official TOGAF chapters. Worth reviewing practice exams and the official guide for this one.
A. not D. The 'Ease of Use' part in D is a trap for the device rollout, but A covers the actual TOGAF principles needed for a big merger like this. Pretty sure that's what recent exam coverage suggests, but let me know if you see it different.
D
A
A tbh. The scenario is about merging two orgs, standardizing apps, and making sure the big-picture benefits are realized. That lines up with TOGAF's "maximize benefit" and "common use applications" from option A. Not 100% but that's what I'd pick here.
C/D? I know most are picking A, but D's 'Ease of Use' looks good given the rollout of hand-held devices and lots of staff needing quick ramp-up. Plus, 'Business Continuity' seems important for a big merger. Could be missing bigger TOGAF priorities like in A though. Open to thoughts on why D isn't right here.
A
A since maximizing benefit to the enterprise and common use applications lines up best with merging business ops in TOGAF. D is tempting for the device rollout, but I think A covers the big-picture architecture principles better here. Open to a different view if I'm missing something.
D . The scenario mentions hand-held devices improving satisfaction, so 'Ease of Use' in D seems pretty important. Also, 'Business Continuity' and 'Data is an Asset' fit with their ongoing ops and systems integration. Might be missing the broader transformation angle though. Anyone else go for D at first glance?
A tbh. Merger is about maximizing enterprise benefit and reducing duplicate systems, so principles like "Maximize Benefit to the Enterprise" and "Common Use Applications" in A match TOGAF focus for this scenario. D looks tempting because of "Ease of Use," but doesn't cover the transformation needs. Seen similar logic in practice Qs, but open if anyone sees a strong case for D.
Be respectful. No spam.