Pegasystems PEGACPLSA88V1 Exam - Topic 8 Question 19 Discussion

Actual exam question for Pegasystems's PEGACPLSA88V1 exam

Question #: 19
Topic #: 8

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 Isabella at Aug 26, 2024, 08:37 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Micaela

4 months ago

Option B could lead to redundancy issues, not a fan.

upvoted 0 times

...

Kate

4 months ago

Embedding in each department sounds like a maintenance nightmare.

upvoted 0 times

...

Long

4 months ago

Wait, why would we not embed it in the enterprise app? Seems odd.

upvoted 0 times

...

Winifred

4 months ago

Totally agree, C is the way to go!

upvoted 0 times

...

Viola

5 months ago

I think option C makes the most sense for reusability.

upvoted 0 times

...

Jules

5 months ago

I recall that we talked about avoiding duplication, so maybe option D is the right choice since it allows each department to manage their own version.

upvoted 0 times

...

Keena

5 months ago

I feel like option A could work, but what if the departments need to customize the functionality? That makes me hesitant.

upvoted 0 times

...

Quentin

5 months ago

I think we practiced a similar question where the focus was on reusability. Maybe option C makes sense for integration purposes?

upvoted 0 times

...

Ivan

5 months ago

I remember discussing how embedding components can lead to better maintainability, but I'm not sure if it should be in the enterprise app or separate.

upvoted 0 times

...

I'm not entirely sure about this one. The question seems to be testing our understanding of application architecture and component reuse. I'll need to carefully consider the pros and cons of each option before making a decision.

upvoted 0 times

...

Huey

5 months ago

I'm leaning towards option C. Placing the component in a separate application makes the most sense to me, as it allows for centralized management and easy integration across the different departments. This approach seems the most scalable and maintainable in the long run.

upvoted 0 times

...

Adrianna

5 months ago

Option B seems like the safest bet to me. Embedding the component in both the enterprise application and the department applications ensures that it's available everywhere it's needed. That way, the departments don't have to worry about integrating with a separate application.

upvoted 0 times

...

Graciela

5 months ago

I'm a bit confused by this question. It's not entirely clear to me what the "enterprise application" is referring to, or how that differs from the department applications. I'll need to think this through carefully before selecting an answer.

upvoted 0 times

...

Nieves

5 months ago

This seems like a straightforward question about the best way to implement a reusable component. I think I'll go with option C - placing the component in a separate application that the departments can integrate with. That way, the component can be easily accessed and used across the organization.

upvoted 0 times

...

Ryan

6 months ago

Hmm, I'm a bit confused. The question says the errors and warnings are tracked and placed into downloadable reports, but it's asking where they can't be found. I'll have to think this through carefully.

upvoted 0 times

...

Kati

1 year 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

1 year ago

I think option D is the most practical solution for our company.

upvoted 0 times

...

Brinda

2 years 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

1 year ago

Glory: Definitely, C is the best approach for this use case.

upvoted 0 times

...

Glory

1 year 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 year ago

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

upvoted 0 times

...

Audry

2 years 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 years 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