Pegasystems Exam PEGACPLSA88V1 Topic 2 Question 21 Discussion

Actual exam question for Pegasystems's PEGACPLSA88V1 exam

Question #: 21
Topic #: 2

A Pega COE team is building a reusable component for a functionality that will be mandatory for all Pega applications that are built for the different departments of a company.

The component functionality is documented and published in a common SharePoint file, so that it is accessible by all Pega developers within the company.

Which one of the following approaches will work best for this use case?

AThe component should be embedded in the enterprise application, so that it does not need to be embedded in the department applications.

BThe component should be embedded in the enterprise application, and should also be embedded in the department applications.

CThe component should be placed in a separate application so that the departments can all integrate with that application when they want to run the functionality.

DThe component should not be embedded in the enterprise application. Instead, each department should include the component in their own application.

Show Suggested Answer

Suggested Answer: C

Separate Application for Reusable Component:

Placing the component in a separate application ensures modularity and reusability.

Departments can integrate with this application as needed, ensuring consistency and reducing redundancy.

Benefits:

Centralized maintenance and updates.

Easier to manage and deploy across various departments.

Avoids embedding the component directly in multiple applications, which could lead to version control issues.

Pega Best Practices Guide

Pega Academy Course on Reusable Components and Modular Design

These answers and explanations have been verified according to the Pega Lead System Architect guidelines and best practices.

by Wilson at Sep 17, 2024, 05:46 AM

Limited Time Offer

25%

Off

Get Premium PEGACPLSA88V1 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Kenda

1 months ago

Ooh, I'm feeling a bit mischievous. What if we just embed the component in the enterprise app, but make it so convoluted that no one can figure it out? That'll show 'em! Just kidding, Option C is the clear winner here.

upvoted 0 times

...

2 months ago

Option C is the way to go! Keeping the component in a separate app allows for easy integration and maintenance across different departments. Brilliant!

upvoted 0 times

Chi

2 months ago

It definitely simplifies maintenance and updates for all the different departments.

upvoted 0 times

...

Herschel

2 months ago

I agree, having the component in a separate application makes it easier for departments to integrate.

upvoted 0 times

...