R Programming Language Certification Communication & Stakeholder Relations 3 — Questions and Answers
Question 1: A marketing team requests that all future analyses be 'version controlled.' Which workflow change should the analyst make?
- Store R scripts and R Markdown files in a Git repository (Correct answer)
- Save multiple copies of scripts with date suffixes
- Use only RData files for storage
- Archive outputs as ZIP files
Correct answer: Store R scripts and R Markdown files in a Git repository
Git repositories track every change to code with author, timestamp, and commit message, providing full audit trails and enabling collaboration.
Question 2: Which knitr chunk option suppresses R code from appearing in a rendered report while still showing its output?
- echo = FALSE (Correct answer)
- eval = FALSE
- include = FALSE
- message = FALSE
Correct answer: echo = FALSE
echo = FALSE hides the source code in the rendered document while still executing the code and displaying results, ideal for non-technical audiences.
Question 3: A finance stakeholder needs a table of summary statistics. Which R package produces publication-quality tables directly from data frames most efficiently?
- kableExtra or gt (Correct answer)
- base print()
- writeLines()
- cat()
Correct answer: kableExtra or gt
kableExtra and gt provide rich formatting options—column alignment, highlighting, footnotes—that turn R data frames into professional HTML or LaTeX tables.
Question 4: During a stakeholder meeting, an analyst presents a p-value of 0.049 as 'highly significant.' Why is this communication problematic?
- A p-value just below 0.05 is borderline and should be presented with effect size and confidence interval context (Correct answer)
- The threshold for significance is 0.01, not 0.05
- P-values below 0.05 are always highly significant
- The p-value should not be mentioned in stakeholder meetings
Correct answer: A p-value just below 0.05 is borderline and should be presented with effect size and confidence interval context
Calling 0.049 'highly significant' overstates certainty; responsible communication pairs p-values with effect sizes and confidence intervals to convey practical importance.
Question 5: A stakeholder from a different department asks for the raw data underlying a chart. What R function allows you to write a data frame to a shareable CSV?
- write.csv() or readr::write_csv() (Correct answer)
- save()
- sink()
- dump()
Correct answer: write.csv() or readr::write_csv()
write.csv() and readr::write_csv() export data frames to comma-separated files that any spreadsheet application can open.
Question 6: An R Markdown report renders correctly locally but fails on a colleague's machine because a package is missing. What is the best practice to prevent this?
- Use renv to create a project-level package library with a lockfile (Correct answer)
- Include install.packages() calls at the top of the report
- Send the colleague your entire R library folder
- Specify package versions in a README comment
Correct answer: Use renv to create a project-level package library with a lockfile
renv captures the exact package versions used in a project in a lockfile, allowing collaborators to restore identical environments with renv::restore().
Question 7: When communicating uncertainty in a forecast to non-statistician stakeholders, which visualization is most interpretable?
- A fan chart or shaded confidence band around the forecast line (Correct answer)
- A table of standard errors
- A Q-Q plot
- A histogram of residuals
Correct answer: A fan chart or shaded confidence band around the forecast line
Fan charts and confidence bands visually encode uncertainty width directly on the forecast, making it intuitive for non-technical audiences without requiring statistical knowledge.
A marketing team requests that all future analyses be 'version controlled.' Which workflow change should the analyst make?