BlackFriday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Pegasystems Exam PEGACPLSA88V1 Topic 8 Question 19 Discussion

Actual exam question for Pegasystems's PEGACPLSA88V1 exam
Question #: 19
Topic #: 8
[All PEGACPLSA88V1 Questions]

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?

Show Suggested Answer Hide 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.

Contribute your Thoughts:

Kati
2 months ago
Option D just sounds like a recipe for inconsistency and redundancy. Might as well have each department reinvent the wheel.
upvoted 0 times
...
Thaddeus
2 months ago
I think option D is the most practical solution for our company.
upvoted 0 times
...
Brinda
2 months ago
Haha, can you imagine the department apps trying to embed the same component? That would be a maintenance nightmare! C is definitely the way to go.
upvoted 0 times
Charlene
28 days ago
Glory: Definitely, C is the best approach for this use case.
upvoted 0 times
...
Glory
1 months ago
Yeah, it would be a mess if each department had to embed the same component in their own app.
upvoted 0 times
...
Ricarda
1 months ago
I agree, having the component in a separate application makes it easier for departments to integrate.
upvoted 0 times
...
...
Audry
2 months ago
I agree, having a centralized component application is the way to go. That way, the departments can just plug into it without having to maintain the component themselves.
upvoted 0 times
...
Carlee
2 months ago
Option C seems like the most scalable approach. Putting the component in a separate app allows for easy integration and updates across the different departments.
upvoted 0 times
Torie
19 days ago
True, it really depends on the specific needs and structure of the company.
upvoted 0 times
...
Zoila
20 days ago
I see your point, but having it separate allows for more flexibility and easier updates.
upvoted 0 times
...
Crista
1 months ago
But wouldn't it be more efficient to embed the component in the enterprise application so that it's already there for all departments?
upvoted 0 times
...
Michal
2 months ago
Yes, it definitely seems like the most efficient and scalable option for this use case.
upvoted 0 times
...
Mireya
2 months ago
I agree, having the component in a separate application makes it easier for all departments to integrate.
upvoted 0 times
...
Wilson
2 months ago
I agree, having the component in a separate application makes it easier for all departments to integrate.
upvoted 0 times
...
...
Lina
2 months ago
I see your point, but I think option C is the most flexible choice.
upvoted 0 times
...
Sharika
3 months ago
I disagree, I believe option B is more efficient.
upvoted 0 times
...
Loise
3 months ago
I think option A is the best approach.
upvoted 0 times
...

Save Cancel