D365 F&O Technical › Module 12: X++ Overview › Question #9588
Single Choice Easy

QWhich of the following actions isn't a best practice to consider when coding?

ID: #9588 Module 12: X++ Overview 195 views
Question Info
#9588Q ID
EasyDifficulty
Module 12: X++ OverviewTopic
Start Quiz on This Topic
 Your Answer

Choose the Best Option

Click any option to instantly check if you're correct.

  • A Comment code to communicate with other developers ✔ ✖
  • B Use a naming standard for an organization ✔ ✖
  • C Limit code comments to shorten text strings ✔ ✖
  • D Each element should have a label assigned in the Properties window ✔ ✖
Correct Answer

Explanation

  • A. Commenting code to communicate with other developers is considered a best practice to show others the purpose of code.
  • B. Using a naming standard for an organization is considered a best practice.
  • C. Limiting code comments to shorten text strings isn't a best practice because comments should be used liberally.
  • D. Each element having a label assigned in the Properties window is a best practice because labels are necessary for the user interface.
 Continue Practice
Previous Question Next Question
 Share

Share This Question

Challenge a friend or share with your study group.

 More from This Topic

Related MCQ Questions

What are the three main Object-Oriented Programming components? You notice some performance issues where certain tasks are taking longer than they should. When you investigat You need a conditional statement that checks if a variable equals “In progress,” “Completed,” or “Canceled.” D You have the following X++ statement: <pre class = "prettyprint"><xmp> For(int counter = What is the VAR keyword used for in X++? Where can variables be declared in X++? Which one of the following is not a relevant business concept to consider before and during an implementation Which of the following statements is NOT true about variable declarations? When you deploy a cloud-based solution of finance and operations apps, which source control process is availab What is a guiding principle in creating a branching structure for your implementation?