For which two reasons would you execute PIP Auditor reports regularly during your PIP
development?
A.
This is the compliance report for a given PIP, which gives you statistics based on category and
priority.
B.
The detailed violation report goes down to line/column level so that you can fix them easily.
C.
This is the compliance report that shows CAVS test results.
D.
This report shows progress of PIP development.
Explanation:
A:The PIP Auditor generates what is called a “Technical Compliance Report”,
reporting code violations based on rules, priority, category, project, and test suite.
D: The PIP Auditor is run against your BPEL and ESB code to check whether they follow the AIA
methodology for coding conventions. The output is a static HTML report. Therefore, the results area single snapshot of your code at the time it was run.The PIP Auditor can be run against Oracle
out-of-the-box PIPs, against PIPs that you have customized, or against your custom code that
follows AIA design and development guidelines. Thus, in some cases, you may want to run the
report weekly to continously monitor your progress (or lack thereof) of coding compliancy.The PIP
Auditor reports on compliancy to coding standards.The PIP Auditor also provides suggestions for
fixes for each of the identified violations.
Reference: White Paper, OVERVIEW OF THE ORACLE AIA FOUNDATION PACK PIP AUDITOR