CAPA Feedback Flashcards

1
Q

General Development Practices

Why is error handling and logging important?

A

To track processes, identify errors, and prevent logic from getting stuck, especially during integrations or automations.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

General Development Practices

What tools should be used for maintaining readable and consistent code?

General Development Practices

A

SQL Linters, refactoring, consistent data types, and adhering to the DRY (Don’t Repeat Yourself) principle.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

General Development Practices

Why is thorough testing essential before go-live?

A

It ensures regression testing, edge-case handling, and consistency across inputs, outputs, and navigation paths.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Functional Development

What should be considered when dealing with list pages or child pages?

A

Validate dependent functionality and ensure adequate regression testing for cross-functional elements like save buttons.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Functional Development

How can performance issues in list pages be avoided as data scales?

A

Implement filtering or pagination to limit the data displayed.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Data Management

How can query performance be optimized?

A

Eliminate unnecessary joins, DISTINCT statements, UDFs in joins or where clauses, and redundant fields.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Data Management

How should dynamic numbering in concurrent scenarios be tested?

A

Stress test to ensure no duplicate numbers are generated due to race conditions.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Data Management

What should be considered for database cleanup?

A

Remove data from unused fields, tables, and custom data beyond standard cleanup scripts.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Configuration & Environment Management

Why avoid hardcoding configuration settings?

A

To prevent errors when promoting code between environments; use dynamic configuration files instead.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Configuration & Environment Management

What best practices should be followed for Node-Red development?

A

Use dockerized dev environments and store environment-specific settings in configuration files.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Configuration & Environment Management

How should self-hosted client environments be managed?

A

Sync promptly, document discrepancies, and use comparison tools to validate updates.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

APIs, Integrations, & Interfaces

How should API calls handle errors?

A

Implement error handling for non-200 responses and use pagination logic for APIs with record limits.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

APIs, Integrations, & Interfaces

What should SOAP API-dependent code account for?

A

Handle both single-object and array responses based on returned rows.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Excel Reporting & Outputs

How can Excel numerical formatting issues be handled?

A

Use preformatted templates, treat numbers as text, or apply custom cell formatting in code.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Input Validation

What should be assumed for text fields in inputs?

A

Always assume untrusted inputs may contain special characters or exceed database limits.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Project Management & Deployment

What should be done during rollout to avoid code reversion?

A

Use release processes or enforce installation order in test and production environments.

17
Q

Project Management & Deployment

What must be verified before closing a ticket?

A

Ensure code is merged, deployed to production, and all documentation (e.g., CAPA) is complete.

18
Q

Project Management & Deployment

How can patches and updates be validated during upgrades?

A

Use Git history logs, comparison tools, and regression testing to confirm critical features remain functional.

19
Q

Special Considerations

Why consider edge cases during development?

A

To handle missing data, concurrent processes, and interactions between updated and dependent features.

20
Q

Special Considerations

How should prior versions of documents or data be handled?

A

Maintain them in a non-editable, published state for consistency.

21
Q

Special Considerations

What steps help prevent regression in large projects or aging tickets?

A

Simplify with releases or sprints, and use comparison tools to validate updates.