SAS 9.4 Base Programming - Performance-Based Exam Free Sample Questions

This is the correct approach. The RETAIN statement is crucial to hold the value of CumulativeSales across observations. The conditional if FIRST.Region then CumulativeSales = 0; correctly resets the accumulator at the beginning of each new Region group. The final assignment statement CumulativeSales = CumulativeSales + SalesAmount; is incorrect syntax for a sum statement but works as a simple assignment; the proper sum statement would be CumulativeSales + SalesAmount;. However, of the options, this is the most complete and functional logic. The sum statement CumulativeSales + SalesAmount; implicitly retains the variable.

By default, SAS handles division by zero by assigning a missing value (.) to the result variable for that observation. It does not stop the DATA step. It prints a 'NOTE: Division by zero.' message to the log, along with the line number and column where it occurred. This is a common source of logic errors, as the program runs to completion but produces incorrect or incomplete results.

The SCAN function is essential for parsing strings based on delimiters. It can be used with the '-' delimiter to extract the 1st ('FY24'), 2nd ('Q3'), and 3rd ('EMAIL') 'words' from the CampaignID string.

The SUBSTR function can be used to extract parts of the string based on position. For example, SUBSTR(CampaignID, 1, 4) could get 'FY24'. While SCAN is more robust for this specific task, SUBSTR is also a valid function for extracting substrings and would be needed to get the 'FY' part from the first word.

The INPUT function is necessary to convert the character year '24' (extracted from 'FY24') and quarter '3' (extracted from 'Q3') into numeric variables if numerical analysis is required later. This is a common step after parsing.

This statement is false. While it is a best practice and logically necessary for a correct merge, SAS will not stop with an error by default if the data is not sorted. Instead, it will issue an 'ERROR: BY variables are not properly sorted' message in the log and continue processing, often producing an incorrect result. This is a common source of logic errors.

The GETNAMES=YES statement tells SAS to use the first row it reads as variable names. The DATAROW=n option specifies the first row of data to read. Since the headers are in row 51, the data itself begins on row 52. Therefore, DATAROW=52 is the correct option to use in conjunction with GETNAMES=YES.

This is the correct solution. It opens both ODS destinations (EXCEL and PDF) at the beginning. It then uses ods pdf exclude Freq; to specifically tell the PDF destination to ignore any output from PROC FREQ. The EXCEL destination is not affected and will receive output from both procedures. Finally, ods _all_ close; is the best practice to close all open destinations. This approach is targeted and correctly implements the specific exclusion requirement for only one of the destinations.

This is the most efficient and correct solution. The BY PatientID; statement ensures each patient's data is processed as a group and PatientID is retained in the output. The VAR Weight_:; statement uses a variable list to select all variables starting with 'Weight_', which is a flexible way to include all measurement columns. By default, PROC TRANSPOSE will create a _NAME_ variable with the original variable names (Weight_Day1, etc.) and a COL1 variable with their values. The RENAME= option is then used to give these new columns more meaningful names. Subsequent data steps would be needed to parse the day number from the Measurement variable.

The correct syntax for a LIBNAME statement is LIBNAME libref [engine] 'path' [options];. The engine name, XLSX in this case, is specified directly after the libref and before the path. The ENGINE= keyword is not used in this context.

For evaluating a single variable against multiple mutually exclusive conditions, a SELECT group is often more efficient and easier to read than a long chain of IF-THEN/ELSE IF statements. The SELECT statement evaluates the expression once and then compares the result to each WHEN condition, which can be faster than re-evaluating conditions in an IF chain.

This code is correct. The VALUE statement defines a format named ScoreFmt. It correctly specifies numeric ranges for each category. The keyword OTHER is used as a catch-all for any values that do not fall into the specified ranges, which is the proper way to handle unexpected or invalid data.